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

2008-11-07 Thread Jim Fulton 


Are there plans for a 2.4 release that includes:

http://bugs.python.org/issue2620, and

http://svn.python.org/view?rev=65335&view=rev

?

These (and other fixes) address:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2315

Jim

--
Jim Fulton
Zope Corporation


___
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] Summary of Python tracker Issues

2008-11-07 Thread Python tracker 

ACTIVITY SUMMARY (10/31/08 - 11/07/08)
Python tracker at http://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue 
number.  Do NOT respond to this message.


 2161 open (+24) / 13941 closed (+10) / 16102 total (+34)

Open issues with patches:   709

Average duration of open issues: 714 days.
Median duration of open issues: 1971 days.

Open Issues Breakdown
   open  2145 (+24)
pending16 ( +0)

Issues Created Or Reopened (35)
___

xml.etree.ElementTree does not read xml-text over page bonderies 11/02/08
   http://bugs.python.org/issue4100reopened ocean-city
   patch   

execution model - clear and complete example in documentation11/01/08
   http://bugs.python.org/issue4246created  robwolfe  
   

Docs: Provide some examples of "pass" use in the tutorial.   11/02/08
CLOSED http://bugs.python.org/issue4247created  jafo  
   patch, patch, easy, needs review

"class in None" in html help keyword 11/02/08
CLOSED http://bugs.python.org/issue4248created  ocean-city
   patch   

HTTPResponse instance has no attribute 'code'11/02/08
   http://bugs.python.org/issue4249created  jbperez   
   

urllib2.py: HTTPResponse instance has no attribute 'code'11/02/08
   http://bugs.python.org/issue4250created  jbperez   
   

library.pdf documentation: "See also: Module " does not lin 11/02/08
   http://bugs.python.org/issue4251created  wplappert 
   

inactive item not shown in html help index pane  11/03/08
   http://bugs.python.org/issue4252created  ocean-city
   patch   

Maildir dumpmessage on   11/03/08
   http://bugs.python.org/issue4253created  [EMAIL PROTECTED] 
   

_cursesmodule.c callable update_lines_cols() 11/03/08
   http://bugs.python.org/issue4254created  nemesis   
   patch   

timing module refers to non-existent documentation   11/03/08
CLOSED http://bugs.python.org/issue4255created  stevenjd  
   

optparse: provide a simple way to get a programmatically useful  11/03/08
   http://bugs.python.org/issue4256created  andybuckley   
   

Documentation for socket.gethostname() needs tweaking11/03/08
CLOSED http://bugs.python.org/issue4257created  roysmith  
   

Use 30-bit digits instead of 15-bit digits for Python integers.  11/04/08
   http://bugs.python.org/issue4258created  marketdickinson   
   patch   

Update pydoc URLs11/04/08
   http://bugs.python.org/issue4259created  akuchling 
   

ctypes.xFUNCTYPE are decorators. 11/05/08
   http://bugs.python.org/issue4260created  LambertDW 
   

The pwd module doesn't distinguish between errors and no user11/05/08
   http://bugs.python.org/issue4261created  astrand   
   

import and compile() do not treat trailing whitespace the same   11/05/08
   http://bugs.python.org/issue4262created  mseaborn  
   

BufferedWriter non-blocking overage  11/05/08
   http://bugs.python.org/issue4263created  severb
   patch   

Patch: optimize code to use LIST_APPEND instead of calling

Re: [Python-Dev] [Python-3000] RELEASED Python 3.0rc2

2008-11-07 Thread Barry Warsaw 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Nov 7, 2008, at 4:53 AM, Victor Stinner wrote:


Hi,

Great job Barry and all contributors who fixed the "last" bugs ;-)


Thanks!


The document "What's new in Python 3.0" in should be updated:
  http://docs.python.org/dev/3.0/whatsnew/3.0.html


Issue 2306, assigned to Guido.
- -Barry

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

iQCVAwUBSRRDT3EjvBPtnXfVAQJUsAP/S9rFA0V4HDp80oxycy0coWDaW2HAnHA4
ombn/+HjWtS2zTIbCkqdFfFsZ05DRDQN7LNKZVkV1sRsmzJ9fASITQP6mpUiFy/f
Aq6I0Z73jHlZtINuDRI5ZaCQCrxHPM/lTdjEP3h0fGxtW0wEibr1/rep3gAJMomL
2V6y2mCOc8I=
=H0+/
-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] [Python-3000] RELEASED Python 3.0rc2

2008-11-07 Thread Benjamin Peterson 
On Fri, Nov 7, 2008 at 3:53 AM, Victor Stinner
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> Great job Barry and all contributors who fixed the "last" bugs ;-)

Which reminds me that this release's star developer award goes to
Victor for his hard work on fixing up the networking libraries for
Py3k!



