Re: [Python-Dev] Small lament...

[Barry Warsaw]

I heard it on reasonably believable authority that the FLUFL took the year off. 
 Lamentable.

-Barry

> On Apr 1, 2023, at 11:19, Skip Montanaro  wrote:
> 
> Just wanted to throw this out there... I lament the loss of waking up on 
> April 1st to see a creative April Fool's Day joke on one or both of these 
> lists, often from our FLUFL... Maybe such frivolity still happens, just not 
> in the Python ecosystem? I know you can still import "this" or "antigravity", 
> but those are now old (both introduced before 2010). When was the last time a 
> clever easter egg was introduced or an April Fool's Day joke played?
> 
> ¯\_(ツ)_/¯
> 
> Skip
> 
> ___
> Python-Dev mailing list -- python-...@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-...@python.org/message/Q62W2Q6R6XMX57WK2CUGEENHMT3C3REF/
> Code of Conduct: http://python.org/psf/codeofconduct/



signature.asc
Description: Message signed with OpenPGP
-- 
https://mail.python.org/mailman/listinfo/python-list

Thank you Larry Hastings!

[Barry Warsaw]

They say being a Python Release Manager is a thankless job, so the Python 
Secret Underground (PSU), which emphatically does not exist, hereby officially 
doesn’t thank Larry for his years of diligent service as the Python 3.4 and 3.5 
release manager.

On the other hand, the Python Steering Council, Python Software Foundation, and 
worldwide Python community, all of which emphatically *do* exist, all extend 
our heartfelt thanks to Larry for his excellent stewardship of Python 3.4 and 
3.5!

Python 3.4 and 3.5 were both pivotal releases.  While the features of these two 
releases are too numerous to mention here, they introduced such staples as:

* asyncio
* enum
* pathlib
* async and await keywords
* matrix multiplication operators
* typing and zipapp modules

and so much more.  For details, see:

* https://docs.python.org/3/whatsnew/3.4.html
* https://docs.python.org/3/whatsnew/3.5.html

Larry’s first official release of 3.4.0a1 was on 2013-08-03 and his last Python 
3.5.10 release was 2020-09-05.  That’s 7 years of exemplary release managing!

Larry, from all of us, and from me personally, thank you so much for your 
invaluable contributions to Python.  Enjoy your retirement!

Cheers,
-Barry (on behalf of the PSC and PSF)



signature.asc
Description: Message signed with OpenPGP
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: [python-committers] [RELEASE] Python 3.8.0b3 is now available for testing

[Barry Warsaw]

I have updated the official docker images with 3.8b3:

https://gitlab.com/python-devs/ci-images/tree/master

-Barry

> On Jul 29, 2019, at 14:48, Łukasz Langa  wrote:
> 
> Signed PGP part
> This time without delays, I present you Python 3.8.0b3:
> 
> https://www.python.org/downloads/release/python-380b3/



signature.asc
Description: Message signed with OpenPGP
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: [RELEASE] Python 3.8.0b2 is now available for testing

[Barry Warsaw]

I’ve updated the official images to include 3.8.0b2:

https://gitlab.com/python-devs/ci-images/tree/master

Cheers,
-Barry

> On Jul 4, 2019, at 15:05, Łukasz Langa  wrote:
> 
> Signed PGP part
> After a few days of delay, but somewhat cutely timed with the US Independence 
> Day, I present you Python 3.8.0b2:
> 
> https://www.python.org/downloads/release/python-380b2/ 
> 
> 
> This release is the second of four planned beta release previews. Beta 
> release previews are intended to give the wider community the opportunity to 
> test new features and bug fixes and to prepare their projects to support the 
> new feature release. The next pre-release of Python 3.8 will be 3.8.0b3, 
> currently scheduled for 2019-07-29.
> 
> Call to action
> 
> We strongly encourage maintainers of third-party Python projects to test with 
> 3.8 during the beta phase and report issues found to the Python bug tracker 
>  as soon as possible. While the release is planned 
> to be feature complete entering the beta phase, it is possible that features 
> may be modified or, in rare cases, deleted up until the start of the release 
> candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 
> and no code changes after 3.8.0rc1, the release candidate. To achieve that, 
> it will be extremely important to get as much exposure for 3.8 as possible 
> during the beta phase.
> 
> Please keep in mind that this is a preview release and its use is not 
> recommended for production environments.
> 
> No more non-bugfixes allowed on the “3.8” branch
> 
> The time has come, team. Please help make Python 3.8 as stable as possible 
> and keep all features not currently landed for Python 3.9. Don’t fret, it’ll 
> come faster than you think.
> 
> 
> - Ł
> 
> 



signature.asc
Description: Message signed with OpenPGP
-- 
https://mail.python.org/mailman/listinfo/python-list

Welcome the 3.8 and 3.9 Release Manager - Łukasz Langa!

[Barry Warsaw]

As Ned just announced, Python 3.7 is very soon to enter beta 1 and thus feature 
freeze.  I think we can all give Ned a huge round of applause for his amazing 
work as Release Manager for Python 3.6 and 3.7.  Let’s also give him all the 
support he needs to make 3.7 the best version yet.

As is tradition, Python release managers serve for two consecutive releases, 
and so with the 3.7 release branch about to be made, it’s time to announce our 
release manager for Python 3.8 and 3.9.

By unanimous and enthusiastic consent from the Python Secret Underground (PSU, 
which emphatically does not exist), the Python Cabal of Former and Current 
Release Managers, Cardinal Ximénez, and of course the BDFL, please welcome your 
next release manager…

Łukasz Langa!

And also, happy 24th anniversary to Guido’s Python 1.0.0 announcement[1].  It’s 
been a fun and incredible ride, and I firmly believe that Python’s best days 
are ahead of us.

Enjoy,
-Barry

[1] 
https://groups.google.com/forum/?hl=en#!original/comp.lang.misc/_QUzdEGFwCo/KIFdu0-Dv7sJ



signature.asc
Description: Message signed with OpenPGP
-- 
https://mail.python.org/mailman/listinfo/python-list

PEP Post-History

[Barry Warsaw]

We’ve made a small change to the PEP process which may affect readers of 
python-list and python-ideas, so I’d like to inform you of it.  This change was 
made to PEP 1 and PEP 12.

PEPs must have a Post-History header which records the dates at which the PEP 
is posted to mailing lists, in order to keep the general Python community in 
the loop as a PEP moves to final status.  Until now, PEPs in development were 
supposed to be posted at least to python-dev and optionally to python-list[1].  
This guideline predated the creation of the python-ideas mailing list.

We’ve now changed this guideline so that Post-History will record the dates at 
which the PEP is posted to python-dev and optionally python-ideas.  python-list 
is dropped from this requirement.

python-dev is always the primary mailing list of record for Python development, 
and PEPs under development should be posted to python-dev as appropriate.  
python-ideas is the list for discussion of more speculative changes to Python, 
and it’s often where more complex PEPs, and even proto-PEPs are first raised 
and their concepts are hashed out.  As such, it makes more sense to change the 
guideline to include python-ideas and/or python-dev.  In the effort to keep the 
forums of record to a manageable number, python-list is dropped.

If you have been watching for new PEPs to be posted to python-list, you are 
invited to follow either python-dev or python-ideas.

Cheers,
-Barry (on behalf of the Python development community)

https://mail.python.org/mailman/listinfo/python-dev
https://mail.python.org/mailman/listinfo/python-ideas

Both python-dev and python-ideas are available via Gmane.

[1] PEPs may have a Discussions-To header which changes the list of forums 
where the PEP is discussed.  In that case, Post-History records the dates that 
the PEP is posted to those forums.  See PEP 1 for details.



signature.asc
Description: Message signed with OpenPGP
-- 
https://mail.python.org/mailman/listinfo/python-list

New security-annou...@python.org mailing list

[Barry Warsaw]

I’m happy to announce the availability of a new mailing list, with the mission 
of providing security announcements to the Python community from the Python 
Security Response Team (PSRT):

security-annou...@python.org

You can sign up in the usual Mailman way:

https://mail.python.org/mailman/listinfo/security-announce

This joins our suite of security related forums.  As always, if you believe 
you’ve found a security issue in Python, you should contact the PSRT directly 
and securely via:

secur...@python.org

For more information on how you can contact us, see:

https://www.python.org/news/security/

We also have a public security-focused discussion mailing list that you can 
subscribe and contribute to.

security-...@python.org
https://mail.python.org/mailman/listinfo/security-sig

Please don’t report security vulnerabilities here, since this is a publicly 
archived mailing list.  We welcome you to collaborate here to help make Python 
and its ecosystem even more secure than it already is.

Once a security vulnerability is identified and fixed, it becomes public 
knowledge.  Generally, these are captured in a ReadTheDocs site for posterity:

https://python-security.readthedocs.io/

This new security-announce mailing list fills a void — one-way communication 
about security related matters from the PSRT back to the community.  This is an 
area that we’ve not done a great job at, frankly, and this new announcement 
list is intended to improve that situation.  The PSRT will use this low 
traffic, high value forum as the primary way the PSRT will communicate security 
issues of high importance back to the wider Python community.  All follow-ups 
to postings to this list are redirected to the security-sig mailing list.

Cheers,
-Barry (on behalf of the PSRT)



