matplotlib-0.87.2 on Windows - using subprocess.Popen()

Darren Dale wrote:

    >> As soon as I know that matplotlib builds subprocess correctly
    >> for windows computers with <python-2.4, I will unmask the
    >> subprocess code again in svn. Any ideas when we might have an
    >> answer to this question?
    >>
    > I suspect that there are relatively few Python 2.3 users
    > on Windows anymore, so I say unmask it now. (It's not like
    > the case in linux where big distros, e.g. Debian, are
    > still on Python 2.3. Windows doesn't have "distros", and

enthought python is only built for 2.3 currently, as far as I can see:

  http://code.enthought.com/enthon

I think this is a pretty important constituency in the scientific
python crowd.

JDH

John Hunter wrote:

"Andrew" == Andrew Straw <strawman@...36...> writes:

    > Darren Dale wrote:
    >> As soon as I know that matplotlib builds subprocess correctly
    >> for windows computers with <python-2.4, I will unmask the
    >> subprocess code again in svn. Any ideas when we might have an
    >> answer to this question?
    >>
    > I suspect that there are relatively few Python 2.3 users
    > on Windows anymore, so I say unmask it now. (It's not like
    > the case in linux where big distros, e.g. Debian, are
    > still on Python 2.3. Windows doesn't have "distros", and

enthought python is only built for 2.3 currently, as far as I can see:

  http://code.enthought.com/enthon

I think this is a pretty important constituency in the scientific
python crowd.

We will be doing 2.4 releases in the next two weeks or so.

···

--
Robert Kern
robert.kern@...149...

"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
  -- Umberto Eco

John Hunter wrote:

"Andrew" == Andrew Straw <strawman@...36...> writes:
           
   > Darren Dale wrote:
   >> As soon as I know that matplotlib builds subprocess correctly
   >> for windows computers with <python-2.4, I will unmask the
   >> subprocess code again in svn. Any ideas when we might have an
   >> answer to this question?
   >> > I suspect that there are relatively few Python 2.3 users
   > on Windows anymore, so I say unmask it now. (It's not like
   > the case in linux where big distros, e.g. Debian, are
   > still on Python 2.3. Windows doesn't have "distros", and

enthought python is only built for 2.3 currently, as far as I can see:

http://code.enthought.com/enthon

I think this is a pretty important constituency in the scientific
python crowd.

OK, point taken.

But still, given that I think I've fixed the bug, we should unmask it so we can see if I actually did.

Still not willing to spend hours on my Windows box just to check legacy Python2.3 support,
Andrew

My understanding is that once NumPy is considered "stable", Enthought
will switch to Python 2.4.

···

On 4/5/06, Andrew Straw <strawman@...36...> wrote:

John Hunter wrote:

>>>>>>"Andrew" == Andrew Straw <strawman@...36...> writes:
>>>>>>
>>>>>>
>
> > Darren Dale wrote:
> >> As soon as I know that matplotlib builds subprocess correctly
> >> for windows computers with <python-2.4, I will unmask the
> >> subprocess code again in svn. Any ideas when we might have an
> >> answer to this question?
> >>
> > I suspect that there are relatively few Python 2.3 users
> > on Windows anymore, so I say unmask it now. (It's not like
> > the case in linux where big distros, e.g. Debian, are
> > still on Python 2.3. Windows doesn't have "distros", and
>
>enthought python is only built for 2.3 currently, as far as I can see:
>
> http://code.enthought.com/enthon
>
>I think this is a pretty important constituency in the scientific
>python crowd.
>
>

OK, point taken.

But still, given that I think I've fixed the bug, we should unmask it so
we can see if I actually did.

Still not willing to spend hours on my Windows box just to check legacy
Python2.3 support,
Andrew

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Ryan Krauss wrote:

My understanding is that once NumPy is considered "stable", Enthought
will switch to Python 2.4.

We will be switching to Python 2.4 as soon as our new build machine arrives and
we've tested Enthon on it. That should be in about two weeks.

Including numpy is a separate issue and will occur later, probably next month.

···

--
Robert Kern
robert.kern@...149...

"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
  -- Umberto Eco

Done. svn 2259.

···

On Wednesday 05 April 2006 17:14, Andrew Straw wrote:

John Hunter wrote:
>>>>>>"Andrew" == Andrew Straw <strawman@...36...> writes:
>
> > Darren Dale wrote:
> >> As soon as I know that matplotlib builds subprocess correctly
> >> for windows computers with <python-2.4, I will unmask the
> >> subprocess code again in svn. Any ideas when we might have an
> >> answer to this question?
>
> > I suspect that there are relatively few Python 2.3 users
> > on Windows anymore, so I say unmask it now. (It's not like
> > the case in linux where big distros, e.g. Debian, are
> > still on Python 2.3. Windows doesn't have "distros", and
>
>enthought python is only built for 2.3 currently, as far as I can see:
>
> http://code.enthought.com/enthon
>
>I think this is a pretty important constituency in the scientific
>python crowd.

OK, point taken.

But still, given that I think I've fixed the bug, we should unmask it so
we can see if I actually did.