This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Unsupported provider

Author vbr
Recipients akitada, amaury.forgeotdarc, collinwinter, ezio.melotti, georg.brandl, giampaolo.rodola, gregory.p.smith, jaylogan, jhalcrow, jimjjewett, loewis, mark, moreati, mrabarnett, nneonneo, pitrou, r.david.murray, rsc, sjmachin, timehorse, vbr
Date 2010-09-21.14:17:36
SpamBayes Score 6.8346138e-09
Marked as misclassified No
Message-id <1285078658.52.0.589148145368.issue2636@psf.upfronthosting.co.za>
In-reply-to
Content
Well, of course, the surrogates probably shouldn't be handled separately in one module independently of the rest of the standard library. (I actually don't know such narrow implementation (although it is mentioned in those unicode quidelines 
http://unicode.org/reports/tr18/#Supplementary_Characters )

The main surprise on my part was due to the compile error rather than empty match as was the case with re; 
but now I see, that it is a consequence of the newly introduced wide unicode notation, the matching behaviour changed consistently.

(for my part, the workarounds I found, seem to be sufficient in the cases I work with wide unicode; most likely I am not going to compile wide unicode build on windows myself in the near future :-)
 vbr
History
Date User Action Args
2010-09-21 14:17:38vbrsetrecipients: + vbr, loewis, georg.brandl, collinwinter, gregory.p.smith, jimjjewett, sjmachin, amaury.forgeotdarc, pitrou, nneonneo, giampaolo.rodola, rsc, timehorse, mark, ezio.melotti, mrabarnett, jaylogan, akitada, moreati, r.david.murray, jhalcrow
2010-09-21 14:17:38vbrsetmessageid: <1285078658.52.0.589148145368.issue2636@psf.upfronthosting.co.za>
2010-09-21 14:17:36vbrlinkissue2636 messages
2010-09-21 14:17:36vbrcreate