Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Victor Stinner
Le Saturday 08 November 2008 00:07:33 Martin v. Löwis, vous avez écrit :
> Yes, my plan is to release 2.5.3 and 2.4.6 simultaneously.
> 2.4.6 will essentially contain everything that is on the
> branch today, unless somebody comes up with an urgent patch
> that also needs consideration.
 
Skip Montanaro and others hackers started to port the multiprocessing module 
to Python 2.4 and 2.5.
   http://code.google.com/p/python-multiprocessing/

Is it planned to include it in 2.4.6 and/or 2.5.3? I don't know the status of 
the project, but it looks like it's still in alpha or beta phase (so far to 
be stable and robust). Or can we at least include the needed patches? 
Especially th threading + fork issue:
   http://bugs.python.org/issue874900

-- 
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Barry Warsaw

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Nov 8, 2008, at 7:24 AM, Martin v. Löwis wrote:

Skip Montanaro and others hackers started to port the  
multiprocessing module

to Python 2.4 and 2.5.
  http://code.google.com/p/python-multiprocessing/

Is it planned to include it in 2.4.6 and/or 2.5.3?


Neither. For 2.4.x, we only accept security fixes; for 2.5.3, only bug
fixes (and after that, only security fixes). New features are  
rejected.


I completely agree.  If only there was an independent repository of  
add-on packages for Python available... .


- -Barry

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSRWJoHEjvBPtnXfVAQIa7wP9FF0+VbZcZWX33RPh8CTVsP/DjVhIvkLr
qLIBwyqByyVhx3kNSxHqzPmtSclOjjtfps04rcD7kPi3f9EaOb7vlvlPtiNjU95n
ti3nBszrJKLeDzBz3CagpCLVBZbXDGWAD8k3dtMGHuwR6TJZNbrHkQ1PvAaBL/wJ
Krw0ph/Qs/8=
=Fxa0
-END PGP SIGNATURE-
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Martin v. Löwis
> Skip Montanaro and others hackers started to port the multiprocessing module 
> to Python 2.4 and 2.5.
>http://code.google.com/p/python-multiprocessing/
> 
> Is it planned to include it in 2.4.6 and/or 2.5.3?

Neither. For 2.4.x, we only accept security fixes; for 2.5.3, only bug
fixes (and after that, only security fixes). New features are rejected.

> Especially th threading + fork issue:
>http://bugs.python.org/issue874900

That one is already backported to 2.5, right?

Regards,
Martin

___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Jesse Noller
No - multiprocessing should not go to the official 2.4/2.5 branches.  
The PEP specified 2.6 and beyond.


The fix for 874900 is not a bad idea though.

On Nov 8, 2008, at 6:41 AM, Victor Stinner  
<[EMAIL PROTECTED]> wrote:


Le Saturday 08 November 2008 00:07:33 Martin v. Löwis, vous avez écr 
it :

Yes, my plan is to release 2.5.3 and 2.4.6 simultaneously.
2.4.6 will essentially contain everything that is on the
branch today, unless somebody comes up with an urgent patch
that also needs consideration.


Skip Montanaro and others hackers started to port the  
multiprocessing module

to Python 2.4 and 2.5.
  http://code.google.com/p/python-multiprocessing/

Is it planned to include it in 2.4.6 and/or 2.5.3? I don't know the  
status of
the project, but it looks like it's still in alpha or beta phase (so  
far to

be stable and robust). Or can we at least include the needed patches?
Especially th threading + fork issue:
  http://bugs.python.org/issue874900

--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/jnoller%40gmail.com

___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Martin v. Löwis
> The fix for 874900 is not a bad idea though.

Doing what specifically (that has not been done yet) is not a bad idea?

Regards,
Martin
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Jesse Noller



On Nov 8, 2008, at 11:50 AM, "Martin v. Löwis" <[EMAIL PROTECTED]>  
wrote:



The fix for 874900 is not a bad idea though.


Doing what specifically (that has not been done yet) is not a bad  
idea?


Regards,
Martin


