[Python-Dev] Should the default Python 2.7 web page mention 2.7.5 instead of 2.7.2?

2013-08-17 Thread Peter Portante 
See http://www.python.org/download/releases/2.7/ as of Saturday, August
17th, 2013.

"Note: A bugfix release, 2.7.2, is currently
available.
Its use is recommended."

Kinds regards, -peter
___
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] Should the default Python 2.7 web page mention 2.7.5 instead of 2.7.2?

2013-08-17 Thread Benjamin Peterson 
Fixed, although hopefully there are few links to that page, since it's
really the release page of 2.7.0.

2013/8/17 Peter Portante :
> See http://www.python.org/download/releases/2.7/ as of Saturday, August
> 17th, 2013.
>
> "Note: A bugfix release, 2.7.2, is currently available. Its use is
> recommended."
>
> Kinds regards, -peter
>
> ___
> Python-Dev mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/benjamin%40python.org
>



-- 
Regards,
Benjamin
___
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] Tracker meta-issue

2013-08-17 Thread Steven D'Aprano 

Is this the right place to request somebody look at an issue in the 
meta-tracker?

http://psf.upfronthosting.co.za/roundup/meta/issue517

Replying to reviews gives an AttributeError exception. This was reported three 
months ago, and is currently unassigned.

Actually, on closer look, it seems to be the same issue as here:

http://psf.upfronthosting.co.za/roundup/meta/issue484

which was ten months ago.




Thanks,

Steven
___
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] Should the default Python 2.7 web page mention 2.7.5 instead of 2.7.2?

2013-08-17 Thread Peter Portante 
FWIW: The first hit that I saw googling "Python 2.7" brought up that page.


On Sat, Aug 17, 2013 at 11:19 AM, Benjamin Peterson wrote:

> Fixed, although hopefully there are few links to that page, since it's
> really the release page of 2.7.0.
>
> 2013/8/17 Peter Portante :
> > See http://www.python.org/download/releases/2.7/ as of Saturday, August
> > 17th, 2013.
> >
> > "Note: A bugfix release, 2.7.2, is currently available. Its use is
> > recommended."
> >
> > Kinds regards, -peter
> >
> > ___
> > Python-Dev mailing list
> > [email protected]
> > http://mail.python.org/mailman/listinfo/python-dev
> > Unsubscribe:
> > http://mail.python.org/mailman/options/python-dev/benjamin%40python.org
> >
>
>
>
> --
> Regards,
> Benjamin
>
___
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] Tracker meta-issue

2013-08-17 Thread Antoine Pitrou 
On Sun, 18 Aug 2013 03:02:28 +1000
Steven D'Aprano  wrote:
> Is this the right place to request somebody look at an issue in the 
> meta-tracker?
> 
> http://psf.upfronthosting.co.za/roundup/meta/issue517

Officially, I suppose the "right place" should be the tracker-discuss
mailing-list, but both Martin and Ezio are certainly following
python-dev.

Also, given that it significantly affects your ability to work on your
patch, I think it's fair that you ping this list, anyway.

Regards

Antoine.



> 
> Replying to reviews gives an AttributeError exception. This was reported 
> three months ago, and is currently unassigned.
> 
> Actually, on closer look, it seems to be the same issue as here:
> 
> http://psf.upfronthosting.co.za/roundup/meta/issue484
> 
> which was ten months ago.
> 
> 
> 
> 
> Thanks,
> 
> Steven



___
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] cpython: Use a known unique object for the dummy entry.

2013-08-17 Thread Antoine Pitrou 
On Sat, 17 Aug 2013 11:32:00 +0200 (CEST)
raymond.hettinger  wrote:

> http://hg.python.org/cpython/rev/2c9a2b588a89
> changeset:   85218:2c9a2b588a89
> user:Raymond Hettinger 
> date:Sat Aug 17 02:31:53 2013 -0700
> summary:
>   Use a known unique object for the dummy entry.
> 
> This lets us run PyObject_RichCompareBool() without
> first needing to check whether the entry is a dummy.
> 
> files:
>   Objects/setobject.c |  45 ++--
>   1 files changed, 20 insertions(+), 25 deletions(-)

This broke test_gdb on several machines:

==
FAIL: test_sets (test.test_gdb.PrettyPrintTests)
Verify the pretty-printing of sets
--
Traceback (most recent call last):
  File "/home/antoine/cpython/default/Lib/test/test_gdb.py", line 319,
in test_sets self.assertEqual(gdb_repr, "{'b'}")
AssertionError: "{, 'b'}" != "{'b'}"
- {, 'b'}
+ {'b'}


Obviously the pretty-printing of sets isn't able to recognize the dummy
from regular set contents, anymore :-) It should be fixable, but I
don't know how.

Regards

Antoine.


___
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