signature.asc
Description: Message signed with OpenPGP
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Moderation and slight change of (de facto) policy

[Barry Warsaw]

On Apr 17, 2016, at 06:08 PM, Matt Ruffalo wrote:

>That seems like a reasonable approach, though I think there *really*
>needs to be an option along the lines of "subscribed to the list for the
>purposes of moderation, but not receiving list messages via email".

We can do this effectively in Mailman 2.1 by adding the non-member to
accept_these_nonmembers, and that's fairly easy to do from the admin page.
Mailman 3 will make this more explicit by actually assigning a role of
"nonmember" to the person, so as to be able to more granularly control their
posting privileges.  While we're starting to roll out some Mailman 3 lists, it
will probably be a while before python-list is converted.

Alternatively, individuals can subscribe to a mailing list and then disable
delivery to their address.  This essentially accomplishes the same thing,
although for some lists, posts start out moderated until the person builds
some positive reputation.  Then the admin can turn off their moderation bit
and their posts will go straight through.

Cheers,
-Barry
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition

[Barry Warsaw]

On Dec 12, 2014, at 08:07 PM, Petr Viktorin wrote:

>If anyone is wondering why their favorite Linux distribution is stuck with
>Python 2 – well, I can only speak for Fedora, but nowadays most of what's
>left are CPython bindings.  No pylint --py3k or 2to3 will help there...

It's true that some of these are tough.  I tried and failed a few times to
port Xapian to Python 3.  The issue was opened upstream 6 years ago and it's
still unresolved: http://trac.xapian.org/ticket/346

OTOH, I ported dbus-python to Python 3 and that worked out much better; we've
had solid Python 3 bindings for several years now, which allowed us to port
many important Debian/Ubuntu tools to Python 3 and more importantly, do all
our new work in Python 3.  With other big toolkits like GObject introspection
working on Python 3, there's a lot you can do.

IME, if the underlying model is string/bytes clean, then the C extension port
can sometimes be easier than pure-Python, thanks to cpp games.  D-Bus's model
is pretty clean, Xapian I found to be not so much (it doesn't help that Xapian
is C++ ;).

We're actually not terribly far from switching Debian and Ubuntu's default
to Python 3.  On Debian, the big blocker is the BTS code (which uses SOAP) and
on Ubuntu it's the launchpadlib stack.  I hope to find time after Jessie to
work on the former, and before 16.04 LTS to work on the latter.

Not that I disagree that there's a long tail of code that would still benefit
a significant population if it got ported to Python 3.  By far Python 3 is a
better language, with a better stdlib, so the work is worth it.

Cheers,
-Barry
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition

[Barry Warsaw]

On Dec 11, 2014, at 11:35 AM, Mark Roberts wrote:

>I disagree. I know there's a huge focus on The Big Libraries (and wholesale
>migration is all but impossible without them), but the long tail of
>libraries is still incredibly important.

It is, but I think it's increasingly the case that packages which don't
support Python 3 will either be shamed into it, important enough to get high
quality contributed ports, or will be effectively abandoned and alternatives
found.  This is a big change from where we were several years ago.

All my new $work code is Python 3.  Some libraries are bilingual but
applications start and stay in Python 3-only.

Just recently the last two dependencies in Mailman 3 that blocked us from
beginning the port to Python 3 have been replaced[1].  We have active branches
that are slowly porting own code now[2].

While we can't quite declare victory yet, and there will always be legacy code
for which there just aren't the resources to port, I think it's perfectly
reasonable for Python 3 to be the default target version for any new code (and
a lot of existing code).

Cheers,
-Barry

[1] SQLAlchemy replaced Storm, and Falcon replaced restish in our trunk.

[2] https://code.launchpad.net/~barry/mailman/py3 and
https://code.launchpad.net/~raj-abhilash1/mailman/py3


pgpsEg8uVRAi1.pgp
Description: OpenPGP digital signature
-- 
https://mail.python.org/mailman/listinfo/python-list

RELEASED: Python 2.6.9 final

[Barry Warsaw]

Hello Pythoneers and Pythonistas,

Five years ago this month, we released Python 2.6.  It was an important
version in Python's evolution, as it was developed in tandem with Python 3.0
and had the express intent of starting the transition toward Python 3.

Amazingly, here we are five years later, and I am happy (and a little sad) to
announce the Python 2.6.9 final release.

Python 2.6.9 is a security-only source-only release, and with this, I
officially retire the Python 2.6 branch.  All maintenance of Python 2.6,
including for security issues, has now ended.

So too has my latest stint as Python Release Manager.  Over the 19 years I
have been involved with Python, I've been honored, challenged, stressed, and
immeasurably rewarded by managing several Python releases.  I wish I could
thank each of you individually for all the support you've generously given me
in this role.  You deserve most of the credit for all these great releases;
I'm just a monkey pushing buttons. :)

Here then are some release notes about 2.6.9.

For ongoing maintenance, please see Python 2.7.

Future issues with Python 2.6 may still be tracked in the Python bug tracker,
and you may wish to visit specific issues to see if unofficial patches are
available for 2.6.

http://bugs.python.org

The source can be downloaded from:

http://www.python.org/download/releases/2.6.9/

You can also see what's changed since Python 2.6.8:

http://www.python.org/download/releases/2.6.9/NEWS.txt

Users on OS X 10.9 (Mavericks) please note that issue 18458, which can crash
the interactive interpreter, is *not* fixed in 2.6.9.  If this issue affects
you, please review the tracker for possible options:

http://bugs.python.org/issue18458

Enjoy,
-Barry
(on behalf of the Python development community)


signature.asc
Description: PGP signature
-- 
https://mail.python.org/mailman/listinfo/python-list

Released: Python 2.6.9 release candidate 1

[Barry Warsaw]

Hello Pythoneers and Pythonistas,

I'm happy to announce the availability of Python 2.6.9 release candidate 1.

Python 2.6.9rc1 is a security-fix source-only release for Python 2.6.  This
means that general bug maintenance has ended, and only critical security
issues are being fixed.  It also means that no installers for Windows or Mac
OS X will be provided.  The last binary release of Python 2.6 was 2.6.6.

Python 2.6.9 final is currently scheduled for Monday, October 28, 2013.  Five
years after the original release of Python 2.6, the 2.6.9 final release will
be the last release of the Python 2.6 series.  After this, all official
maintenance of any kind for Python 2.6 will cease and the series will be
retired.

For ongoing maintenance, please see Python 2.7.

Since 2.6.9 will be the last Python 2.6 release ever, I ask that you please
download Python 2.6.9rc1, build it on your favorite platforms, and test it
with your favorite code.  You can report bugs to the Python bug tracker:

http://bugs.python.org

The source can be download from:

http://www.python.org/download/releases/2.6.9/

You can also see what's changed since Python 2.6.8:

http://www.python.org/download/releases/2.6.9/NEWS.txt

Many thanks go out to the entire Python community for their contributions and
help in making Python 2.6.9 available, especially Jyrki Pulliainen for his
patch contributions.

Enjoy,
-Barry
(on behalf of the Python development community)


signature.asc
Description: PGP signature
-- 
https://mail.python.org/mailman/listinfo/python-list

Python 3 porting

[Barry Warsaw]

I want to take this opportunity to make folks aware of several Python 3
porting initiatives and resources.

In Ubuntu 12.10, we are going to be making a big push to target all the
applications and libraries on the desktop CDs to Python 3.  While this is a
goal of Ubuntu, the intent really is to work with the wider Python community
(i.e. *you*!) to help drive more momentum toward Python 3.

We can't do this alone, and we hope you will participate.  While we on Ubuntu
have our own list of priorities, of course we want to push as much of this as
possible upstream so that everyone can benefit, regardless of platform.  We
also want to help spread the word about Python 3, and how easy it can be to
support it.

One of the best ways to get involved is to join the 'python-porting' mailing
list:

http://mail.python.org/mailman/listinfo/python-porting

which is *the* forum for discussion issues, getting help, and coordinating
with others on Python 3 ports of your favorite upstream projects.

I've also resurrected the #python3 IRC channel on Freenode, for those of you
who want to provide or receive more real-time help.

Web resources for porters include:

 * http://getpython3.com/
   General Python 3 resources, forkable on github

 * http://python3porting.com/
   Lennart Regebro's excellent in-depth porting guide

 * https://wiki.ubuntu.com/Python/3
   My quick guide for porting

 * https://wiki.ubuntu.com/Python/FoundationsQPythonVersions
   Detailed plans for Python 3 on Ubuntu 12.10

 * http://tinyurl.com/6vm3egu
   My recent blog post on Ubuntu's plans for Python 3

 * http://tinyurl.com/7dsyywo
   Ubuntu's top priorities for porting, as a shared Google doc spreadsheet

Many of these pages have additional links and resources for porting, and can
help you find packages that need resources in getting to Python 3.

At the Ubuntu Developer Summit in Oakland, California, May 7-11, 2012, we'll
also be holding some sessions on Python 3, so if you're in the area, please
come by.

http://uds.ubuntu.com/

Cheers,
-Barry


signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

Released: Python 2.6.7

[Barry Warsaw]

Hello Pythoneers and Pythonistas,

I'm happy to announce the final release of Python 2.6.7.

