Re: [Python-Dev] 2.3.6 for the unicode buffer overrun
Martin v. Löwis wrote: In 2.3.6, there wouldn't just be that change, but also a few other changes that have been collected, some relevant for Windows as well why not just do a 2.3.5+security source release, and leave the rest to the downstream maintainers? /F ___ 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] 2.3.6 for the unicode buffer overrun
On Tuesday 17 October 2006 18:54, Fredrik Lundh wrote: Martin v. L�wis wrote: In 2.3.6, there wouldn't just be that change, but also a few other changes that have been collected, some relevant for Windows as well why not just do a 2.3.5+security source release, and leave the rest to the downstream maintainers? I think we'd need to renumber it to 2.3.6 at least, otherwise there's the problem of distinguishing between the two. I'd _hope_ that all the downstreams will have picked up the patch (if you know of someone who hasn't, let me know and I'll kick them for you if it would help). But I'm certainly thinking if there's a 2.3.6, it's going to be 2.3.5 with the email fix and the unicode repr() fix, and that's it. No windows or Mac binaries - they'll be pointed to the perfectly fine 2.3.5 binary installers. And no, I'm not doing another 2.2 release :) ___ 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] 2.3.6 for the unicode buffer overrun
Anthony Baxter wrote: why not just do a 2.3.5+security source release, and leave the rest to the downstream maintainers? I think we'd need to renumber it to 2.3.6 at least, otherwise there's the problem of distinguishing between the two. I'd _hope_ that all the downstreams will have picked up the patch (if you know of someone who hasn't, let me know and I'll kick them for you if it would help). in my experience, downstream builders tend to deal with patches just fine; I'm more worried about people who build directly from tarballs (using the good old wget, tar xvfz, configure, make mental macro) But I'm certainly thinking if there's a 2.3.6, it's going to be 2.3.5 with the email fix and the unicode repr() fix, and that's it. sounds good to me. how much work would that be, and if you're willing to coordinate, is there anything we can do to help? /F ___ 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] 2.3.6 for the unicode buffer overrun
On Tuesday 17 October 2006 19:09, Fredrik Lundh wrote: But I'm certainly thinking if there's a 2.3.6, it's going to be 2.3.5 with the email fix and the unicode repr() fix, and that's it. sounds good to me. how much work would that be, and if you're willing to coordinate, is there anything we can do to help? Less than a normal release, since I'm not going to worry about changing the docs, the windows installers or the mac installers. I'll look at it next week, once 2.4.4 final is done. Anthony -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
Martin v. Löwis wrote: Steve Holden schrieb: The other thing to watch out for is that I (or whoever) can still do local work on a bunch of different files the point of my previous post is that you *shouldn't* have to edit a bunch of different files to make a new release. Indeed. I seem to remember suggesting a while ago on pydotorg that whatever replaces pyramid should cater to groups such as the release team by allowing everything necessary to be generated from a simple set of data that wouldn't be difficult to maintain. Anthony has enough on his plate without having to fight the web server too ... There is always some sort of text that accompanies a release. That has to be edited to be correct; a machine can't do that. OK. ^everything^the content structure and many of the files^ regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://holdenweb.blogspot.com Recent Ramblings http://del.icio.us/steve.holden ___ 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] 2.3.6 for the unicode buffer overrun
On Sunday 15 October 2006 21:23, Steve Holden wrote: Martin v. Löwis wrote: Steve Holden schrieb: The other thing to watch out for is that I (or whoever) can still do local work on a bunch of different files the point of my previous post is that you *shouldn't* have to edit a bunch of different files to make a new release. Indeed. I seem to remember suggesting a while ago on pydotorg that whatever replaces pyramid should cater to groups such as the release team by allowing everything necessary to be generated from a simple set of data that wouldn't be difficult to maintain. Anthony has enough on his plate without having to fight the web server too ... There is always some sort of text that accompanies a release. That has to be edited to be correct; a machine can't do that. OK. ^everything^the content structure and many of the files^ If you compare the various pieces that make up the release pages, you'll see that much of it is boilerplate, true. There's two cases worth mentioning: First release of a new series (2.4.4c1, 2.5a1). This involves making the new directory and all the little fiddly files. In practice, this is done by recursively copying the previous release and removing the .ssh directories so that it can be re-added. I then go through and update the files. Subsequent release. This is still largely a manual process - I search for all the references to the previous release, update them, then read through it for missed bits. I then update the text bits that need to be changed. There's all sorts of minor variations there - for instance, often in a non-final release, we don't have an unpacked version of the documentation (but sometimes we do, wah). The killer bits for me are all the other places. For instance, updating the sidebar menu quicklinks for 2.4.4 to 2.5. There's just too many files, and the structure of pyramid's files still doesn't make sense to me. Anthony -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
Anthony Baxter schrieb: Subsequent release. This is still largely a manual process - I search for all the references to the previous release, update them, then read through it for missed bits. I then update the text bits that need to be changed. There's all sorts of minor variations there - for instance, often in a non-final release, we don't have an unpacked version of the documentation (but sometimes we do, wah). If that's a source of pain, we can standardize (assuming you are talking about the .chm file). Which way would you like it? It really doesn't matter to me either way - I just didn't think of it causing problems. Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
Josiah Carlson schrieb: I've got a build setup for 2.3.x, but I lack the Wise Installer. It may be possible to use the 2.4 or 2.5 .msi creation tools, if that was sufficient. I don't think that would be appropriate. There are differences in usage which might be significant to some users, e.g. in automated install scenarios. We should attempt not to break this. Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
Brett Cannon wrote: I know AMK was experimenting with rest2web as a possible way to do the web site. There has also been talk about trying out another system. But I also know some people would rather put the effort into improving Pyramid. You forgot the ponies! Once again, it's a matter of people putting the time in to make a switch happen to a system that the site maintainers would be happy with. The people behind the current system and process has invested way too much energy and prestige in the current system to ever accept that the result is pretty lousy as a site, and complete rubbish as technology. It's about sunk costs, not cost- and time-effective solutions. For reference, here's my effbot.org release procedure: 1) upload the distribution files one by one, as soon as they're available. all links and stuff will appear automatically 2) update the associated description text through the web, when necessary, as an HTML fragment. click save to publish. 3) mail out an announcement when everything looks good. Maybe I should offer Anthony to do the releases via effbot.org instead? /F ___ 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] 2.3.6 for the unicode buffer overrun
Anthony Baxter wrote: The other thing to watch out for is that I (or whoever) can still do local work on a bunch of different files the point of my previous post is that you *shouldn't* have to edit a bunch of different files to make a new release. /F ___ 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] 2.3.6 for the unicode buffer overrun
For reference, here's my effbot.org release procedure: 1) upload the distribution files one by one, as soon as they're available. all links and stuff will appear automatically 2) update the associated description text through the web, when necessary, as an HTML fragment. click save to publish. 3) mail out an announcement when everything looks good. Maybe I should offer Anthony to do the releases via effbot.org instead? First off - I'm not going to be posting 10M or 16M files through a web-browser. That's insane :-) The bit of the website that's dealing with the actual files is not the tricky bit - I have a dinky little python script that generates the download table. The problems are with the other bits of the pages. I keep thinking next release, I'll automate it further, but never have time on the day. -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
Anthony Baxter wrote: For reference, here's my effbot.org release procedure: 1) upload the distribution files one by one, as soon as they're available. all links and stuff will appear automatically 2) update the associated description text through the web, when necessary, as an HTML fragment. click save to publish. 3) mail out an announcement when everything looks good. Maybe I should offer Anthony to do the releases via effbot.org instead? First off - I'm not going to be posting 10M or 16M files through a web-browser. That's insane :-) oh, I only edit the pages through the web, not the files. there's nothing wrong with scp or sftp or rsync-over-ssh or whatever you're using today. The bit of the website that's dealing with the actual files is not the tricky bit - I have a dinky little python script that generates the download table. yeah, but *you* are doing it. if the server did that, Martin and other trusted contributors could upload the files as soon as they're available, instead of first transferring them to you, and then waiting for you to find yet another precious time slot to spend on this release. The problems are with the other bits of the pages. I keep thinking next release, I'll automate it further, but never have time on the day. that's why you have to have an overall infrastructure that lets you make incremental tweaks to the tool chain, so things can get a little better all the time. Pyramid obviously isn't such a system. /F ___ 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] 2.3.6 for the unicode buffer overrun
On Friday 13 October 2006 16:59, Fredrik Lundh wrote: yeah, but *you* are doing it. if the server did that, Martin and other trusted contributors could upload the files as soon as they're available, instead of first transferring them to you, and then waiting for you to find yet another precious time slot to spend on this release. Sure - I get that. There's a couple of reasons for me doing it. First is gpg signing the release files, which has to happen on my local machine. There's also the variation in who actually builds the releases; at least one of the Mac builds was done by Bob I. But there could be ways around this. I don't want to have to ensure every builder has scp, and I'd also prefer for it to all go live at once. A while back, the Mac installer would follow up some time after the Windows and source builds. Every release, I'd get emails saying where's the mac build?! The problems are with the other bits of the pages. I keep thinking next release, I'll automate it further, but never have time on the day. that's why you have to have an overall infrastructure that lets you make incremental tweaks to the tool chain, so things can get a little better all the time. Pyramid obviously isn't such a system. I can't disagree with this. -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
On 10/13/06, Anthony Baxter [EMAIL PROTECTED] wrote: On Friday 13 October 2006 16:59, Fredrik Lundh wrote: yeah, but *you* are doing it. if the server did that, Martin and other trusted contributors could upload the files as soon as they're available, instead of first transferring them to you, and then waiting for you to find yet another precious time slot to spend on this release. Sure - I get that. There's a couple of reasons for me doing it. First is gpg signing the release files, which has to happen on my local machine. There's also the variation in who actually builds the releases; at least one of the Mac builds was done by Bob I. But there could be ways around this. I don't want to have to ensure every builder has scp, and I'd also prefer for it to all go live at once. A while back, the Mac installer would follow up some time after the Windows and source builds. Every release, I'd get emails saying where's the mac build?! With most consumer connections it's a lot faster to download than to upload. Perhaps it would save you a few minutes if the contributors uploaded directly to the destination (or to some other fast server) and you could download and sign it, rather than having to scp it back up somewhere from your home connection. To be fair, (thanks to Ronald) the Mac build is entirely automated by a script with the caveat that you should be a little careful about what your environment looks like (e.g. don't install fink or macports, or to move them out of the way when building). It downloads all of the third party dependencies, builds them with some special flags to make it universal, builds Python, and then wraps it up in an installer package. Given any Mac OS X 10.4 machine, the builds could happen automatically. Apple could probably provide one if someone asked. They did it for Twisted. Or maybe the Twisted folks could appropriate part of that machine's time to also build Python. -bob ___ 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] 2.3.6 for the unicode buffer overrun
On Friday 13 October 2006 20:35, Bob Ippolito wrote: With most consumer connections it's a lot faster to download than to upload. Perhaps it would save you a few minutes if the contributors uploaded directly to the destination (or to some other fast server) and you could download and sign it, rather than having to scp it back up somewhere from your home connection. I actually pull them down to both dinsdale and home, then verify they're the same with SHA and MD5 before signing, and uploading the keys. The only thing I upload directly are the keys and the source tarballs. Given any Mac OS X 10.4 machine, the builds could happen automatically. Apple could probably provide one if someone asked. They did it for Twisted. Or maybe the Twisted folks could appropriate part of that machine's time to also build Python. We have one, macteagle. For some reason builds fail on it right now - Ronald might be able to supply more details as to why. Anthony -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
Martin v. Löwis schrieb: Anthony Baxter schrieb: Mostly it is easy for me, with the one huge caveat. As far as I know, the Mac build is a single command to run for Ronald, and the Doc build similarly for Fred. I don't know what Martin has to do for the Windows build. Actually, for 2.3.x, I wouldn't do the Windows builds. I think Thomas Heller did the 2.3.x series. Yes. But I've switched machines since I last build an installer, and I do not have all of the needed software installed any longer, for example the Wise Installer. Thomas ___ 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] 2.3.6 for the unicode buffer overrun
On Friday, October 13, 2006, at 01:10PM, Anthony Baxter [EMAIL PROTECTED] wrote: On Friday 13 October 2006 20:35, Bob Ippolito wrote: With most consumer connections it's a lot faster to download than to upload. Perhaps it would save you a few minutes if the contributors uploaded directly to the destination (or to some other fast server) and you could download and sign it, rather than having to scp it back up somewhere from your home connection. I actually pull them down to both dinsdale and home, then verify they're the same with SHA and MD5 before signing, and uploading the keys. The only thing I upload directly are the keys and the source tarballs. Given any Mac OS X 10.4 machine, the builds could happen automatically. Apple could probably provide one if someone asked. They did it for Twisted. Or maybe the Twisted folks could appropriate part of that machine's time to also build Python. We have one, macteagle. For some reason builds fail on it right now - Ronald might be able to supply more details as to why. IIRC it has the wrong version of Xcode installed (or rather another one than I use and test with). It also has darwinports installed at the default location, which can cause problems because the setup.py adds that directory to the include/link paths. I don't want to release installers that require that the user has darwinports installed :-) I can supply a newer version of Xcode if someone with an admin account is willing to install that. I don't know if the admin of that machine has GUI access to the machine, if not I'd have to investigate how to ensure that the proper subpackages get installed using a command-line install (using RemoteDesktop to administrator servers has spoiled me a bit in that regard). I guess this comes down to the usual problem: I have a working setup for building the mac installer and fixing macteagle takes time which I don't have available in great amounts (who does?). Ronald ___ 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] 2.3.6 for the unicode buffer overrun
On Friday, October 13, 2006, at 12:36PM, Bob Ippolito [EMAIL PROTECTED] wrote: To be fair, (thanks to Ronald) the Mac build is entirely automated by a script with the caveat that you should be a little careful about what your environment looks like (e.g. don't install fink or macports, or to move them out of the way when building). That (the don't install Fink or macports part) is because setup.py explicitly adds those directories to the library and include search path. IMHO that is a misfeature because it is much to easy to accidently contaminate a build that way. Fink and macports can easily add their directories to the search paths using OPTS and LDFLAGS, there's no need to automate this in setup.py. The beauty of macports is that /opt/local is the default prefix, but you can easily pick another prefix and most ports work fine that way (or rather not worse than with the default prefix). Ronald ___ 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] 2.3.6 for the unicode buffer overrun
Fredrik Lundh wrote: Anthony Baxter wrote: The other thing to watch out for is that I (or whoever) can still do local work on a bunch of different files the point of my previous post is that you *shouldn't* have to edit a bunch of different files to make a new release. Indeed. I seem to remember suggesting a while ago on pydotorg that whatever replaces pyramid should cater to groups such as the release team by allowing everything necessary to be generated from a simple set of data that wouldn't be difficult to maintain. Anthony has enough on his plate without having to fight the web server too ... regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://holdenweb.blogspot.com Recent Ramblings http://del.icio.us/steve.holden ___ 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] 2.3.6 for the unicode buffer overrun
Fredrik Lundh wrote: Brett Cannon wrote: I know AMK was experimenting with rest2web as a possible way to do the web site. There has also been talk about trying out another system. But I also know some people would rather put the effort into improving Pyramid. You forgot the ponies! Once again, it's a matter of people putting the time in to make a switch happen to a system that the site maintainers would be happy with. The people behind the current system and process has invested way too much energy and prestige in the current system to ever accept that the result is pretty lousy as a site, and complete rubbish as technology. It's about sunk costs, not cost- and time-effective solutions. I don't believe that's true, but I'm certainly not the one with the most time invested in pyramid. Tim Parkin is on record as saying he'd be willing to help with a(nother) migration project. I think there's a general appreciation of pyramid's strangths *and* deficiencies. For reference, here's my effbot.org release procedure: 1) upload the distribution files one by one, as soon as they're available. all links and stuff will appear automatically 2) update the associated description text through the web, when necessary, as an HTML fragment. click save to publish. 3) mail out an announcement when everything looks good. Maybe I should offer Anthony to do the releases via effbot.org instead? You can try. Or you can start to promote Django again ... regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://holdenweb.blogspot.com Recent Ramblings http://del.icio.us/steve.holden ___ 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] 2.3.6 for the unicode buffer overrun
Steve Holden schrieb: The other thing to watch out for is that I (or whoever) can still do local work on a bunch of different files the point of my previous post is that you *shouldn't* have to edit a bunch of different files to make a new release. Indeed. I seem to remember suggesting a while ago on pydotorg that whatever replaces pyramid should cater to groups such as the release team by allowing everything necessary to be generated from a simple set of data that wouldn't be difficult to maintain. Anthony has enough on his plate without having to fight the web server too ... There is always some sort of text that accompanies a release. That has to be edited to be correct; a machine can't do that. Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
Martin v. Löwis [EMAIL PROTECTED] wrote: Thomas Heller schrieb: Yes. But I've switched machines since I last build an installer, and I do not have all of the needed software installed any longer, for example the Wise Installer. Ok. So we are technically incapable of producing the Windows binaries of another 2.3.x release, then? I've got a build setup for 2.3.x, but I lack the Wise Installer. It may be possible to use the 2.4 or 2.5 .msi creation tools, if that was sufficient. - Josiah ___ 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] 2.3.6 for the unicode buffer overrun
[Thomas Heller] Yes. But I've switched machines since I last build an installer, and I do not have all of the needed software installed any longer, for example the Wise Installer. [Martin v. Löwis] Ok. So we are technically incapable of producing the Windows binaries of another 2.3.x release, then? FYI, I still have the Wise Installer. But since my understanding is that the Unicode buffer overrun thingie is a non-issue on Windows, I've got no interest in wrestling with a 2.3.6 for Windows. ___ 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] 2.3.6 for the unicode buffer overrun
Tim Peters schrieb: FYI, I still have the Wise Installer. But since my understanding is that the Unicode buffer overrun thingie is a non-issue on Windows, I've got no interest in wrestling with a 2.3.6 for Windows. In 2.3.6, there wouldn't just be that change, but also a few other changes that have been collected, some relevant for Windows as well: there are several updates to the email package, and a fix to pcre to prevent a buffer overrun. I'm not saying that you should produce a Windows binary then, just that it would be good if one was produced if there was another release. Of course, people might also get the binaries from ActiveState should they produce some. Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
I've had a couple of queries about whether PSF-2006-001 merits a 2.3.6. Personally, I lean towards no - 2.4 was nearly two years ago now. But I'm open to other opinions - I guess people see the phrase buffer overrun and they get scared. Plus once 2.4.4 final is out next week, I'll have cut 12 releases since March. Assuming a 2.5.1 before March (very likely) that'll be 14 releases in 12 months. 16 releases in 12 months would just about make me go crazy. ___ 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] 2.3.6 for the unicode buffer overrun
Anthony Baxter wrote: 16 releases in 12 months would just about make me go crazy. is there any way we could further automate or otherwise streamline or distribute the release process ? ideally, releasing (earlier release + well-defined patch set) should be fairly trivial, compared to releasing (new release from trunk). what do we have to do to make it easier to handle that case? /F ___ 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] 2.3.6 for the unicode buffer overrun
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 12, 2006, at 4:08 AM, Anthony Baxter wrote: I've had a couple of queries about whether PSF-2006-001 merits a 2.3.6. Personally, I lean towards no - 2.4 was nearly two years ago now. But I'm open to other opinions - I guess people see the phrase buffer overrun and they get scared. Plus once 2.4.4 final is out next week, I'll have cut 12 releases since March. Assuming a 2.5.1 before March (very likely) that'll be 14 releases in 12 months. 16 releases in 12 months would just about make me go crazy. I've offered in the past to dust off my release manager cap and do a 2.3.6 release. Having not done one in a long while, the most daunting part for me is getting the website updated, since I have none of those tools installed. I'm still willing to do a 2.3.6, though the last time this came up the response was too underwhelming to care. I'm not sure this advisory is enough to change people's minds about that -- I'm sure any affected downstream distro is fully capable of patching and re- releasing their own packages. Since this doesn't affect the binaries /we/ release, I'm not sure I care enough either. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRS5hD3EjvBPtnXfVAQIlLgP/Rz5ahaeus0VLJT0HmyZUYBf07Crr2e1K KgCoEDqXZq+LyF7B8bqokXZ4uFisBbQTREM3d+8vYEHC9kcQpt0FurkSFc47G0gj rJvm0XbGkhXFGdPqrTwUoT033f/bhabpEILDkNJx6bB+Jk5G23EyTKRRDB531QvY qC6ttgGRfVA= =dECg -END PGP SIGNATURE- ___ 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] 2.3.6 for the unicode buffer overrun
Barry Warsaw [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- I've offered in the past to dust off my release manager cap and do a 2.3.6 release. Having not done one in a long while, the most daunting part for me is getting the website updated, since I have none of those tools installed. I'm still willing to do a 2.3.6, though the last time this came up the response was too underwhelming to care. I'm not sure this advisory is enough to change people's minds about that -- I'm sure any affected downstream distro is fully capable of patching and re- releasing their own packages. Since this doesn't affect the binaries /we/ release, I'm not sure I care enough either. Perhaps all that is needed from both a practical and public relations viewpoint is the release of a 2.3.5U4 security patch as a separate file listed just after 2.3.5 on the source downloads page (if this has not been done already). Add a note (or link to a note) to the effect that it should be applied if one has or is going to compile a wide Unicode build for use in an environment exposed to untrusted Unicode text. tjr ___ 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] 2.3.6 for the unicode buffer overrun
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 12, 2006, at 1:34 PM, Terry Reedy wrote: Perhaps all that is needed from both a practical and public relations viewpoint is the release of a 2.3.5U4 security patch as a separate file listed just after 2.3.5 on the source downloads page (if this has not been done already). I don't currently have the ability to update the website, but I think the download page should have a big red star that points to the security patch. The 2.3.5 page should probably be updated with a link to the patch too. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRS6BjnEjvBPtnXfVAQKssAQAnrgoMFbuAQRFSAReCYLBovsXJK481NdB gTk/gaAAXe15Ko+HN0gr1EF7Mpd9a8h+5UaWyiQo+2dEJFPYr8LKcLhVLRO75jwK A7oeXl859cUjwVK1Lc6uR/gFXUIhCsd8kujKb3lE71K6ygVtcqHwxr4OcMlMe/+j YExPu6zELjk= =NcuJ -END PGP SIGNATURE- ___ 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] 2.3.6 for the unicode buffer overrun
On Thursday 12 October 2006 18:18, Fredrik Lundh wrote: Anthony Baxter wrote: 16 releases in 12 months would just about make me go crazy. is there any way we could further automate or otherwise streamline or distribute the release process ? It's already pretty heavily automated (see welease.py in the SVN sandbox). The killer problem is pyramid (the system for the website). Here's (roughly) a breakdown of the workload: - Update the 10 or so files that need the date and version number (about 3m) - Run welease.py, select the branch, enter the version number, press 4 buttons, one after the other. It complains and stops if something goes wrong. (elapsed time about 5-10m, actual work time 30s) - Wait for the Mac/Win/Doc builders (elapsed, 6-12h, depending on timezones, actual work time 0s) - Sign binaries and put in place on website (maybe 2m work, plus 5-10m to scp up to dinsdale) - Update webpages (between 30m and an hour, depending on how much I have to fight with pyramid. I still need to go update the old release pages putting the warnings on them, so there's probably another hour of work today) I've mentioned this on pydotorg enough times, I don't feel I can continue to complain about it (because I can't offer the time to make it better) but pyramid is *not* *good* from my point of view. The older system with Makefiles, ht2html and rsync took maybe 1/4 to 1/3 as long. ideally, releasing (earlier release + well-defined patch set) should be fairly trivial, compared to releasing (new release from trunk). what do we have to do to make it easier to handle that case? Mostly it is easy for me, with the one huge caveat. As far as I know, the Mac build is a single command to run for Ronald, and the Doc build similarly for Fred. I don't know what Martin has to do for the Windows build. -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 12, 2006, at 3:27 PM, Anthony Baxter wrote: Mostly it is easy for me, with the one huge caveat. As far as I know, the Mac build is a single command to run for Ronald, and the Doc build similarly for Fred. I don't know what Martin has to do for the Windows build. Why can't we get buildbot to do most or all of this? At work, we have buildbot slaves that post installers to a share after successful checkout, build, and test on all our supported platforms. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRS6k2HEjvBPtnXfVAQJeawP7BTqVw7tN80h5lB5UZp4MuN2Q/3KWapIi lYZeBqoaiouXKIkKsHbCVb1/OeZQRnDwEqWPu0xKfzlteYUchmDh2h53nzfynyyS PdJ5FaKcAk0LBjR0JsSZKd6TEWxKZZHs04V2LiKZpmsICG8g7uH954wleyGLTl2h 7VZ1aVxGuko= =1Ito -END PGP SIGNATURE- ___ 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] 2.3.6 for the unicode buffer overrun
On Oct 12, 2006, at 10:25 PM, Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 12, 2006, at 3:27 PM, Anthony Baxter wrote: Mostly it is easy for me, with the one huge caveat. As far as I know, the Mac build is a single command to run for Ronald, and the Doc build similarly for Fred. I don't know what Martin has to do for the Windows build. Why can't we get buildbot to do most or all of this? At work, we have buildbot slaves that post installers to a share after successful checkout, build, and test on all our supported platforms. The windows build is a single command, but I test the output on 3 different platforms (10.3/ppc, 10.4/ppc and 10.4/x86). If buildbot supports such a configuration I'd be very interested (and not just for Python itself). Ronald smime.p7s Description: S/MIME cryptographic signature ___ 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] 2.3.6 for the unicode buffer overrun
On Friday 13 October 2006 06:25, Barry Warsaw wrote: On Oct 12, 2006, at 3:27 PM, Anthony Baxter wrote: Mostly it is easy for me, with the one huge caveat. As far as I know, the Mac build is a single command to run for Ronald, and the Doc build similarly for Fred. I don't know what Martin has to do for the Windows build. Why can't we get buildbot to do most or all of this? At work, we have buildbot slaves that post installers to a share after successful checkout, build, and test on all our supported platforms. Speaking for myself, I'd rather do it by hand, if it's not a lot of work (which it isn't) - I don't like the idea of official releases just being an automated thing. If you're instead just talking about daily builds, maybe, but we'd need to have some new way to do versioning for these. -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
Barry Warsaw schrieb: Why can't we get buildbot to do most or all of this? Very easy. Because somebody has to set it up. I estimate a man month or so before it works. Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
Anthony Baxter schrieb: Mostly it is easy for me, with the one huge caveat. As far as I know, the Mac build is a single command to run for Ronald, and the Doc build similarly for Fred. I don't know what Martin has to do for the Windows build. Actually, for 2.3.x, I wouldn't do the Windows builds. I think Thomas Heller did the 2.3.x series. Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 12, 2006, at 4:08 AM, Anthony Baxter wrote: I've had a couple of queries about whether PSF-2006-001 merits a 2.3.6. Personally, I lean towards no - 2.4 was nearly two years ago now. But I'm open to other opinions - I guess people see the phrase buffer overrun and they get scared. Plus once 2.4.4 final is out next week, I'll have cut 12 releases since March. Assuming a 2.5.1 before March (very likely) that'll be 14 releases in 12 months. 16 releases in 12 months would just about make me go crazy. I've offered in the past to dust off my release manager cap and do a 2.3.6 release. Having not done one in a long while, the most daunting part for me is getting the website updated, since I have none of those tools installed. I'm I the only one who feels that the website is a big workflow problem? Georg ___ 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] 2.3.6 for the unicode buffer overrun
Fredrik Lundh schrieb: ideally, releasing (earlier release + well-defined patch set) should be fairly trivial, compared to releasing (new release from trunk). what do we have to do to make it easier to handle that case? For the Windows release, I doubt there is much one can do. The time-consuming part is to run the MSI file, on three different architectures, and in various combinations (admin/no-admin, default directory/Program Files, upgrade/no-upgrade). I don't always do all of them, but still it takes a while; I usually need an hour to make a release. Plus, sometimes something goes wrong: there might a backport that doesn't work on Windows, or it might be that I broke my build environment somehow (which I normally keep across releases - if I have to start from scratch on a fresh machine, it takes much longer: a day or so). Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
On Fri, Oct 13, 2006 at 06:43:40AM +1000, Anthony Baxter wrote: On Friday 13 October 2006 06:25, Barry Warsaw wrote: On Oct 12, 2006, at 3:27 PM, Anthony Baxter wrote: Mostly it is easy for me, with the one huge caveat. As far as I know, the Mac build is a single command to run for Ronald, and the Doc build similarly for Fred. I don't know what Martin has to do for the Windows build. Why can't we get buildbot to do most or all of this? At work, we have buildbot slaves that post installers to a share after successful checkout, build, and test on all our supported platforms. Speaking for myself, I'd rather do it by hand, if it's not a lot of work (which it isn't) - I don't like the idea of official releases just being an automated thing. IMHO thats a backwards view; I'm with Barry. Requiring human intervention to do anything other than press the big green go button to launch the official release build process is an opportunity for human error. the same goes for testing the built release installers and tarballs. three macs with some virtual machines could take care of this (damn apple for not allowing their stupid OS to be virtualized). that said, i'm not volunteering to setup an automated system for this but i've got good ideas how to do it if i ever find time or someone wants to chat offline. :( as for buildbot, i haven't looked at its design but from the chatter i've seen i was under the impression that it operates on a continually updated sandbox rather than a 100% fresh checkout for each build? if thats true (is it?) i'd prefer to see a build system setup to do a fresh checkout+build of everything (including externals) in a new directory for each build in use. thats what we do at work. none of the above even considers the web site updating problem.. greg ___ 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] 2.3.6 for the unicode buffer overrun
On Thu, Oct 12, 2006 at 09:30:49PM +0200, Georg Brandl wrote: Barry Warsaw wrote: I've offered in the past to dust off my release manager cap and do a 2.3.6 release. Having not done one in a long while, the most daunting part for me is getting the website updated, since I have none of those tools installed. I'm I the only one who feels that the website is a big workflow problem? nope, you're not. ___ 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] 2.3.6 for the unicode buffer overrun
Gregory P. Smith schrieb: three macs with some virtual machines could take care of this (damn apple for not allowing their stupid OS to be virtualized). that said, i'm not volunteering to setup an automated system for this but i've got good ideas how to do it if i ever find time or someone wants to chat offline. :( Of course, that makes the idea die here and now. Without volunteers to do the actual work, it just won't happen. as for buildbot, i haven't looked at its design but from the chatter i've seen i was under the impression that it operates on a continually updated sandbox rather than a 100% fresh checkout for each build? if thats true (is it?) i'd prefer to see a build system setup to do a fresh checkout+build of everything (including externals) in a new directory for each build in use. thats what we do at work. Buildbot could do that easily; in fact, I had to explicitly configure it to not start from scratch each time, to reduce the network traffic of the donated machines. Regards, Martin ___ 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] 2.3.6 for the unicode buffer overrun
On Friday 13 October 2006 05:30, Georg Brandl wrote: I'm I the only one who feels that the website is a big workflow problem? Assuming you meant Am I, then I absolutely agree with you. -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 12, 2006, at 5:03 PM, Gregory P. Smith wrote: IMHO thats a backwards view; I'm with Barry. Requiring human intervention to do anything other than press the big green go button to launch the official release build process is an opportunity for human error. the same goes for testing the built release installers and tarballs. Oh yes, that's an important step I forgot to mention. At work, we also run automated tests of the built installers, so we have a high degree of confidence that what our buildbot farm produces at least passes the sniff test (/then/ our QA dept takes over from there). The files we upload then are named by product, platform, version, revision id, and date. It takes a manual step to delete old builds, but we have big disks so we generally don't do that except for EOL'd versions. The nice thing about that is that you can go back to almost any build and pull down a working installer. Greg hints at a major benefit of this: the knowledge for how to successfully build products is contained in scripts that are themselves revision controlled. A wiki page providing an overview and the starting points are still needed but rarely consulted. i'm not volunteering to setup an automated system for this but i've got good ideas how to do it if i ever find time or someone wants to chat offline. :( I wish I had the cycles to volunteer to help out implementing this. :( - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRS608nEjvBPtnXfVAQIypAQAtiantWJkvStPYR8tnl+AU+HzI7bZ54s1 oX8Ni0/1IbZQwYloV6UMmhwisirZ5bwAtNWfZnd3UQXFhrCC1MGlRMOWP/y6AwS2 /gSzUV9A1dxUE9iVdPy50gEMFrzrZ32g16+FsHzae/9FgklB+GjogAuYmr2vbxd4 SrB1dgEHnXg= =6rIv -END PGP SIGNATURE- ___ 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] 2.3.6 for the unicode buffer overrun
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 12, 2006, at 5:07 PM, Martin v. Löwis wrote: Of course, that makes the idea die here and now. Without volunteers to do the actual work, it just won't happen. True, and there's no carrot/stick of a salary to entice people into doing what is mostly thankless grunt work. ;) OTOH, there's always new blood with lots of time on there hands coming into the community looking for a way to distinguish themselves (read: students :). Maybe someone will step forward and win a little lemony slice of net.fame. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRS610nEjvBPtnXfVAQKtiwP/a+BfIhLupcDQwfY6AhXNxjvnh+scjqTd nutSPfHR8qdbDxAxq6YcBkMeIh55XP0QSu+gYSdDDj9dGkIP0FGhurpZVW1WFrye KEBapAmnPUnC8X5kAj0Wrw6BXacchilrH3cpC1psDtlT58TgAsUxtjmYsSKEI0ZP l+tx3jlp2Ck= =vbwS -END PGP SIGNATURE- ___ 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] 2.3.6 for the unicode buffer overrun
On 10/12/06, Anthony Baxter [EMAIL PROTECTED] wrote: On Friday 13 October 2006 05:30, Georg Brandl wrote: I'm I the only one who feels that the website is a big workflow problem?Assuming you meant Am I, then I absolutely agree with you. I have touched the web site since the Pyramid switch and thus am not that active, so what I am about to say may be slightly off, but ...I know AMK was experimenting with rest2web as a possible way to do the web site. There has also been talk about trying out another system. But I also know some people would rather put the effort into improving Pyramid. Once again, it's a matter of people putting the time in to make a switch happen to a system that the site maintainers would be happy with.-Brett ___ 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] 2.3.6 for the unicode buffer overrun
Brett Cannon wrote: On 10/12/06, *Anthony Baxter* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: On Friday 13 October 2006 05:30, Georg Brandl wrote: I'm I the only one who feels that the website is a big workflow problem? Assuming you meant Am I, then I absolutely agree with you. I have touched the web site since the Pyramid switch and thus am not that active, so what I am about to say may be slightly off, but ... I know AMK was experimenting with rest2web as a possible way to do the web site. +1 for rest2web ;-) There has also been talk about trying out another system. But I also know some people would rather put the effort into improving Pyramid. Actually from the little I looked at it, pyramid seemed a very good system. Particularly the SVN integration. If rest2web is a serious option and needs any customisation, I'd be happy to look into it. Michael Foord Once again, it's a matter of people putting the time in to make a switch happen to a system that the site maintainers would be happy with. -Brett ___ 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/fuzzyman%40voidspace.org.uk No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.2/472 - Release Date: 11/10/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.2/472 - Release Date: 11/10/2006 ___ 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] 2.3.6 for the unicode buffer overrun
On Friday 13 October 2006 07:34, Barry Warsaw wrote: i'm not volunteering to setup an automated system for this but i've got good ideas how to do it if i ever find time or someone wants to chat offline. :( I wish I had the cycles to volunteer to help out implementing this. :( Well, regardless of anything else, without someone doing it, it's not going to happen. I don't have the time to spend doing this. Right now, the amount of work this would save me is minimal, so I also have little or no incentive to do it. The thing that does take the time is the website - fixing that is a major investment of time, which I also don't have. Yes, had I spent the probably 20+ hours I've spent doing website stuff I could have made it a bit better, but that's what I know _now_ :) -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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] 2.3.6 for the unicode buffer overrun
Michael Foord wrote: Brett Cannon wrote: On 10/12/06, *Anthony Baxter* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: On Friday 13 October 2006 05:30, Georg Brandl wrote: I'm I the only one who feels that the website is a big workflow problem? Assuming you meant Am I, then I absolutely agree with you. I have touched the web site since the Pyramid switch and thus am not that active, so what I am about to say may be slightly off, but ... I know AMK was experimenting with rest2web as a possible way to do the web site. +1 for rest2web ;-) There has also been talk about trying out another system. But I also know some people would rather put the effort into improving Pyramid. Actually from the little I looked at it, pyramid seemed a very good system. Particularly the SVN integration. The real problem is the more or less complete lack of incremental rebuild, which does make site generation time-consuming. The advantage of pyramid implementation was the regularisation of the site data. I think we probably need to look at taking the now more-or-less regular data structures used to drive pyramid and find some way to use them (still with source control, but hopefully with much less verbiage) to drive something like Django. To retain the advantages of source control this might mean using scripts to generate database content from SVN-controlled data files. Or something [waves hands vaguely and steps back hopefully]. regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://holdenweb.blogspot.com Recent Ramblings http://del.icio.us/steve.holden ___ 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] 2.3.6 for the unicode buffer overrun
On Friday 13 October 2006 12:56, Steve Holden wrote: The real problem is the more or less complete lack of incremental rebuild, which does make site generation time-consuming. That's _part_ of it. There's other issues. For instance, there's probably 4 places where the list of releases is stored. Every time I do a release, I need to update all of these. If it's a new release, I also have to update the apache config for the /X.Y.Z redirect (anyone who thinks a default URL of www.python.org/download/releases/X.Y.Z is a good idea needs to quit drinking before lunchtime wink) Creating a new release area, or hell, even a new page, is a whole pile of fiddly files. These still don't make sense to me - I end up copying an existing page each time, then reading through them looking for the relevant pieces of text. Personally, I can mostly deal with the reST now, although it still trips me up on a regular basis. YAML as well is just way more complexity - I don't understand the syntax, but it appears to offer massively more than we actually use. The advantage of pyramid implementation was the regularisation of the site data. Sure - and hopefully if we go down another path we can get that out. To retain the advantages of source control this might mean using scripts to generate database content from SVN-controlled data files. Or something [waves hands vaguely and steps back hopefully]. The other thing to watch out for is that I (or whoever) can still do local work on a bunch of different files, then check it in all in one hit once it's done and checked. This was an issue I had with the various wiki-based proposals, I haven't seen many wikis that allow this. -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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