[Python-Dev] 2.0 Release Plans

[Fredrik Lundh]

tim wrote:
> > 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.

to reduce my load somewhat, maybe someone who does
Python 2.0 development on a Unix box could produce that
patch?

(all our unix boxes are at the office, but I cannot run CVS
over SSH from there -- and sorting that one out will take
more time than I have right now...)

:::

anyway, fixing this is pretty straightforward:

1) move the class (etc) from popen2.py to os.py

2) modify the "if hasattr" stuff; change

    # popen2.py
    if hasattr(os, "popen2"):
        def popen2(...):
            # compatbility code, using os.popen2
    else:
        def popen2(...):
            # unix implementation

to

    # popen2.py
    def popen2(...):
        # compatibility code

    # os.py
    def popen2(...)
        # unix implementation, with the order of
        # the return values changed to (child_stdin,
        # child_stdout, child_stderr)

:::

> > 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.
> 
> 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).

if someone else can do the popen2 stuff, I'll take care
of this one!

</F>