Python 2.6 is in security-fix only mode.  This means that general bug
maintenance has ended, and only critical security issues are being fixed.
We will support Python 2.6 in security-fix only mode until October 2013.
Also, this is a source-only release; no installers for Windows or Mac OS X
will be provided.

Please download the source from:

http://www.python.org/download/releases/2.6.7/

The NEWS file contains the list of changes since 2.6.6:

http://www.python.org/download/releases/2.6.7/NEWS.txt

Many thanks go out to the entire Python community for their contributions and
help in making Python 2.6.7 available.

Enjoy,
-Barry
(on behalf of the Python development community)


signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.7 release candidate 2 now available

[Barry Warsaw]

Hello to all you Pythoneers and Pythonistas,

I'm happy to announce the availability of Python 2.6.7 release candidate 2.
Release candidate 1 was not widely announced due to a mismatch between the
Mercurial and Subversion branches.  Barring any unforeseen issues, this will
be the last release candidate before 2.6.7 final, which is currently scheduled
for June 3, 2011.

As previously announced, Python 2.6 is in security-fix only mode.  This means
that general bug fix maintenance has ended, and only critical security fixes
are supported.  We will support Python 2.6 in security-fix only mode until
October 2013.  Also, this is a source-only release; no installers for Windows
or Mac OS X will be provided.

Please download and test this release candidate.

http://www.python.org/download/releases/2.6.7/

The NEWS file contains a list of changes since 2.6.6.

http://www.python.org/download/releases/2.6.7/NEWS.txt

Many thanks go out to the entire Python community for their contributions
great and small.

Enjoy,
-Barry
(on behalf of the Python development community)



signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

Released: Python 2.6.6

[Barry Warsaw]

Hello fellow Pythoneers and Pythonistas,

I'm very happy to announce the release of Python 2.6.6.  A truly impressive
number of bugs have been fixed since Python 2.6.5.  Source code and Windows
installers for Python 2.6.6 are now available here:

http://www.python.org/download/releases/2.6.6/

The full details of everything that's changed is available in the NEWS file:

http://www.python.org/download/releases/2.6.6/NEWS.txt

Python 2.6.6 marks the end of regular maintenance releases for the Python 2.6
series.  From now until October 2013, only security related, source-only
releases of Python 2.6 will be made available.  After that date, Python 2.6
will no longer be supported, even for security bugs.

My deepest appreciation go out to everyone who has helped contribute fixes
great and small, and much testing and bug tracker gardening for Python 2.6.6.

Enjoy,
-Barry
(on behalf of the Python development community)


signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.6 release candidate 2 now available.

[Barry Warsaw]

Hello fellow Python enthusiasts,

The source tarballs and Windows installers for the second (and hopefully last)
Python 2.6.6 release candidate is now available:

http://www.python.org/download/releases/2.6.6/

We've had a handful of important fixes since rc1, and of course a huge number
of bugs have been fixed since 2.6.5, with the full NEWS file available here:

http://www.python.org/download/releases/2.6.6/NEWS.txt

We would love it if you can download, install, and test this version with your
favorite projects and on your favorite platforms.  We expect to release Python
2.6.6 final on August 24, 2010.

Please note that with the release of Python 2.7 final on July 3, 2010, and in
accordance with Python policy, Python 2.6.6 is the last scheduled bug fix
maintenance release of the 2.6 series.  Because of this, your testing of this
release candidate will help immensely.  We plan on continuing to support
source-only security fixes in Python 2.6 for the next five years.

My thanks go out to everyone who has contributed with code, testing and bug
tracker gardening for Python 2.6.6.  The excellent folks on #python-dev are
true Pythonic heros.

Enjoy,
-Barry
(on behalf of the Python development community)


signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.6 release candidate 1 now available

[Barry Warsaw]

Hello fellow Pythoneers and Pythonistas,

The source tarballs and Windows installers for the first (and hopefully only)
Python 2.6.6 release candidate is now available:

http://www.python.org/download/releases/2.6.6/

As usual, we would love it if you could download, install, and test these with
your favorite projects and environments.  A truly impressive number of bug
have been fixed since Python 2.6.5, with the full NEWS file available here:

http://www.python.org/download/releases/2.6.6/NEWS.txt

Barring complications, we expect to release Python 2.6.6 final on August 16,
2010.

Please note that with the release of Python 2.7 final on July 3, 2010, and in
accordance with Python policy, Python 2.6.6 is the last scheduled bug fix
maintenance release of the 2.6 series.  Because of this, your testing of this
release candidate will help immensely.  We will of course continue to support
security fixes in Python 2.6 for quite some time.

My thanks go out to everyone who has helped contribute fixes great and small,
and much testing and bug tracker gardening for Python 2.6.6.  The excellent
folks on #python-dev are true Pythonic heros too.

Enjoy,
-Barry
(on behalf of the Python development community)


signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6.5

[Barry Warsaw]

On behalf of the Python community, I'm happy to announce the availability of
Python 2.6.5 final.  This is the latest production-ready version in the Python
2.6 series.

Python 2.6.5 fixes dozens of issues in the core, built-in modules, libraries,
and documentation since Python 2.6.4 was released back in October 2009.  We
highly recommend that you upgrade to Python 2.6.5.

Please see the NEWS file for all the gory details.

http://www.python.org/download/releases/2.6.5/NEWS.txt

Source tarballs and the Windows installers can be downloaded from the Python
2.6.5 page.  The Mac OS X disk image will be uploaded soon.

http://www.python.org/download/releases/2.6.5/

For more information on Python 2.6 in general, please see

http://docs.python.org/whatsnew/2.6.html

Please report bugs for any Python version in the Python tracker.

http://bugs.python.org

Enjoy,
-Barry

Barry Warsaw
ba...@python.org
Python 2.6 Release Manager
(on behalf of the entire python-dev team)


signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.5 release candidate 2 now available

[Barry Warsaw]

Hi everyone,

The source tarballs and Windows installer for Python 2.6.5 release candidate 2
are now available:

http://www.python.org/download/releases/2.6.5/

As usual, please download, install, and test them with your favorite projects
and environments.  A number of regressions and build problems on OS X have
been fixed since rc1, and I'm really hoping we will not have to do an rc3.
I'm currently planning on releasing 2.6.5 final on March 19, 2010.

Enjoy,
-Barry

P.S. The Mac installer will hopefully be available soon.



signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.5 release candidate 1 now available

[Barry Warsaw]

Hello everyone,

The source tarballs and Windows installer for Python 2.6.5 release candidate 1
are now available:

http://www.python.org/download/releases/2.6.5/

Please download them, install them, and try to use them with your favorite
projects and environments.  If no regressions are found, we will do the final
release on Monday March 15, 2010.  Please test the release candidate as
much as possible in the meantime, and help make 2.6.5 a rock solid release!

Thanks,
-Barry

P.S. The Mac installer will hopefully be available soon.


signature.asc
Description: PGP signature
-- 
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6.4

[Barry Warsaw]

On behalf of the Python community, I'm happy to announce the  
availability of Python 2.6.4.  This is the latest production-ready  
version in the Python 2.6 series.


We had a little trouble with the Python 2.6.3 release; a number of  
unfortunate regressions were introduced.  I take responsibility for  
rushing it out, but the good news is that Python 2.6.4 fixes the known  
regressions in 2.6.3.  We've had a lengthy release candidate cycle  
this time, and are confident that 2.6.4 is a solid release.  We highly  
recommend you upgrade to Python 2.6.4.


Please see the NEWS file for all the gory details.

http://www.python.org/download/releases/2.6.4/NEWS.txt

Source tarballs and the Windows installers can be downloaded from the  
Python 2.6.4 page.  The Mac OS X disk image will be uploaded soon.


   http://www.python.org/download/releases/2.6.4/

For more information on Python 2.6 in general, please see

   http://docs.python.org/whatsnew/2.6.html

Please report bugs for any Python version in the Python tracker.

   http://bugs.python.org

Enjoy,
-Barry

Barry Warsaw
ba...@python.org
Python 2.6 Release Manager
(on behalf of the entire python-dev team)



PGP.sig
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.4rc2

[Barry Warsaw]

Hello everyone.

The source tarballs and Windows installers for Python 2.6.4rc2 are now  
available:


http://www.python.org/download/releases/2.6.4/

Please download them, install them, and try to use them with your  
projects and environments.  Let's make 2.6.4 a rock solid release!  If  
there are no more regressions found, we'll do the final release in one  
week, on 25-October.


Enjoy,
-Barry



PGP.sig
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.4rc1

[Barry Warsaw]

Hello everyone.

The source tarballs and Windows installers for Python 2.6.4rc1 are now  
available:


http://www.python.org/download/releases/2.6.4/

Please download them, install them, and try to use them with your  
projects and environments.  Let us know if you encounter any problems  
with them.  Hopefully we can avoid the situation with 2.6.3 having  
such critical bugs.


2.6.4 final is planned for 18-October.

Cheers,
-Barry



PGP.sig
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6.3

[Barry Warsaw]

On behalf of the Python community, I'm happy to announce the  
availability of Python 2.6.3.  This is the latest production-ready  
version in the Python 2.6 series.  Somewhere near 100 bugs have been  
fixed since Python 2.6.2 was released in April 2009.  Please see the  
NEWS file for all the gory details.