-- 
Cheers,
Benjamin Peterson
"There's nothing quite as beautiful as an oboe... except a chicken
stuck in a vacuum cleaner."
___
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] [Python-3000] RELEASED Python 3.0rc2

2008-11-07 Thread Steve Holden 
Benjamin Peterson wrote:
> On Fri, Nov 7, 2008 at 3:53 AM, Victor Stinner
> <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> Great job Barry and all contributors who fixed the "last" bugs ;-)
> 
> Which reminds me that this release's star developer award goes to
> Victor for his hard work on fixing up the networking libraries for
> Py3k!
> 
Yay, Victor

regards
 Steve
-- 
Steve Holden+1 571 484 6266   +1 800 494 3119
Holden Web LLC  http://www.holdenweb.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] DVCS PEP update

2008-11-07 Thread Brett Cannon 
On Thu, Nov 6, 2008 at 18:23, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Brett Cannon writes:
>
>  > I consider that a perk feature.
>
> Let's not judge which features are perks or essential quite yet.  (If
> the number of features/scenarios/whatnot becomes a burden on you, then
> you must triage them, of course.)
>
> But a lot of people will not know what the features are unless they go
> in the PEP.  Eg, I've never actually encountered the merge-across-rename
> issue in the wild, for example.  A scenario where I could actually try
> it for myself would be educational, as many people I respect swear by it.
>

I never said perk features would not be mentioned in the PEP. The
Special Features section is for the various DVCSs to puff up their
chests and show off.

-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

Re: [Python-Dev] Looking for VCS usage scenarios

2008-11-07 Thread Brett Cannon 
On Thu, Nov 6, 2008 at 18:31, Steve Holden <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
>> I have started the DVCS PEP which can be seen at
>> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
>> beyond the rationale, usage scenarios I plan to use, and what other
>> sections I plan to write.
>>
> Brett:
>
> Would you care to get a PEP number allocated to this draft document? I
> think it's likely that it will eventually be published, and I'd like a
> number to use in reference to it if possible, please.
>

Sure, although I will initially just have the PEP in svn point to the
Google doc since it is easier to work with everyone helping me out
that way.

-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

Re: [Python-Dev] RELEASED Python 3.0rc2

2008-11-07 Thread Victor Stinner 
Hi,

Great job Barry and all contributors who fixed the "last" bugs ;-)

Le Friday 07 November 2008 04:53:35 Barry Warsaw, vous avez écrit :
> We expect only critical bugs to be fixed between now and the 
> final release, currently planned for 03-Dec-2008.

The document "What's new in Python 3.0" in should be updated:
   http://docs.python.org/dev/3.0/whatsnew/3.0.html

"PEP 352: Exceptions must derive from BaseException. This is the root of the 
exception hierarchy."
   I prefer to derive from Exception to be able to use 
   "exept Exception as: ..." which doesn't catch SystemExit 
   nor KeyboardInterrupt.

"PEP 3134: Exception chaining. (The __context__ feature from the PEP hasn’t 
been implemented yet in 3.0a2.)"
   The feature is now implemented!

"PEP 237: long renamed to int. (...) sys.maxint was also removed since the int 
type has no maximum value anymore."
   What about the new sys.maxsize constant? Oh, it's written at the bottom, 
   "Removed sys.maxint. Use sys.maxsize." Both paragraphs should be merged.

"Optimizations (...) 33% slower (...) we expect to be optimizing string and 
integer operations significantly before the final 3.0 release!"
   I don't expect "significant" changes before the final release. I worked on
   some patches about the int type (use base 2^30 instead of 2^15, GMP, etc.),
   but all patches optimize large integer (more than 1 digit, or more than 20
   digits) whereas most integers in Python are very small.

   About str=>unicode, I also don't expect changes. On character in now 
   4 bytes (or 2 bytes), whereas Python2 used 1 byte. This introduce an
   overhead. Most functions at C level use an conversion from byte
   string (ASCII) to Unicode (eg. PyErr_SetString). We should directly use
   wide string (eg. PyErr_SetWideString?).

"Porting to Python 3.0"
   This section is very small and gives few informations. There is nothing
   about 2to3 (just two references in the document). I also read somewhere
   that someone wrote a document explaining how to port a C extension to
   Python3.

What about a link to the "What's new in Python 2.6" document? Most people are 
still using Python 2.4 or 2.5. And Python3 is Python 2.5 +  + .

-- 
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] [Python-3000] RELEASED Python 3.0rc2

2008-11-07 Thread Barry Warsaw 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Nov 7, 2008, at 12:39 PM, Benjamin Peterson wrote:


On Fri, Nov 7, 2008 at 3:53 AM, Victor Stinner
<[EMAIL PROTECTED]> wrote:

Hi,

Great job Barry and all contributors who fixed the "last" bugs ;-)


