Re: [Python-Dev] Mail archive line wrapping (Was: Import and unicode: part two)
On 11:59 AM, James Y Knight wrote:
Well, yes, that's a pretty annoying bug in mailman, isn't it? If only anyone
around here was involved in mailman and could fix it! :) [I've attempted to
cc this to mailman-users with this message, but since I'm not subscribed I
dunno if it'll make it or not.]
I have this in my user CSS override file to fix the issue for myself globally
on all such archives out in the world:
/* Mailing list archives */
htmlbodypre { white-space: pre-wrap !important; }
But really, pipermail should just output a suitable style itself, e.g.: pre
style=hite-space: pre-wrap or a stylepre { white-space: pre-wrap;
}/style in the header.
This is mailman bug 266467
https://bugs.launchpad.net/mailman/+bug/266467. It was fixed in
Mailman 2.1.13.
--
Mark Sapiro msap...@value.net The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] web framework for py3k
I would want to help porting some web framework for py3k .. I want to know to know which one is good and which can be ported easily . Also i would require some guidance for this work as I am just a beginner here .. Thanks Yeswanth ___ Python-Dev mailing list Python-Dev@python.org 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-checkins] r88140 - in python/branches/py3k: Misc/NEWS Modules/zipimport.c
On Sat, Jan 22, 2011 at 5:30 AM, victor.stinner python-check...@python.org wrote: .. zipimport uses ASCII encoding instead of *cp497* to decode filenames, .. Shouldn't this be instead of *cp437*? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] web framework for py3k
On 1/22/2011 1:16 PM, yeswanth wrote: In general, this list is for development of Python, CPython, and its stdlib, not 3rd party modules. I would want to help porting some web framework for py3k .. The target of any such efforts should be 3.2 as it has changes intended to help web programming. I want to know to know which one is good and which can be ported easily Opinions will depend on the person. Such questions might be better asked on Python list or the specialized web-sig list, where there are more people involved with web frameworks. Most frameworks have their own lists. Some can be accessed as newsgroups at news.gmane.org in the gmane.comp.python hierarchy. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] What's new 2.x in 3.x docs.
The 3.x docs mostly started fresh with 3.0. The major exception is the What's new section, which goes back to 2.0. The 2.x stuff comprises about 650KB in the repository and whatever that translates into in the distribution. I cannot imagine that anyone who only has 3.x and no 2.x version would have any interest in the 2.x history. And of course, the complete 2.x history will always be available with the latest 2.7.z. And the cover page for 3.x could even say so and include a link. So why not remove it from the 3.2 release (and have two separate pages for the online version)? -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] What's new 2.x in 3.x docs.
On Sat, 22 Jan 2011 14:04:00 -0500 Terry Reedy tjre...@udel.edu wrote: The 3.x docs mostly started fresh with 3.0. The major exception is the What's new section, which goes back to 2.0. The 2.x stuff comprises about 650KB in the repository and whatever that translates into in the distribution. I cannot imagine that anyone who only has 3.x and no 2.x version would have any interest in the 2.x history. And of course, the complete 2.x history will always be available with the latest 2.7.z. And the cover page for 3.x could even say so and include a link. So why not remove it from the 3.2 release (and have two separate pages for the online version)? Well, is there any point in doing so, apart from saving 650KB in the repository? I'm not sure we care about the latter (right now the whole source tree is more than 50MB, and that's without version control information). Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Triagers and checkin access to the devguide repository
On Fri, Jan 21, 2011 at 18:35, Nick Coghlan ncogh...@gmail.com wrote: Given that some of the dev guide docs cover triaging and other aspects of managing issues on the tracker, does it make sense to offer devguide checkin access to triagers that want it? There are enough triagers with commit privileges that this is probably not needed. -Brett Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] What's new 2.x in 3.x docs.
On Jan 22, 2011, at 11:04 AM, Terry Reedy wrote: The 3.x docs mostly started fresh with 3.0. The major exception is the What's new section, which goes back to 2.0. The 2.x stuff comprises about 650KB in the repository and whatever that translates into in the distribution. I cannot imagine that anyone who only has 3.x and no 2.x version would have any interest in the 2.x history. And of course, the complete 2.x history will always be available with the latest 2.7.z. And the cover page for 3.x could even say so and include a link. So why not remove it from the 3.2 release (and have two separate pages for the online version)? I think there is value in the older whatsnew docs. The provide a readable introduction to various features and nicely augment the plain docs which can be a little dry. +1 for keeping the links as-is. Removing them takes away a resource and gains nothing. Raymond ___ Python-Dev mailing list Python-Dev@python.org 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-checkins] r88140 - in python/branches/py3k: Misc/NEWS Modules/zipimport.c
Le samedi 22 janvier 2011 à 13:25 -0500, Alexander Belopolsky a écrit : zipimport uses ASCII encoding instead of *cp497* to decode filenames, .. Shouldn't this be instead of *cp437*? Woops, correct: fixed in r88145. Victor ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Beta version of the new devguide
http://docs.python.org/devguide/ If you are a core developer and have a correction you want to make you can simply check out the devguide yourself (link is in the Resources section of the devguide) and make the corrections yourself. Otherwise reply here (you can email me directly but I already have instances of multiple people telling me about the same spelling mistake so it's nice to have it public so people know when I have been informed). As for what is left to do, there are a a few things. One is fixing some issues to allow test coverage to be run for the entire test suite (see the coverage docs to know what issues are tracking the problems). I will work on this next if no one beats me to it as both issues should be relatively simple to do. Two, what should the final URL be? Georg picked the current one and I am happy with it. Three, where should it be linked from? docs.python.org homepage? Four, what to do with www.python.org/dev/? Redirect for all the pages? Otherwise I consider the devguide ready to go. My next thing will be an official HOWTO on dealing with Python 2/3 porting/maintenance. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Beta version of the new devguide
And I forgot to mention I also plan to edit the help text on the various fields on the issue tracker to point to the triaging doc. On Sat, Jan 22, 2011 at 17:08, Brett Cannon br...@python.org wrote: http://docs.python.org/devguide/ If you are a core developer and have a correction you want to make you can simply check out the devguide yourself (link is in the Resources section of the devguide) and make the corrections yourself. Otherwise reply here (you can email me directly but I already have instances of multiple people telling me about the same spelling mistake so it's nice to have it public so people know when I have been informed). As for what is left to do, there are a a few things. One is fixing some issues to allow test coverage to be run for the entire test suite (see the coverage docs to know what issues are tracking the problems). I will work on this next if no one beats me to it as both issues should be relatively simple to do. Two, what should the final URL be? Georg picked the current one and I am happy with it. Three, where should it be linked from? docs.python.org homepage? Four, what to do with www.python.org/dev/? Redirect for all the pages? Otherwise I consider the devguide ready to go. My next thing will be an official HOWTO on dealing with Python 2/3 porting/maintenance. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] What's new 2.x in 3.x docs.
On Sun, Jan 23, 2011 at 7:23 AM, Raymond Hettinger raymond.hettin...@gmail.com wrote: On Jan 22, 2011, at 11:04 AM, Terry Reedy wrote: The 3.x docs mostly started fresh with 3.0. The major exception is the What's new section, which goes back to 2.0. The 2.x stuff comprises about 650KB in the repository and whatever that translates into in the distribution. I cannot imagine that anyone who only has 3.x and no 2.x version would have any interest in the 2.x history. And of course, the complete 2.x history will always be available with the latest 2.7.z. And the cover page for 3.x could even say so and include a link. So why not remove it from the 3.2 release (and have two separate pages for the online version)? I think there is value in the older whatsnew docs. The provide a readable introduction to various features and nicely augment the plain docs which can be a little dry. +1 for keeping the links as-is. Removing them takes away a resource and gains nothing. They're also a useful resource when developing compatibility guides for projects that target older versions (including ones that support py3k via 2to3). With the latest 3.x release always being at the top, I agree with Raymond that retaining the history is a better option. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] What's new 2.x in 3.x docs.
On 1/22/2011 2:20 PM, Antoine Pitrou wrote: On Sat, 22 Jan 2011 14:04:00 -0500 Terry Reedytjre...@udel.edu wrote: The 3.x docs mostly started fresh with 3.0. The major exception is the What's new section, which goes back to 2.0. The 2.x stuff comprises about 650KB in the repository and whatever that translates into in the distribution. I cannot imagine that anyone who only has 3.x and no 2.x version would have any interest in the 2.x history. And of course, the complete 2.x history will always be available with the latest 2.7.z. And the cover page for 3.x could even say so and include a link. So why not remove it from the 3.2 release (and have two separate pages for the online version)? Well, is there any point in doing so, apart from saving 650KB in the repository? I'm not sure we care about the latter (right now the whole source tree is more than 50MB, and that's without version control information). I was only proposing actual removal of what to me is noise from the windows help file (now 5.6 mb) with a link to the online version. But the idea is rejected. Fini. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] build problem
Hello I got the latest copy of python source from svn and was trying to build it on Windows Vista (32 bit) using Microsoft Visual Express 2008. I got the following error: 5C:\Program Files\TortoiseSVN\bin\subwcrev.exe .. ..\Modules\getbuildinfo.c E:\coding\py3kclean\py3k\PCbuild\Win32-temp-Debug\pythoncore\\getbuildinfo2.c 5'C:\Program' is not recognized as an internal or external command, Adding an extra set of quotes around the command seems to fix this. I've attached a patch. Thanks Prasun buildinfo.patch Description: Binary data ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