http://www.python.org/download/releases/2.6.3/NEWS.txt

Source tarballs, Windows installers and the Mac OS X disk image can be  
downloaded from the Python 2.6.3 page.


http://www.python.org/download/releases/2.6.3/

For more information on Python 2.6 in general, please see

http://docs.python.org/whatsnew/2.6.html

Please report bugs for any Python version in the Python tracker.

http://bugs.python.org

Enjoy,
-Barry

Barry Warsaw
ba...@python.org
Python 2.6 Release Manager
(on behalf of the entire python-dev team)



PGP.sig
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2.6.3rc1 available

[Barry Warsaw]

The first (and hopefully last) release candidate for Python 2.6.3 is  
now available via


http://www.python.org/download/releases/2.6.3/

Source releases and Windows binaries are currently available, and Mac  
OS X binaries should be forthcoming.


Nearly 100 bugs have been fixed since 2.6.2.  Barring any unforeseen  
problems, we will make the final 2.6.3 release this Friday, October  
2nd.  Please give this release candidate a spin and let us know if you  
encounter any show stopping problems.


Enjoy,
-Barry



PGP.sig
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list

Python 3.0 (pinin' for the fjords)

[Barry Warsaw]

Now that Python 3.1 is out, it seems there's been some confusion as to  
whether there will be one last Python 3.0 release, i.e. Python 3.0.2.


At the PyCon 2009 language summit it was decided that there will be  
*no* Python 3.0.2.  Python 3.0 is different than all other releases.   
There will be no last maintenance release and no ongoing security  
releases.  Python 3.1 is the replacement for Python 3.0, and it's  
release schedule was accelerated specifically so that production users  
would be able to switch immediately.


If you're using Python 3, you are strongly urged to update to Python  
3.1.  Python 3.1 will be a 'normal' release in that we're making all  
the guarantees that we make for other releases.  It is likely that  
Python 3.2 is 18-24 months away, there will be Python 3.1.x  
maintenance releases, and there will be one last Python 3.1.x release  
after the final release of Python 3.2.


Cheers,
-Barry



PGP.sig
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-mode] What text editor is everyone using for Python

[Barry Warsaw]

On May 28, 2009, at 7:09 AM, Andreas Roehler wrote:

python-mode.el was its bloody-minded determination to regard '_' as  
a word

character, something which caused me more typing that it ever saved.



Its just one line to comment in python-mode.el, like this:

 ;; (modify-syntax-entry ?\_ "w"  py-mode-syntax-table)


This one is ancient and I remember that Guido and I talked about this  
for a long time before settling on the behavior.


-Barry



PGP.sig
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-Dev] RELEASED Python 2.6.2

[Barry Warsaw]

On Apr 17, 2009, at 5:42 AM, Piet van Oostrum wrote:


Maybe a link to the MacOSX image can also be added to
http://www.python.org/download


Done.
-Barry



PGP.sig
Description: This is a digitally signed message part
--
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-Dev] RELEASED Python 2.6.2

[Barry Warsaw]

On Apr 15, 2009, at 4:47 PM, Russell E. Owen wrote:


Thank you for 2.6.2.

I see the Mac binary installer isn't out yet (at least it is not  
listed

on the downloads page). Any chance that it will be compatible with 3rd
party Tcl/Tk?

Most recent releases have not been; the only way I know to make a
compatible build is to build the installer on a machine that already  
has

a 3rd party Tcl/Tk installed; the resulting binary is then compatible
with both 3rd party versions of Tcl/Tk and also with Apple's ancient
built in version.


I can't answer this, but Ronald is building the OS X image for 2.6.2,  
AFAIK.  I think it will be out soon, and maybe he can answer your Tcl/ 
Tk question.


-Barry



PGP.sig
Description: This is a digitally signed message part
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6.2

[Barry Warsaw]

On behalf of the Python community, I'm happy to announce the  
availability of Python 2.6.2.  This is the latest production-ready  
version in the Python 2.6 series.  Dozens of issues have been fixed  
since Python 2.6.1 was released back in December.  Please see the NEWS  
file for all the gory details.


http://www.python.org/download/releases/2.6.2/NEWS.txt

For more information on Python 2.6 in general, please see

 http://docs.python.org/dev/whatsnew/2.6.html

Source tarballs, Windows installers, and (soon) Mac OS X disk images  
can be downloaded from the Python 2.6.2 page:


http://www.python.org/download/releases/2.6.2/

Please report bugs for any Python version in the Python tracker:

http://bugs.python.org

Enjoy,
-Barry

Barry Warsaw
ba...@python.org
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)



PGP.sig
Description: This is a digitally signed message part
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6.2 candidate 1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'm happy to announce the release of Python 2.6.2 candidate 1.  This  
release contains dozens of bug fixes since Python 2.6.1.  Please see  
the NEWS file for a detailed list of changes.


Barring unforeseen problems, Python 2.6.2 final will be released  
within a few days.


   http://www.python.org/download/releases/2.6.2/NEWS.txt

For more information on Python 2.6 please see

http://docs.python.org/dev/whatsnew/2.6.html

Source tarballs and Windows installers for this release candidate can  
be downloaded from the Python 2.6.2 page:


   http://www.python.org/download/releases/2.6.2/

Bugs can be reported in the Python bug tracker:

   http://bugs.python.org

Enjoy,
Barry

Barry Warsaw
ba...@python.org
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSdwZ0HEjvBPtnXfVAQJTsAP+Krt1F6qGjuk9a7q8HwF2oAWr/peIAfDf
7HGjOpieoyyAKO1ZNqWvxZ1Ftx+I0YHjfk5OKz/1FN9H3eteFU/L5EEbJD1iTSmK
LAOycWWtWJp+OPatqveHZbGr4ap4XON05yMrzlewnnIH0iGnYjMAgxKkwVKA7MwN
BiXDeBPba1A=
=HdKG
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-Dev] PEP 382: Namespace Packages

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Apr 6, 2009, at 9:21 AM, Jesse Noller wrote:


On Thu, Apr 2, 2009 at 4:33 PM, M.-A. Lemburg  wrote:

On 2009-04-02 17:32, Martin v. Löwis wrote:

I propose the following PEP for inclusion to Python 3.1.


Thanks for picking this up.

I'd like to extend the proposal to Python 2.7 and later.



-1 to adding it to the 2.x series. There was much discussion around
adding features to 2.x *and* 3.0, and the consensus seemed to *not*
add new features to 2.x and use those new features as carrots to help
lead people into 3.0.


Actually, isn't the policy just that nothing can go into 2.7 that  
isn't backported from 3.1?  Whether the actual backport happens or not  
is up to the developer though.  OTOH, we talked about a lot of things  
and my recollection is probably fuzzy.


Barry

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

iQCVAwUBSdoDAXEjvBPtnXfVAQIrPgQAse7BXQfPYHJJ/g3HNEtc0UmZZ9MCNtGc
sIoZ2EHRVz+pylZT9fmSmorJdIdFvAj7E43tKsV2bQpo/am9XlL10SMn3k0KLxnF
vNCi39nB1B7Uktbnrlpnfo4u93suuEqYexEwrkDhJuTMeye0Cxg0os5aysryuPza
mKr5jsqkV5c=
=Y9iP
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-Dev] RELEASED Python 3.0.1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Feb 13, 2009, at 11:46 PM, Benjamin Kaplan wrote:


Any chance of getting a Mac installer for this one?


I believe Ronald is planning to upload it soon.
Barry

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

iQCVAwUBSZbWDHEjvBPtnXfVAQJNOQQAl89fJc7ezmpaDlClehtFJTwX5xE7JAtD
yZ47O9yUOQfdIem2l1VVApHnsnUmLKILYG3v4MHiWJBjOT10Oxjc4JKlV3nmREda
aUYOHCk1aHrPgdLHS4Cb/NBA6uYoG/+fHBcEMujClxv30lUTj76kDcjIMlflcpu6
r9I/jJdYywg=
=nyT7
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 3.0.1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team, I'm happy to announce the  
availability of Python 3.0.1, the first bug fix release of Python  
3.0.  Version 3.0.1 fixes dozens of bugs reported since the release of  
Python 3.0 on December 3rd, 2008.


Python 3.0 represents a major milestone in Python's history.  This new  
version of the language is incompatible with the 2.x line of releases,  
while remaining true to BDFL Guido van Rossum's vision.


For more information, links to documentation, and downloadable  
distributions, see the Python 3.0.1 release page:


http://www.python.org/download/releases/3.0.1/

To report bugs in Python 3.0.1, please submit them to the issue  
tracker at:


http://bugs.python.org/

Enjoy!
Barry

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

iQCVAwUBSZYpSnEjvBPtnXfVAQLQwgP/WSHp12dJVpEYtEOL/X8ynCQACriij9AM
PgT6SacbMJLbsy84CTGA1lxF4NdEUQMY1IYz0do/aZ0+nBkSoy7SlkOVcncysLSC
hVyTVlWQBdh63yA8QUk1I5dMbKeNpbCqRRgvSHaBrVdVz9mDM/r/L+j9lhBW4Cam
2lHLjRdQaG0=
=vy0O
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6.1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hot on the heals of Python 3.0 comes the Python 2.6.1 bug-fix  
release.  This is the latest production-ready version in the Python  
2.6 family.  Dozens of issues have fixed since Python 2.6 final was  
released in October.  Please see the NEWS file for details:


