[Python-Dev] 2.0 Release Plans
Tim Peters
tim_one@email.msn.com
Wed, 23 Aug 2000 15:00:33 -0400
[Fredrik Lundh]
[on patch 100899]
> mal has reviewed the patch, and is waiting for an update
> from me.
Thanks! On that basis, I've reassigned the patch to you.
> PS. the best way to get me to do something is to add a
> task to the task manager.
Yikes! I haven't looked at the thing since the day after I enabled it
<wink> -- thanks for the clue.
> I currently have three things on my slate:
>
> 17333 add os.popen2 support for Unix
Guido definitely wants this for 2.0, but there's no patch for it and no
entry in PEP 200. Jeremy, please add it.
> 17334 add PyErr_Format to errors module
> 17335 add compressed unicode database
Those two are in Open patches, and both assigned to you.
> if I missed something, let me know.
In your email (to Guido and me) from Monday, 31-July-2000,
> so to summarize, Python 2.0 will support the following
> hex-escapes:
>
> \xNN
> \uNNNN
> \UNNNNNNNN
>
> where the last two are only supported in Unicode and
> SRE strings.
>
> I'll provide patches later this week, once the next SRE
> release is wrapped up (later tonight, I hope).
This apparently fell through the cracks, and I finally remembered it last
Friday, and added them to PEP 200 recently. Guido wants this in 2.0, and
accepted them long before feature-freeze. I'm currently writing a PEP for
the \x change (because it has a surreal chance of breaking old code). I
haven't written any code for it. The new \U escape is too minor to need a
PEP (according to me).