Which reminds me that this release's star developer award goes to
Victor for his hard work on fixing up the networking libraries for
Py3k!


Indeed, great work Victor!
- -Barry

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

iQCVAwUBSRSkCnEjvBPtnXfVAQK7MAP/ayV9U241Xi1+s02LNphTwSNhJFDW9mbP
UhN1PVINDkS6kqs8GYQ6iO5KsTi20eQxjuTsITLZzFsNuGUKXRcIzkzibWZBMR7m
3WjHC5heGwaxYmaPYmcHUFipdW8T0vYGwiNmk/TWinHx11KSCEhHHeP/Mcr/xd+9
j+VCcl+45pI=
=S+vx
-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-07 Thread Martin v. Löwis 
> Are there plans for a 2.4 release that includes:

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. FWIW, there won't be another
2.3.x release.

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

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

2008-11-07 Thread Fernando Perez 
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.

Here are the results, with some background and links (I'll also paste the
original reST file at the end for reference and archival):

https://cirl.berkeley.edu/fperez/static/numpy-pep225/numpy-pep225.html

I'll mention this thread on the numpy and sage lists in case anyone from the
original discussions would like to pitch in.  

I hope this feedback is useful for you guys to make a decision.  I should note
that I'm just acting as a scribe here, relaying feedback (though I do like the
PEP and think it would be very useful for numpy).  I would most certainly NOT
be available for implementing the PEP in Python itself...

Cheers,

f


### Original reST source for feedback doc kept at
### https://cirl.berkeley.edu/fperez/static/numpy-pep225/numpy-pep225.html

=
 Discussion regarding possible new operators in Python (PEP 225)
=

.. Author: Fernando Perez
.. Contact: [EMAIL PROTECTED]
.. Time-stamp: "2008-10-28 16:47:52 fperez"
.. Copyright: this document has been placed in the public domain.

.. contents::
..
1  Introduction
2  Background: matrix multiplication and Numpy
3  Summary from the NumPy community
4  Arguments neutral towards or against the PEP
5  Other considerations and suggestions
  5.1  Operator form for logical_X functions
  5.2  Alternate comparisons
  5.3  Why just go one step?
  5.4  Alternate syntax
  5.5  Unicode operators
  5.6  D-language inspired syntax


Introduction


In the Python-dev mailing lists, there were recently two threads regarding the
possibility of adding to the language a new set of operators.  This would
provide easy syntactic support for behavior such as element-wise and
matrix-like multiplication for numpy arrays.  The original python-dev threads
are here:

* http://mail.python.org/pipermail/python-dev/2008-July/081508.html
* http://mail.python.org/pipermail/python-dev/2008-July/081551.html

And the actual PEP that discusses this at length is PEP 225:

* http://www.python.org/dev/peps/pep-0225/

In order to provide feedback from the scientific/numerical community, a
discussion was held on the numpy mailing list.  This document is a brief
summary of this discussion, in addition to some issues that were brought up
during a BOF session that was held during the SciPy'08 conference.  The point
of this document is to provide the Python development team (and ultimately
Guido) with feedback from a community that would be likely an important target
of the features discussed in PEP 225, hoping that a final decision can be made
on the PEP, either as-is or with modifications arising from this feedback.

This document contains a summary of an original discussion whose thread in the
numpy list can be found here:

* http://projects.scipy.org/pipermail/numpy-discussion/2008-August/036769.html
* http://projects.scipy.org/pipermail/numpy-discussion/2008-August/036858.html

and it has been further updated with a final round of vetting.  The final
thread which this document summarizes is here:

* http://projects.scipy.org/pipermail/numpy-discussion/2008-October/038234.html


Background: matrix multiplication and Numpy
===

It is probably useful, for the sake of the Python dev team, to provide a bit of
background regarding the array/matrix situation in `Numpy
`_, which is at the heart of much of this.  The numpy
library provides, in addition to the basic arrays that support element-wise
operations::

In [1]: from numpy import array, matrix

In [2]: a = array([[1,2],[3,4]])

In [3]: b = array([[10,20],[30,40]])

In [4]: a*b
Out[4]:
array([[ 10,  40],
   [ 90, 160]])

also an object called ``matrix`` that implements classic matrix multiplication
semantics for the ``*`` operator::
   
In [5]: aM = matrix(a)

In [6]: bM = matrix(b)

In [7]: aM*bM
Out[7]:
matrix([[ 70, 100],
[150, 220]])

The existence of two almost-but-not-quite identical objects at the core of
numpy has been the source of a large amount of discussion and effort to provide
smoother integration.  Yet, despite much work it is the opinion of many that
the situation will always remain unsatisfactory, as many pitfalls continue to
exist.  It is very easy to pass a matrix to some routine that does numerical
manipulations on its inputs and forgets to verify that a matrix was received,
and to end up with an array instead afterwards.  While much work has gone into
making the core