http://www.python.org/download/releases/2.6.1/NEWS.txt

For more information on Python 2.6 please see

http://docs.python.org/dev/whatsnew/2.6.html

Source tarballs and Windows installers can be downloaded from the  
Python 2.6.1 page:


   http://www.python.org/download/releases/2.6.1/

Bugs can be reported in the Python bug tracker:

   http://bugs.python.org

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSTi3KnEjvBPtnXfVAQLhQAP7BR8eqlVLDlu/bp2tGaRRQS8GW5X8KQQk
h0RwCcAKK19WH6YS6zH+VoIpD8LnD37YqZL3m5MQZ/rDf0o3e6152CZ6GJvWE+0i
6w0cSvDqdWuOpfUfpYR21eQnoFuC6x/yfI//yWCnu8bZCypjmJCLKZAvu4pMjYgD
ceChg4lLE68=
=u/iW
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

Re: RELEASED Python 3.0 final

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Dec 3, 2008, at 9:13 PM, Dotan Cohen wrote:


On this page:
http://www.python.org/download/releases/3.0/

The text "This is a proeuction release" should probably read "This is
a production release". It would give a better first impression :)


Fixed, thanks!
- -Barry

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

iQCVAwUBSTc/WHEjvBPtnXfVAQL8TwP+M2Ryv7WY36ICEvzGU4EzlRG/gI4MolQe
cD8DJUJfQuR6INTot/t7vTcL8oDHq7q9OHbfvd3jmSwH/ZytsMz2OvJUYlKDQjwG
BcQRpioprcesoU6cufSmKAUiUP+L0RTAMmT0WDbbeCzzMZRq3Humd4Zs43nL26NT
uFb83Dk6yWA=
=qPjn
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 3.0 final

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the release of Python 3.0 final.


Python 3.0 (a.k.a. "Python 3000" or "Py3k") represents a major  
milestone in Python's history, and was nearly three years in the  
making.  This is a new version of the language that is incompatible  
with the 2.x line of releases, while remaining true to BDFL Guido van  
Rossum's vision.  Some things you will notice include:


* Fixes to many old language warts
* Removal of long deprecated features and redundant syntax
* Improvements in, and a reorganization of, the standard library
* Changes to the details of how built-in objects like strings and  
dicts work

* ...and many more new features

While these changes were made without concern for backward  
compatibility, Python 3.0 still remains very much "Pythonic".


We are confident that Python 3.0 is of the same high quality as our  
previous releases, such as the recently announced Python 2.6.  We will  
continue to support and develop both Python 3 and Python 2 for the  
foreseeable future, and you can safely choose either version (or both)  
to use in your projects.  Which you choose depends on your own needs  
and the availability of third-party packages that you depend on.  Some  
other things to consider:


* Python 3 has a single Unicode string type; there are no more 8-bit  
strings
* The C API has changed considerably in Python 3.0 and third-party  
extension modules you rely on may not yet be ported
* Tools are available in both Python 2.6 and 3.0 to help you migrate  
your code

* Python 2.6 is backward compatible with earlier Python 2.x releases

We encourage you to participate in Python 3.0's development process by  
joining its mailing list:


http://mail.python.org/mailman/listinfo/python-3000

If you find things in Python 3.0 that are broken or incorrect, please  
submit bug reports at:


   http://bugs.python.org/

For more information, links to documentation, and downloadable  
distributions, see the Python 3.0 website:


   http://www.python.org/download/releases/3.0/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSTc3pXEjvBPtnXfVAQI69wP/dPHh8IL3GxziEV9QzlveKG+KyZb2X16x
fxJnTCiXAbiAhT5C+m43OEnbF1PJgMDKtcZ5b7aQb4TQ0mJxISTQh0RfLCpArmlo
tdTbzCLnh13KzB+3sUHCx+MeQNXERoWDV8hLz+4Ae71UsuUGynhtyP7ZJMJDue8j
so2gv3fOMSs=
=vkiy
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-mode] special editor support for indentation needed.

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Nov 27, 2008, at 3:13 AM, Andreas Roehler wrote:


Eric S. Johansson wrote:

Andreas Roehler wrote:

with python-mode.el from

http://sourceforge.net/projects/python-mode/


I think there's something wrong with the site because it tells me  
it's version

1.0 from year 2005.


You are right, sorry. I should tell you the present place.

Barry Warsaw, the maintainer, took it to

https://launchpad.net/python-mode

Please look there for last version.

Maybe subscribe the mailing list at
[EMAIL PROTECTED]


I've tried as best I could to make it clear on the SF site that we've  
moved development to Launchpad.  SF doesn't make it easy though.   
Unfortunately, we still haven't been able to import all the tracker  
issues from SF to LP, though a request is still open on that.  For  
now, all new issues on python-mode.el should be opened here:


https://bugs.launchpad.net/python-mode

I'm going to try to do a new release of python-mode.el, maybe this  
weekend, but it won't have much more than what's in the bzr repository  
right now.


- -Barry

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

iQCVAwUBSS6y9nEjvBPtnXfVAQIHkQQApjxeqbv9cfDVKB3b0Pvy3seryYi7++8S
J1LXnwUUgq7xUtf72i5tyJrdUPQRl6cQXxMaLczzm+HE0ULdB7mRiYOYpA+eZS/J
man5kPe89KbyI6Jvd0NqXe+YJ2ud6XLVQQ37l8Is9vwBgrPFtgmHuxEkz0Ya8iS/
pV/QrTpd6ow=
=WuiR
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 3.0rc3

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the third and last planned release candidate for  
Python 3.0.


This is a release candidate, so while it is not quite suitable for  
production environments, we strongly encourage you to download and  
test this release on your software.  We expect only critical bugs to  
be fixed between now and the final release, currently planned for 03- 
Dec-2008.


If you find things broken or incorrect, please submit bug reports at

   http://bugs.python.org

Please read the RELNOTES file in the distribution for important  
details about this release.  For more information and downloadable  
distributions, see the Python 3.0 website:


   http://www.python.org/download/releases/3.0/

See PEP 361 for release schedule details:

   http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSSbOhHEjvBPtnXfVAQLzBwP/dS2j4XhZMNdb28TG3ZblkSmlPS4IU20U
Vvq85inUkJ6idwKZBqa6brrD1hbqrl4UjKZh4/ppzhIwsJtFMlMiqnkHVrvIYFBG
Yg+pQdO5HQzrw9K04aTdtNiKTiiJNIkqWdQQUd573XBFODRAIaq0qwk9C24kXeZM
e3xNgNRxfmY=
=TvxY
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 3.0rc2

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the second release candidate for Python 3.0.


This is a release candidate, so while it is not suitable for  
production environments, we strongly encourage you to download and  
test this release on your software.  We expect only critical bugs to  
be fixed between now and the final release, currently planned for 03- 
Dec-2008.


If you find things broken or incorrect, please submit bug reports at

http://bugs.python.org

For more information and downloadable distributions, see the Python
3.0 website:

http://www.python.org/download/releases/3.0/

See PEP 361 for release schedule details:

http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSRO7wHEjvBPtnXfVAQIYrQP+Lynpa/p7VMY/YxJyjxiBI0bvOATPIKbE
jqu9ZFwXlO19+G4bFiAoYviY5UFYPm3TpbMoso2qNoJsJFLSt4d+AycWWcaXKd08
vpifsxVoWvdLCLZtT7ioMBJh/juu+Pchf2o2l+PHm5aWlLvq/24uu8YKbpSKKbr9
K4gB4ecYd3A=
=3UPl
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

Re: RELEASED Python 2.6 final

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Oct 1, 2008, at 11:46 PM, Barry Warsaw wrote:

On behalf of the Python development team and the Python community, I  
am happy to announce the release of Python 2.6 final.  This is the  
production-ready version of the latest in the Python 2 series.


Source tarballs, Windows installers, and Mac disk images can be  
downloaded from the Python 2.6 page:


   http://www.python.org/download/releases/2.6/


Due to a minor snafu in our build scripts, the source tgz and tar.bz2  
files contained some extra cruft.  I have created and uploaded new  
tarballs but I have /not/ bumped the Python version number since they  
were made from exactly the same Subversion tag.  The new tarballs are  
identical to the originals except that they don't contain the cruft  
(.svn files and such).


If you have already downloaded the tarballs, you do not need to  
download the new ones. The new tarballs are about 2MB smaller though.


With apologies,
- -Barry

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

iQCUAwUBSOUgjnEjvBPtnXfVAQJ3gQP4mxxW9kaaMlsg7yd1uNcgYa29pitYdF2+
DhFgrCajPZpskc3XlKbPcnPJWT8wtI/EIC5QcPEpAWCHECrTUHzPyGLNeMQz0kFF
/ZGCGbef7Mc/JaZvEyF6OATnKhYA5XyUOPdddygx6oar/Y6ZbK2JyLR4pvzh+gtQ
SA+u6OPIpQ==
=7uu8
-END PGP SIGNATURE-

--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6 final

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the release of Python 2.6 final.  This is the  
production-ready version of the latest in the Python 2 series.


There are many new features and modules, improvements, bug fixes, and  
other changes in Python 2.6.  Please see the "What's new" page for  
details