Nothing, I think you're correct and the fix is in 2.5
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Jesse Noller



On Nov 8, 2008, at 7:44 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Nov 8, 2008, at 7:24 AM, Martin v. Löwis wrote:

Skip Montanaro and others hackers started to port the  
multiprocessing module

to Python 2.4 and 2.5.
 http://code.google.com/p/python-multiprocessing/

Is it planned to include it in 2.4.6 and/or 2.5.3?


Neither. For 2.4.x, we only accept security fixes; for 2.5.3, only  
bug
fixes (and after that, only security fixes). New features are  
rejected.


I completely agree.  If only there was an independent repository of  
add-on packages for Python available... .


- -Barry



The backported version of MP is on pypi. Fancy that.
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Barry Warsaw

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Nov 8, 2008, at 8:41 AM, Jesse Noller wrote:


The backported version of MP is on pypi. Fancy that.


SHHH!  Don't tell Guido you've made dups of his time machine keys.

- -Barry

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSRXXenEjvBPtnXfVAQIMIgP+MK8WNirYeRiJELSAx7CO++IbqEYjIp7Z
+HLvjrKW9X8+Pzl7YuXizeRuUI1fnb5DLYmbB2AfnJs6wPPnTmVv6CJNHFF7g9nU
nBCRboHPPihJK4r3tpIRyFqPhitN/Whx7s7brG5YO3tl+JPceMF9oF9X4jMUtr+i
hspEMOG5/RU=
=rgCy
-END PGP SIGNATURE-
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread Terry Reedy

Martin v. Löwis wrote:
Skip Montanaro and others hackers started to port the multiprocessing module 
to Python 2.4 and 2.5.

   http://code.google.com/p/python-multiprocessing/

Is it planned to include it in 2.4.6 and/or 2.5.3?


Neither. For 2.4.x, we only accept security fixes; for 2.5.3, only bug
fixes (and after that, only security fixes). New features are rejected.


If there are release notes, they could mention mp's availability on pypi.

___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Released fixes for CVE-2008-2315 for Python 2.4?

2008-11-08 Thread skip

Terry> If there are release notes, they could mention mp's availability
Terry> on pypi.

I think the best place to reference it would be in the 2.6/3.0 module
documentation.

Skip

___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Feedback from numerical/math community on PEP 225

2008-11-08 Thread Michele Simionato
On Sat, Nov 8, 2008 at 5:01 AM, Fernando Perez <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> a while back there was a discussion about new operators for the language, 
> which
> ended in people mentioning that the status of PEP 225 was still undecided and
> that it was the most likely route to consider in this discussion.  I offered
> to collect some feedback from the numerical and math/scientific computing
> communities and report back here.

While not an user of numpy, I feel legitimate to give my feedback as a
person with a scientific background.
I personally have always felt the lack of a binary operator expressing
non-commutative multiplication.
It could be used for matrices, but also for functions composition and
other more abstract things. I think a single new operator is all is
needed.

Michele Simionato
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Getting Set Up dev doc

2008-11-08 Thread Brett Cannon
Thanks to the flu that I am getting over I finally got around to start
writing the dev docs I have been planning to author for years. The
first one is how to get set up, with the draft at
http://docs.google.com/Doc?id=dg7fctr4_5457424jfh . Obviously any
corrections are appreciated.

About the only thing I am unsure about with the doc is what the proper
separation between this doc and the dev FAQ should be. At this point
the FAQ has organically grown to the svn and ssh cheatsheet, which
makes me think that I should move all tool-specific info in this doc
to the dev FAQ and just reference the specific sections from this doc.
But I am somewhat hesitant about doing that as I don't want the FAQ to
get overloaded and just become The Dev Doc For Everything.

And so everyone knows where I am going with this, I plan to have docs
on the life of an issue (with a good chunk dedicated to writing
patches), various ways to get involved, and how to get stuff into
Python. That should cover all of the basics along with the dev FAQ.
Those of you who attended my tutorial on sprinting on the core at
PyCon 2008 should recognize how I am breaking the information down in
my head.

-Brett
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com