Re: [Python-Dev] Add python.exe to PATH environment variable
> But then you don't get to pass arguments to the program, > get to see the output before the window disappears, etc. Did you actually try before posting? 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] [Python-3000] Proposed revised schedule
Raymond> With the extra time, it would be worthwhile to add dbm.sqlite Raymond> to 3.0 to compensate for the loss of bsddb so that shelves Raymond> won't become useless on Windows builds. My vote is to separate 2.6 and 3.0 then come back together for 2.7 and 3.1. I'm a bit less sure about adding dbm.sqlite. Unless Josiah's version is substantially faster and more robust I think my version needs to cook a bit longer. I'm just not comfortable enough with SQLite to pronounce my version fit enough. I only intended it as a proof-of-concept, and it's clear it has some shortcomings. Skip ___ 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-3000] Proposed revised schedule
On Mon, Sep 8, 2008 at 7:07 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote: > [Guido van Rossum] >> >> Well, from the number of release blockers it sounds like another 3.0 >> beta is the right thing. For 2.6 however I believe we're much closer >> to the finish line -- there aren't all those bytes/str issues to clean >> up, for example! And apparently the benefit of releasing on schedule >> is that we will be included in OSX. That's a much bigger deal for 2.6 >> than for 3.0 (I doubt that Apple would add two versions anyway). > > With the extra time, it would be worthwhile to add dbm.sqlite to 3.0 > to compensate for the loss of bsddb so that shelves won't become > useless on Windows builds. So get started already! :-) -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ 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-3000] Proposed revised schedule
[Guido van Rossum] Well, from the number of release blockers it sounds like another 3.0 beta is the right thing. For 2.6 however I believe we're much closer to the finish line -- there aren't all those bytes/str issues to clean up, for example! And apparently the benefit of releasing on schedule is that we will be included in OSX. That's a much bigger deal for 2.6 than for 3.0 (I doubt that Apple would add two versions anyway). With the extra time, it would be worthwhile to add dbm.sqlite to 3.0 to compensate for the loss of bsddb so that shelves won't become useless on Windows builds. 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] Add python.exe to PATH environment variable
Greg Ewing wrote: > Martin v. Löwis wrote: > >> OTOH, other things *are* available, such as registered extensions. >> For example, you don't need python on PATH to start a Python script; >> just invoking the .py file will find the Python interpreter from the >> registry. > > But then you don't get to pass arguments to the program, > get to see the output before the window disappears, etc. > I believe you are confusing the command-line PATHEXT mechanism with the Explorer/registry execution mechanism: C:\Users\sholden\Documents\dyjr>python 'python' is not recognized as an internal or external command, operable program or batch file. C:\Users\sholden\Documents\dyjr>manage.py Type 'manage.py help' for usage. regards Steve -- Steve Holden+1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ ___ 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-3000] Proposed revised schedule
Antoine Pitrou writes: > It's not only the marketing. Having both releases in lock step means the > development process is synchronized between trunk and py3k, that there is no > loss of developer focus, and that merges/backports happen quite naturally. As usual, in theory precision is infinite, but in engineering practice it's fuzzy. "Lock step" doesn't mean "as fine as you can split a second"; for 2.6/3.0 a couple of weeks separation is not going to matter. The important thing is to get right back on schedule for releasing 2.7/3.1 together (if that's the plan). Split-second precision does matter for marketing, though. ___ 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-3000] Proposed revised schedule
On Mon, Sep 8, 2008 at 5:22 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > Christian Heimes cheimes.de> writes: >> >> Ok, from the marketing perspective it's a nice catch to release 2.6 and >> 3.0 on the same day. "Python 2.6.0 and 3.0.0 released" makes a great >> headline. > > It's not only the marketing. Having both releases in lock step means the > development process is synchronized between trunk and py3k, that there is no > loss of developer focus, and that merges/backports happen quite naturally. I think that we've reached the point where very few things are merged from 2.6 to 3.0 -- I see a lot more "block" commits than "merge" commits lately. Also, the added activity in 3.0 doesn't involve merges at all, because it's all 3.0-specific. Sure, we lose the ability to add last-minute -3 warnings. But I think that's a pretty minor issue (and those warnings have a tendency to subtly break things occasionally, so we shouldn't do them last-minute anyway). > But I don't think it's an overwhelming argument either. I would value it at > around 50 euro cents, not even the price of a good croissant ;-) -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ 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-3000] Proposed revised schedule
Christian Heimes cheimes.de> writes: > > Ok, from the marketing perspective it's a nice catch to release 2.6 and > 3.0 on the same day. "Python 2.6.0 and 3.0.0 released" makes a great > headline. It's not only the marketing. Having both releases in lock step means the development process is synchronized between trunk and py3k, that there is no loss of developer focus, and that merges/backports happen quite naturally. But I don't think it's an overwhelming argument either. I would value it at around 50 euro cents, not even the price of a good croissant ;-) 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] [Python-3000] Proposed revised schedule
Guido van Rossum wrote: Well, from the number of release blockers it sounds like another 3.0 beta is the right thing. For 2.6 however I believe we're much closer to the finish line -- there aren't all those bytes/str issues to clean up, for example! And apparently the benefit of releasing on schedule is that we will be included in OSX. That's a much bigger deal for 2.6 than for 3.0 (I doubt that Apple would add two versions anyway). I'm on Guido's side. Ok, from the marketing perspective it's a nice catch to release 2.6 and 3.0 on the same day. "Python 2.6.0 and 3.0.0 released" makes a great headline. But given the chance to get Python 2.6 into the next OSX version it's fine with me to release 3.0 a couple of weeks later. Python 3.0 is not ready for a release candidate. We just fixed a bunch of memory leaks and critical errors over the last week. And don't forget Windows! The Windows builds didn't get thorough testing because we didn't provide our tests with official builds. I'm +1 for a 2.6rc and another beta of 3.0 Christian ___ 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] Add python.exe to PATH environment variable
Martin v. Löwis wrote: OTOH, other things *are* available, such as registered extensions. For example, you don't need python on PATH to start a Python script; just invoking the .py file will find the Python interpreter from the registry. But then you don't get to pass arguments to the program, get to see the output before the window disappears, etc. -- 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] [Python-3000] Proposed revised schedule
On Mon, Sep 8, 2008 at 4:13 PM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > On Mon, Sep 8, 2008 at 12:13 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: >> On Mon, Sep 8, 2008 at 6:23 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: >>> I don't think there's any way we're going to make our October 1st goal. We >>> have 8 open release critical bugs, and 18 deferred blockers. We do not have >>> a beta3 Windows installer and I don't have high hopes for rectifying all of >>> these problems in the next day or two. >>> >>> I propose that we push the entire schedule back two weeks. This means that >>> the planned rc2 on 17-September becomes our rc1. The planned final release >>> for 01-October becomes our rc2, and we release the finals on 15-October. >>> >>> - -Barry >> >> Perhaps it's time to separate the 2.6 and 3.0 release schedules? I >> don't care if the next version of OSX contains 3.0 or not -- but I do >> care about it having 2.6. > > I'm not really sure what good that would do us unless we wanted to > bring 3.0 back to the beta phase and continue to work on some larger > issues with it. I also suspect doing two separate, but close together > final releases would be more stressful than having them in lock and > step. Well, from the number of release blockers it sounds like another 3.0 beta is the right thing. For 2.6 however I believe we're much closer to the finish line -- there aren't all those bytes/str issues to clean up, for example! And apparently the benefit of releasing on schedule is that we will be included in OSX. That's a much bigger deal for 2.6 than for 3.0 (I doubt that Apple would add two versions anyway). > Just my pocket change, though. > > > > -- > Cheers, > Benjamin Peterson > "There's no place like 127.0.0.1." > -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ 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-3000] Proposed revised schedule
On Mon, Sep 8, 2008 at 12:13 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On Mon, Sep 8, 2008 at 6:23 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: >> I don't think there's any way we're going to make our October 1st goal. We >> have 8 open release critical bugs, and 18 deferred blockers. We do not have >> a beta3 Windows installer and I don't have high hopes for rectifying all of >> these problems in the next day or two. >> >> I propose that we push the entire schedule back two weeks. This means that >> the planned rc2 on 17-September becomes our rc1. The planned final release >> for 01-October becomes our rc2, and we release the finals on 15-October. >> >> - -Barry > > Perhaps it's time to separate the 2.6 and 3.0 release schedules? I > don't care if the next version of OSX contains 3.0 or not -- but I do > care about it having 2.6. I'm not really sure what good that would do us unless we wanted to bring 3.0 back to the beta phase and continue to work on some larger issues with it. I also suspect doing two separate, but close together final releases would be more stressful than having them in lock and step. Just my pocket change, though. -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1." ___ 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] bsddb
On Sep 7, 2008, at 12:04 PM, Gregory P. Smith wrote: FWIW, many years ago in the past when I asked sleepycat about this (long before oracle bought them) they said that python was considered to be the application. Using berkeleydb via python for a commercial application did not require a berkeleydb license. They also posted a FAQ on their web site which included that statement, including specifically declaring that using BerkeleyDB via Python for a commercial product did not require a commercial licence. Oh, look, it is still there: http://www.oracle.com/technology/software/products/berkeley-db/htdocs/ licensing.html """ Q. Do I have to pay for a Berkeley DB license to use it in my Perl or Python scripts? A. No, you may use the Berkeley DB open source license at no cost. The Berkeley DB open source license requires that software that uses Berkeley DB be freely redistributable. In the case of Perl or Python, that software is Perl or Python, and not your scripts. Any scripts you write are your property, including scripts that make use of Berkeley DB. None of the Perl, Python or Berkeley DB licenses place any restrictions on what you may do with them. """ Regards, Zooko --- http://allmydata.org -- Tahoe, the Least-Authority Filesystem http://allmydata.com -- back up all your files for $5/month ___ 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-3000] Proposed revised schedule
On Mon, Sep 8, 2008 at 6:23 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > I don't think there's any way we're going to make our October 1st goal. We > have 8 open release critical bugs, and 18 deferred blockers. We do not have > a beta3 Windows installer and I don't have high hopes for rectifying all of > these problems in the next day or two. > > I propose that we push the entire schedule back two weeks. This means that > the planned rc2 on 17-September becomes our rc1. The planned final release > for 01-October becomes our rc2, and we release the finals on 15-October. > > - -Barry Perhaps it's time to separate the 2.6 and 3.0 release schedules? I don't care if the next version of OSX contains 3.0 or not -- but I do care about it having 2.6. -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ 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] Proposed revised schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't think there's any way we're going to make our October 1st goal. We have 8 open release critical bugs, and 18 deferred blockers. We do not have a beta3 Windows installer and I don't have high hopes for rectifying all of these problems in the next day or two. I propose that we push the entire schedule back two weeks. This means that the planned rc2 on 17-September becomes our rc1. The planned final release for 01-October becomes our rc2, and we release the finals on 15-October. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMUnWXEjvBPtnXfVAQIEAQQAnut+CRyBAacC2zzptb5l9cphwke0sEjx THJXHCBUfidaEV7SCtyfkh6i+IpqynvFRsKyOYSWsMojAa5rO/iM6ZJLkUav9c62 IzweJ6Nw3UnOJ/7xksCesDVxDRncFtvu0eRUZWDkOsrNawL+Z21DGKtAuau/pgiY sFnKeyP7NX0= =ZNPm -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] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 8, 2008, at 7:37 AM, A.M. Kuchling wrote: On Sun, Sep 07, 2008 at 12:02:06PM -0400, Barry Warsaw wrote: There are 8 open release blockers, a few of which have patches that need review. So I think we are still not ready to release rc1. But it worries me because I think this is going to push the final release beyond our October 1st goal. Should we try to schedule a bug evening some time this week? Monday, Tuesday and Friday are good for me. I might be around a bit on Wednesday evening. (All times EDT/UTC-4). I'm usually on irc. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMUma3EjvBPtnXfVAQIkEQP9HdcmjL3zRLO5yxBt3JEfxd2l924wFgAa avi5VZMA3YFRCqfmfS/BBtng2qTSbzyL8UO9tWSVdtjLd62g2uLuS1UzcBJ+O8qE I1veedtxxoSvjDOoVYmuYy3dS1ZFTEKvEs0PrE2ukoGzPkRpZTAQ1AeTxSXbuRc9 fZXgOWVYg6k= =PQUF -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] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 7, 2008, at 4:12 PM, Fredrik Lundh wrote: Barry Warsaw wrote: (I have a few minor ET fixes, and possibly a Unicode 5.1 patch, but have had absolutely no time to spend on that. is the window still open?) There are 8 open release blockers, a few of which have patches that need review. So I think we are still not ready to release rc1. So what's the new ETA? Should I set aside some time to work on the patches, say, tomorrow, or is it too late? It's not too late. If they fix bugs and the code gets reviewed then yes, you can check them in. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMUlmHEjvBPtnXfVAQJ51QP7BdUGcKN4+L9vD+g7y2TI0+TSw4Ms+eAc yXprcbQnfGp1+uxzjiTCeAv0OSAodw4aakAaI4wzrAkKYNmsVaWOiGKiKrLvR7+Y ++qBxxxVwlKL606hlJCKgphD4hbZcW1w3wY94CXkmrTqyZe/XrStvBj7X10gWeYW lwC3ATaQQ5Y= =tyym -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] Not releasing rc1 tonight
On Sun, Sep 07, 2008 at 12:02:06PM -0400, Barry Warsaw wrote: > There are 8 open release blockers, a few of which have patches that need > review. So I think we are still not ready to release rc1. But it > worries me because I think this is going to push the final release > beyond our October 1st goal. Should we try to schedule a bug evening some time this week? --amk ___ 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] Not releasing rc1 tonight
Fredrik Lundh pythonware.com> writes: > > So what's the new ETA? Should I set aside some time to work on the > patches, say, tomorrow, or is it too late? Given the state of things in the tracker, I'd say it doesn't look too late. ___ 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] ?spurious? Timeout in BSDDB under MS Windows
On Fri, Sep 05, 2008 at 05:55:13PM +0200, Jesus Cea wrote: > Trent, are you available to look at the ?spurious? timeout failures in > bsddb replication code in the Windows buildbot?. > > Ten seconds timeout should be plenty enough. I can't debug any MS > Windows issue myself; this is a Microsoft-free environment. I think I added in 10 seconds 'cause the tests kept failing when it was at 2 seconds ;-) I remember digging around the code a bit when I bumped bsddb to 4.7 on Windows to try and figure out what was going on. As far as I could tell it wasn't anything obvious caused by the Python code; is it possible this could be an issue with the underlying bsddb code? Side note: are all your recent bsddb changes that went into trunk also available in py3k? I've had "bump py3k Windows buildbots to use bsddb 4.7.25" on my todo list for far too long! Trent. ___ 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