http://docs.python.org/dev/whatsnew/2.6.html

as well as PEP 361

http://www.python.org/dev/peps/pep-0361/

While Python 2.6 is backward compatible with earlier versions of  
Python, 2.6 has many tools and features that will help you migrate to  
Python 3.  Wherever possible, Python 3.0 features have been added  
without affecting existing code.  In other cases, the new features can  
be enabled through the use of __future__ imports and command line  
switches.


Python 3.0 is currently in release candidate and will be available  
later this year.  Both Python 2 and Python 3 will be supported for the  
foreseeable future.


Source tarballs, Windows installers, and Mac disk images can be  
downloaded from the Python 2.6 page:


http://www.python.org/download/releases/2.6/

(Please note that due to quirks in the earth's time zones, the Windows  
installers will be available shortly.)


Bugs can be reported in the Python bug tracker:

http://bugs.python.org

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSOREJ3EjvBPtnXfVAQLAigP/aEnrdvAqk7wbNQLFbmBonIr2YQbd1vEu
TyTr5imYXFWGNfv1/JMeMBjMfwpHi1bgPEDTLEZdhDRNj/G1h4NqqnpfJS0lfIaU
4JBKwnsO80se/RGyupcs5f09UdKxOljhbFKEw46CHDkd9lE+cqy2yhetEwyx3c3+
AVC11sjcO54=
=Oxo3
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6rc2 and 3.0rc1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the second and final planned release candidate  
for Python 2.6, as well as the first release candidate for Python 3.0.


These are release candidates, so while they are not suitable for  
production environments, we strongly encourage you to download and  
test them on your software.  We expect only critical bugs to be fixed  
between now and the final releases.  Currently Python 2.6 is scheduled  
for October 1st, 2008.  Python 3.0 release candidate 2 is planned for  
October 1st, with the final release planned for October 15, 2008.


If you find things broken or incorrect, please submit bug reports at

http://bugs.python.org

For more information and downloadable distributions, see the Python  
2.6 website:


http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

http://www.python.org/download/releases/3.0/

See PEP 361 for release schedule details:

http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSNHpw3EjvBPtnXfVAQLW9wP/RBCaUvhuheIh+BjLLIHQFBQi7D3uVgqi
l0+4fhhoKGJvtWklLfSM9I1prcjH/d6tzUu4fIOjX7aM+wZSG++vkfmBoehnhyZW
AvU9Lax4mqDwhOJA2QA0WMx0obpYYVHeUl7D1g9kWzbRUkZDX9NZGMWThhEOC1qA
UA3bBYbvWiQ=
=BFNH
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6rc1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the first release candidate for Python 2.6.


This is a release candidate, so while it is not suitable for  
production environments, we strongly encourage you to download the  
release and test it on your software.  We expect only critical bugs to  
be fixed between now and the final 2.6 release, still scheduled for  
October 1st, 2008.  There is one more release candidate planned for  
September 17th.


You might notice that unlike earlier releases, we are /not/ releasing  
Python 3.0rc1 at this time.  It was decided that 3.0 still needs time  
to resolve open issues and that we would not hold up the 2.6 release  
for this.  We feel that Python 2.6 is nearly ready for its final  
release.


If you find things broken or incorrect, please submit bug reports at

http://bugs.python.org

For more information and downloadable distributions, see the Python  
2.6 website:


   http://www.python.org/download/releases/2.6/

(Note that the Windows installers will be uploaded shortly.)

See PEP 361 for release schedule details:

http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSMsXV3EjvBPtnXfVAQJFsgP9GxZYQocbDTd0Z/0yEjpHfZ/FTd8y83jV
5JouO07lB8XtLawnWB9hF8sUrCuBVog5He3mLVUPDmlyn30qvjYWMG2J6zW0yYMX
yZdjUyUmta0IMCsXe7YXj369xebh4nWuwG4tDygly4donA7GYPXAlxI48MmyDJxw
1v07LM4Dttw=
=Nd3s
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6b3 and 3.0b3

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I am happy
to announce the third and last planned beta releases of Python 2.6 and Python
3.0.

Please note that these are beta releases, and as such are not suitable for
production environments.  We continue to strive for a high degree of quality,
and these releases are intended to freeze the feature set for Python 2.6 and
3.0.

As these are the last planned beta releases, we strongly urge you to download
these releases and test them against your code.  Once we reach release
candidates (currently planned for 03-Sep-2008), only highly critical bugs will
be fixed before the final release.

If you find things broken or incorrect, please submit bug reports at

 http://bugs.python.org

For more information and downloadable distributions, see the Python  
2.6 website:

 http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

 http://www.python.org/download/releases/3.0/

See PEP 361 for release schedule details:

 http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIrN472YZpQepbvXERAl4fAJ9QxHhSn/jYdA3lCYvgfXRhBVV2pgCfdNUx
3NTlSrsSULxXhoMqiNmUMSg=
=Z4+y
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6b2 and 3.0b2

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the second beta releases of Python 2.6 and Python  
3.0.


Please note that these are beta releases, and as such are not suitable  
for production environments.  We continue to strive for a high degree  
of quality, and these releases are intended to freeze the feature set  
for Python 2.6 and 3.0.


From now until the planned final releases in October 2008, we will be  
fixing known problems and stabilizing these new Python versions.  You  
can help by downloading and testing them, providing feedback and  
hopefully helping to fix bugs.  You can also use these releases to  
determine how changes in 2.6 and 3.0 might impact you.


ONLY ONE MORE BETA RELEASE IS PLANNED, so now is a great time to  
download the releases and try them with your code.  If you find things  
broken or incorrect, please submit bug reports at


http://bugs.python.org

For more information and downloadable distributions, see the Python  
2.6 website:


http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

http://www.python.org/download/releases/3.0/

See PEP 361 for release schedule details:

http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSIARKHEjvBPtnXfVAQL7AQQAjPSbfKz2Oh/au/hPzS4x2IR5/R6FVe+g
o9UYrONNRKJ14UHpbZRzvIvw/4G3PdpzzGxjYFIhVGEesEGJnMzT3YdkMHt4NW9d
HOZxL3hseGbTdpUJPCsIkNG+4hX7iuY3NSV81Z75LGAL4tqbooGqwwUslXMT5f8s
lRrZUcBRKZ0=
=ju6s
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-3000] RELEASED Python 2.6b1 and 3.0b1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Jun 19, 2008, at 4:43 AM, Paul Moore wrote:


On 19/06/2008, Barry Warsaw <[EMAIL PROTECTED]> wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community,  
I am
happy to announce the first beta releases of Python 2.6 and Python  
3.0.


Any ETA for Windows builds? The web pages still point to the alphas.
(I'd like to see the Windows builds more closely integrated with the
releases now we're in beta stage...)


Martin usually fills these in pretty quickly.  I think the current  
situation works fine for the betas but we'll make sure the final  
release (and candidates) are better coordinated.


- -Barry

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

iQCVAwUBSFpIpnEjvBPtnXfVAQJyWQP9FSH8Ipg93UDM3nmH3UtN+i61YGsQPd0O
ypHlnz4yHpxeRkJm1zkppHHI0hKMou6JOeUf05QCnPzrAdsG/mkuv5aoBrBt3dDd
UncHLoQOvXEhGrrPzexmHKv3ehxUXPQOzkiWBWVv9e69GYH4e4HcqV6s2Ya2733T
zC/EyOgkyMg=
=5wM5
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6b1 and 3.0b1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the first beta releases of Python 2.6 and Python  
3.0.


Please note that these are beta releases, and as such are not suitable  
for production environments.  We continue to strive for a high degree  
of quality, and these releases are intended to freeze the feature set  
for Python 2.6 and 3.0.


From now until the planned final releases in September 2008, we will  
be fixing known problems and stabilizing these new Python versions.   
You can help by downloading and testing them, providing feedback and  
hopefully helping to fix bugs.  You can also use these releases to  
determine how changes in 2.6 and 3.0 might impact you.  If you find  
things broken or incorrect, please submit bug reports at


  http://bugs.python.org

For more information and downloadable distributions, see the Python  
2.6 website:


  http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

  http://www.python.org/download/releases/3.0/

See PEP 361 for release schedule details:

   http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSFnIbnEjvBPtnXfVAQKCMgP+L9Vpk9vQgYw01KShtF9HyvCKE0guSy86
0Q/IRbkXGahXg910D4nVLY9NORaOSq/VP8Kx+fOU8egUDHvVF9MuKkY75ZHYoixR
mieeV7BIpYHYKYhva48FVoF4p0+sUeNvfeOAP0nnV5Pi2icGqCpzizfSHZloXJjc
Y8M4F5vVrOM=
=Oo15
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6a3 and 3.0a5

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I  
am happy to announce the third alpha release of Python 2.6, and the  
fifth alpha release of Python 3.0.


Please note that these are alpha releases, and as such are not  
suitable for production environments.  We continue to strive for a  
high degree of quality, but there are still some known problems and  
the feature sets have not been finalized.  These alphas are being  
released to solicit feedback and hopefully discover bugs, as well as  
allowing you to determine how changes in 2.6 and 3.0 might impact
you.  If you find things broken or incorrect, please submit a bug  
report at


   http://bugs.python.org

For more information and downloadable distributions, see the Python
2.6 website:

   http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

   http://www.python.org/download/releases/3.0/

These are the last planned alphas for both versions.  If all goes  
well, next month will see the first beta releases of both, which will  
also signal feature freeze.  Two beta releases are planned, with the  
final releases scheduled for September 3, 2008.


See PEP 361 for release details:

http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSCORrnEjvBPtnXfVAQIK+QQAgEUtAvW7uo0BxMiT1bCAo2E9ZecWJ9xe
DBgd/5IK8moITkqhqGAH5UvfytV6uPkOMgGIS/Uvk4hzhU3jwSopEIDJLFQ5nGtC
lCzOHzkDjSNZ8Q2OOAI9mbSHY8grvVxCMB4X2SVXIEMZ6M/X1AcV2b0utp9O1w/l
T/PEvP8U1uY=
=2Tnb
-END PGP SIGNATURE-
--
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6a2 and 3.0a4

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I'm  
happy to announce the second alpha release of Python 2.6, and the  
fourth alpha release of Python 3.0.

Please note that these are alpha releases, and as such are not  
suitable for production environments.  We continue to strive for a  
high degree of quality, but there are still some known problems and  
the feature sets have not been finalized.  These alphas are being  
released to solicit feedback and hopefully discover bugs, as well as  
allowing you to determine how changes in 2.6 and 3.0 might impact  
you.  If you find things broken or incorrect, please submit a bug  
report at

http://bugs.python.org

For more information and downloadable distributions, see the Python  
2.6 web
site:

http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

http://www.python.org/download/releases/3.0/

We are planning one more alpha release of each version, followed by  
two beta releases, with the final releases planned for August 2008.   
See PEP 361 for release details:

 http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBR/WImHEjvBPtnXfVAQJmoQP+MzqNDI+Xt8zua/FE7Ca4TVXoIIy2uoOm
I1i3+vmevZ9vtAb9hcGwfEgPY4LSwb9Js4KnJJWMPaMuFJK4NgGoiMdj+t42zDbQ
bEzfBUOCoVkejLRxIQnWeJf1Hu8JocYyCHIRffv57/QdKpHuiSs8aE8GIT3STo3o
I88H5NY1GgI=
=WT2z
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-Dev] [ANN] Python 2.3.7 and 2.4.5, release candidate 1

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mar 3, 2008, at 1:48 AM, Martin v. Löwis wrote:

>>> But it would be really nice if the configure fix for 2.5 was
>>> backported to 2.4.5 since Zope is still on 2.4 and Mac OS X skipped
>>> system builds for 2.4 going direct from 2.3 -> 2.5.
>>
>>
>> Yes, it would be very nice if this worked out of the box on Mac OS X
>> 10.5.2.  It's definitely a surprise for those of us who built our  
>> 2.4.4
>> on Mac OS X 10.4.x.
>
> I can put a notice in the release notes, but I definitely won't change
> it to work out of the box. If 2.4.4 compiled out of the box on this  
> box,
> it would have been a regression and would have to be fixed. IIUC,  
> 2.4.4
> won't compile on 10.5, either, and Python 2.4.5 will have no code to
> port it to new platforms.

Can you also add a note to the 2.3 and 2.4 web pages?

- -Barry

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

iQCVAwUBR8vsPHEjvBPtnXfVAQJVpgP5AbRU+BENEa7fv7vGUykjtQRftaF6ATQz
yTo9018UiQZ20bFv2PIvgHltsET1ksTuieSdDjGbQ3rGu3vo1tldiGYxUQJgi++C
q8ntOyLUo+nHSlKm11TTyMiNX4igl+X0bes5PlgJZbWOnw0vBvWbVRrwgMUsJqfi
ox/d8+2jWc4=
=HLja
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Python-3000] RELEASED Python 2.6a1 and 3.0a3

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mar 1, 2008, at 5:26 PM, Martin v. Löwis wrote:

>> As of 4:50 PM  EST, the links to Windows installers give 404 File Not
>> Found.
>>
>> I gather that they are still in process,
>> and notice that there is no public c.l.p. announcement.
>
> I just fixed that. The files were there; just the links were wrong.

Thanks for fixing these Martin!

- -Barry

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

iQCVAwUBR8nY1HEjvBPtnXfVAQJ3YgP/TYr0X5vRqvVDEMgsHxHuiSuYZCIr8y36
ibAh3RAGeLLK7C7NiOyAfxkesf91HCbL1in0TcnD06QZy52O8elBa927JOomP3mc
Y6K4Y49JhxonBrmGcmasnc9PFjbhXtGdWLREinuzpB5itLpRv+SevMhxP27Fp8qr
df173TV4hpk=
=nf32
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.6a1 and 3.0a3

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Python development team and the Python community, I'm  
happy to announce the first alpha release of Python 2.6, and the third  
alpha release of Python 3.0.

Python 2.6 is not only the next advancement in the Python 2 series, it  
is also a transitionary release, helping developers begin to prepare  
their code for Python 3.0.  As such, many features are being  
backported from Python 3.0 to 2.6.  It makes sense to release both  
versions in at the same time, the precedence for this having been set  
with the Python 1.6 and 2.0 releases.

During the alpha testing cycle we will be releasing both versions in  
lockstep, on a monthly release cycle.  The releases will happen on the  
last Friday of every month.  If this schedule works well, we will  
continue releasing in lockstep during the beta program.  See PEP 361  
for schedule details:

 http://www.python.org/dev/peps/pep-0361/

Please note that these are alpha releases, and as such are not  
suitable for production environments.  We continue to strive for a  
high degree of quality, but there are still some known problems and  
the feature sets have not been finalized.  These alphas are being  
released to solicit feedback and hopefully discover bugs, as well as  
allowing you to determine how changes in 2.6 and 3.0 might impact  
you.  If you find things broken or incorrect, please submit a bug  
report at

 http://bugs.python.org

For more information and downloadable distributions, see the Python  
2.6 web
site:

 http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

 http://www.python.org/download/releases/3.0/

We are planning a number of additional alpha releases, with the final  
release schedule still to be determined.

Enjoy,
- -Barry

Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBR8mlu3EjvBPtnXfVAQKePAQAgx6w9wztfJaSWkbKrbwur2U6t6o5aIY5
pyMa00CZWY06p8099BztcSjgp5rKrd6/9V7cJ0NP7NLZ+tz20uRfyI8uqoIYBIWC
ibJay6SSnzgOQM3PRIJV/K/m0dVPPPVD1LDnoEvuu+cKUpV434yHdgWkMPswsxUd
fLydrXABlOM=
=l6aj
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Mailman-Developers] Parsing and Rendering rfc8222

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Jul 6, 2006, at 1:56 PM, Brad Knowles wrote:

> Barry said:
>
>> We should certainly do everything we can to make sure that Richard's
>> ht:dig solution is nearly trivial to integrate, but I'm not sure we
>> should distribute it with Mailman.
>
> Sorry, I guess I wasn't clear -- I just meant for him to look at both
> Python and non-Python solutions, before deciding what was going to  
> be done
> and how.
>
> I wasn't advocating the incorporation of ht:dig itself into the  
> stuff we
> ship.  At least, I didn't mean for it to come off that way.

Cool, +1
- -Barry

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

iQCVAwUBRK3cv3EjvBPtnXfVAQJd9AQAnhPFHyIpMyVyzeRzQ8Xn3ZZNcmeRW+T9
HHE162EMEskuXEaZ4FzorpZ/6bAVp1IUqZ9oArEimF/CU6jRolcMyCct0n/Va0RS
cJMybtddQlq6g7OMvlH1RCQBMn4uMaBvhtQOcqQQlCoLq5G2Pdcvrvvz+6rwjfUk
fWDDnuCJc38=
=Ypl5
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Mailman-Developers] Parsing and Rendering rfc8222

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Jul 5, 2006, at 12:30 AM, Mark Sapiro wrote:

> Also there is a related issue if A posts, B replies, A replies off  
> list
> to B, and B replies on list. If threading relies solely on References:
> or In-Reply-To:, and either A's or B's MUA generates only In-Reply-To,
> this thread is broken at the 'missing' post. I don't have any really
> good suggestions for alternative threading algorithms however. I think
> there was something on this not too long ago on mailman-users or maybe
> mailman-developers - I looked and found what I think I remember. The
> relevant post is at
>  017660.html>
> and points to a description of an algorithm at
> .

I haven't read JWZ's article in a while, but IIRC, it lays out an  
algorithm that does about as good as you can do in these cases.

BTW, my earlier post re: X-List-Message-ID isn't about threading,  
it's about message identification and trying to make that as robust  
as possible.

- -Barry

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

iQCVAwUBRKxM3XEjvBPtnXfVAQJUhQP/ZXeVZhPYuXMecIMTO6QiPncRuHMZiSAA
rpGeYNspQkszVbsLB27nkppfShkJQC8iSMY8WPEssGUJ4guqROtCdJ7hUURUve5D
4uvAizTrl6Kriv82SZPCmUvN12XnfkT5+ENIkwpWEnh5xf4qoQXNqXfAqWX83Y/Y
ldDwY+zkltY=
=Nhwt
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Mailman-Developers] Parsing and Rendering rfc8222

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Jul 4, 2006, at 5:33 PM, Brad Knowles wrote:

> Don't ignore non-Python solutions.

My main problem with non-Python solutions /as a default for Mailman/  
is that it complicates distribution and packaging.  It means that  
we'll have additional dependencies we can't satisfy ourselves, e.g.  
on other interpreters or on compilers.  At least with a pure Python  
solution, we can package up a distutils thingie and be pretty much  
assured that it's going to work out of the box.

We should certainly do everything we can to make sure that Richard's  
ht:dig solution is nearly trivial to integrate, but I'm not sure we  
should distribute it with Mailman.

- -Barry

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

iQCVAwUBRKxMYHEjvBPtnXfVAQKQqgP/V82bojemSuFnLGrThmKAS0QBVNvsFsPA
IomgATzMERVs8ld+Nwi3QYG41PEMXeuxHGfU3wQqLO4SViS1BepUN1ZUuc9TJ6oM
1M3KmwID4gw5Ra5CjhIBgDjUva7E7OOM/r4/6TWp8pCHuUL/AIf5tjXu5t+NvBvn
vfC71BCMrn4=
=qAgQ
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Mailman-Developers] Parsing and Rendering rfc8222

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Jul 4, 2006, at 3:44 PM, emf wrote:

> Here's where I'm at, grouped functionally:
>
> * Need to convert rfc8222 to xml/html
>
> I haven't found anything substantial via searching. My next step is to
> go spelunking in MailManager code and other python-webmail  
> packages. If
> anyone knows good trees in this forest, please clue me in.

You might also poke around www.divmod.org and the Chandler project.   
I believe both of them are in a similar space and there may be  
components that can be borrowed from those projects to do this kind  
of thing.

> * Want to provide feeds (rss/atom/YourMommasSyntaxFormat)
>
> Right this second I'm planning on using pyfeed [1]; is there anything
> else I should consider?
>
> [1] http://home.blarg.net/~steveha/pyfeed.html
>
> * mbox thread indexing on messages
>
> I plan on using [2] to generate mbox thread indexes for rapid  
> navigation
> of lists. Any suggestions for more robust variants would be welcome;
> feedback on how to handle threading for message-id-less messages would
> also be welcome.
>
> [2] http://benno.id.au/code/archiver/jwzthreading.py

I haven't looked at either package, but JWZ does have the  
authoritative word on threading, AFAICT.

The question of Message-IDs is the interesting one because it's  
clearly the most natural unique identifier to use.  However, while  
the RFC says it /should/ be unique, there's actually no guarantee  
that it /is/ unique, or even present.  What should Mailman do if it  
sees a Message-ID collision?  What should it do if there is no  
Message-ID?

It's been argued that Mailman should clobber any Message-ID it sees  
and just overwrite it with one it can guarantee is unique (for any  
specific installation, that is).  I don't like that solution because  
of the negative effects on threading when that message is received  
through Mailman by other systems or applications.  It's also been  
suggested that we just don't worry about it, because the chances of  
collisions in practice are very small.  Yeah, okay, but what if it / 
does/ happen?  Seems like you'd still have to munge Message-ID in  
that case.

It's also been suggested that Mailman assign its own unique  
identifier whenever it forwards a message to a list membership.  I  
like this the best, and it would have to be called something like X- 
List-Message-ID or some such.  I've long favored a solution where the  
X-List-Message-ID could be calculated from components of the message  
that would have a high probability of being immutable, even if a copy  
of the message was received out-of-band from Mailman.  IOW, if an  
archiver received a message before Mailman could calculate the X-List- 
Message-ID (or if it received it after some intermediate tool  
stripped that header), it could perform the same calculation and  
would end up with the same url, probably using List-Archive in that  
calculation.

I'm thinking something along the lines of sha1 hashing Message-ID and  
perhaps Date.  RFC 2822 $3.6 says that the only required headers are  
the origination date (Date:) and originator address fields (From: and  
possibly Sender: and Reply-To:).  Those seem like good candidates to  
base a hash on, but fields like Subject and the body of the message  
are probably unusable.  Then again, we have to watch out for  
originator header munging. :/

> * full-text indexing
>
> pylucene seems to be the obvious choice; anything else I should
> consider? Anyone know of good pylucene/web UI glue code out there?

Just keep in mind that of course, Mailman is GPL so anything we  
bundle has to be GPL-compatible.

- -Barry



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

iQCVAwUBRKxLlXEjvBPtnXfVAQJsBwP/ZvTAHqZaBGA8MR0PH6Oq5c8QCqUBX2tr
JjRDT89wQYJqE+dY3tDMrPIytJBKiE50n9usfURzlikq517NG79hYfMMYfZM550K
Ua3a9oBrBTzLW+SpEUaM8KT+QakqkDNY3ro6e3KnqUhl3MwwRii9X178m7pYAHRH
Sc87Ps/1r8Y=
=OH6a
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: [Mailman-Developers] Parsing and Rendering rfc2822

[Barry Warsaw]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Jul 5, 2006, at 6:37 PM, emf wrote:

>> I seem to
>> recall this is also Barry's preference who noted the existing  
>> pipermail
>> was only a stop-gap solution so there would be some default archiver,
>> but it was never the intention Mailman would have any extensive
>> archiving implementation.
>
> Like many stop gap solutions, this one is widely used, and represents
> the most visited portion of the "mailman web UI". At a bare  
> minimum, the
> archive pages should provide decent navigation.
>
> The requirement for a default archiver remains, and the solution I
> propose is much more override friendly than the existing one; it
> wouldn't create hundreds of webpages out of the archives, just read  
> out
> of the existing mbox files.

Pipermail was originally a separate project, developed by Andrew  
Kuchling IIRC.  A looonngg time ago it was integrated into Mailman,  
but not in a terribly clean way (e.g. inheritance through cut-and- 
paste).  I don't think Andrew's been interested in Pipermail for years.

My own position on Pipermail and archiving is that Mailman should  
come with a default archiver that is minimally useful for simple  
sites, and that the Python-based Pipermail makes the most sense to  
serve as this default, simplistic archiver.  It keeps packaging,  
dependencies, and deployment very simple.  I'm open to suggestions  
for alternatives though. (Or ideally, some young college student with  
lots of free time to devote unending hours to improving Pipermail, at  
the expense of family, sleep, social life and studies.  That, or get  
Tim Peters interested.)

However, it should be very easy to integrate any other archiver with  
Mailman, and to the extent that current APIs need to be improved, I'm  
all for that.  If you have a pet archiver that requires changes to  
Mailman to work better, please let us know!

Pipermail's lack of a default search feature is its biggest (but by  
no means only) problem.  I'd like to see this addressed, if it can be  
done cleanly, in MM2.2.  I'd favor a Python solution here, for the  
same reasons as above but again, pluggability would be favored over a  
hard coded connection.

Other than that, it's clear that Pipermail's web u/i is so 1995, and  
needs a major overhaul.  For example, just as you'd like Mailman's  
web u/i to be easily integrated into the L&F of a site, so too for  
the Pipermail interface.  The major problem with that though is that  
because Pipermail generates its pages statically, and because of  
various bugs and misfeatures in earlier versions, any regeneration of  
the static pages to a new u/i carries with it a high potential to  
break existing links.  Honestly, I don't think there's any good  
solution to link breakage, so I think the right thing to do is to be  
able to preserve the current u/i and link algorithm unless the new  
one is explicitly enabled.  And if the archives are regenerated with  
a new u/i, we should ensure that the link urls will be much more  
persistent than they currently are, probably based on a guaranteed  
unique Message-ID or other header-based identifier.

- -Barry

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

iQCVAwUBRKxHbXEjvBPtnXfVAQJokwQAsfoFnAp4zBW/1TQXiKqADTf3GIGV1v2u
10NLSlsj11kftf2mSANqTDZvFB/oquzG7f2UBNU1OUtOQhH9guneywLcAnxcmH3o
bu1yzcA2dm0AslVPonyg76ps7KERNGK5s4Dw181jlCvjZiyloYi5m+LJhMjQSvNP
j4wUyt4CvrI=
=j6G0
-END PGP SIGNATURE-
-- 
http://mail.python.org/mailman/listinfo/python-list

Standalone email package 3.0 final

[Barry Warsaw]

Python 2.4 final will probably be released in a few hours so this seems
like a good time to release the standalone email package, version 3.0
final.  Unless there's some last second snafu, this will be identical to
the version released with Python 2.4.

email 3.0 is compatible with Python 2.3 and 2.4.  If you need to support
earlier versions of Python, stick with email 2.5.5.   For documentation
(until Fred flips the "current" docs switch) and download links, please
see the email-sig home page:

http://www.python.org/sigs/email-sig

Changes in email 3.0 include:

  * New FeedParser provides an incremental parsing API for
applications that may need to read email messages from blocking
sources (e.g. sockets).  FeedParser is also more standards
compliant than the old parser and is "non-strict", so that it
should never raise parse errors when parsing broken messages.
  * The old Parser API is (mostly) supported for backward
compatibility.
  * Previously deprecated API features have been removed, while a
few more deprecations have been added.
  * Support for Pythons earlier than 2.3 have been removed.
  * Lots and lots of fixes.

Feel free to join the email-sig mailing list for further discussion.

-Barry



signature.asc
Description: This is a digitally signed message part
-- 
http://mail.python.org/mailman/listinfo/python-list