[Python-Dev] No email about buildbot failures for 3.1?

2009-01-17 Thread Brett Cannon
I just realized that I had not received any emails on python-checkins about the buildbot failures I accidentally caused. And then I noticed that I had not gotten any emails for py3k in a while. Did that get switched off on purpose? -Brett ___ Python-Dev

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 17, 2009, at 8:03 AM, Victor Stinner wrote: Le Saturday 17 January 2009 04:45:28 Barry Warsaw, vous avez écrit : The optparse one could easily be fixed for 2.6, if we agree it should be fixed. This untested patch should do it I think: Inde

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Benjamin Peterson
On Sat, Jan 17, 2009 at 4:58 PM, Barry Warsaw wrote: > On Jan 16, 2009, at 10:52 PM, Benjamin Peterson wrote: >> On Fri, Jan 16, 2009 at 9:45 PM, Barry Warsaw wrote: >>> - -if type(args[0]) is types.StringType: >>> +if type(args[0]) in types.StringTypes: >> >> It'd probably be bet

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 17, 2009, at 2:25 PM, Guido van Rossum wrote: On Sat, Jan 17, 2009 at 12:25 AM, "Martin v. Löwis" > wrote: Index: Lib/optparse.py === --- Lib/optparse.py(revision 68465) +++

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 16, 2009, at 10:52 PM, Benjamin Peterson wrote: On Fri, Jan 16, 2009 at 9:45 PM, Barry Warsaw wrote: The optparse one could easily be fixed for 2.6, if we agree it should be fixed. This untested patch should do it I think: Index: Lib

[Python-Dev] http://bugs.python.org/issue4977 - assumption that maxint64 fits into long on 32-bit systems

2009-01-17 Thread Luke Kenneth Casson Leighton
this was found as part of the regression tests, compiling python under wine under msys with mingw32. test_maxint64 failed. i tracked it down to the assumption that a long will fit into 32-bits, which obviously... it won't! the simplest case is to add a test for the length of the data string bein

Re: [Python-Dev] Python 3 for Mac OSX

2009-01-17 Thread Ned Deily
In article <655d2f11-818d-43e4-8234-1dd6c3b74...@qwest.net>, Roger Vossler wrote: > > Any idea when the Mac OSX disk image (.dmg file) for Python 3.x > > will be available? > > Are we talking about days? weeks? Or, should I start learning how to > build Python from > source? Any info would b

Re: [Python-Dev] Python 3 for Mac OSX

2009-01-17 Thread Martin v. Löwis
> Are we talking about days? weeks? Or, should I start learning how to > build Python from source? Any info would be appreciated. The latter. Don't ever expect that others will help you. This is open source; you have to help yourself. Regards, Martin __

[Python-Dev] Python 3 for Mac OSX

2009-01-17 Thread Roger Vossler
Hi, Any idea when the Mac OSX disk image (.dmg file) for Python 3.x will be available? Are we talking about days? weeks? Or, should I start learning how to build Python from source? Any info would be appreciated. Thanks, Roger. ___ Python-De

Re: [Python-Dev] off-by-one on ftell on wine, but no re gression test to catch it

2009-01-17 Thread Antoine Pitrou
Luke Kenneth Casson Leighton lkcl.net> writes: > running under wine, ftell() has an off-by-one bug, where the file > position accidentally doesn't include the fact that the CR of the CRLF > has been skipped. but, now with the fgets() bug fixed, the regression > tests pass, but there's still the o

[Python-Dev] off-by-one on ftell on wine, but no regression test to catch it

2009-01-17 Thread Luke Kenneth Casson Leighton
folks, hi, http://bugs.winehq.org/show_bug.cgi?id=16982 related to this: from array import array TESTFN = "testfile.txt" def fail(x): print x testlines = [ "spam, spam and eggs\n", "eggs, spam, ham and spam\n", "saussages, spam, spam and eggs\n", "spam, ham, spam and eggs\n"

Re: [Python-Dev] bundlebuilder broken in 2.6

2009-01-17 Thread Ned Deily
In article <7043cb7c-18f4-4e16-ae0c-cda6ba311...@barrys-emacs.org>, Barry Scott wrote: > It seems that the packaging of Mac Python 2.6 is missing at least one > file > that is critical to the operation of bundlebuilder.py. > > I've logged the issue as http://bugs.python.org/issue4937. I've n

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Martin v. Löwis
> That seems a bit *too* strict to me, as long as the Unicode strings > contain just ASCII. I'm fine with fixing both cases Barry mentioned, > especially if it otherwise breaks "from __future__ import > unicode_literals". I expect though that as one tries more things one > will find more things bro

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Guido van Rossum
On Sat, Jan 17, 2009 at 12:25 AM, "Martin v. Löwis" wrote: >> Index: Lib/optparse.py >> === >> --- Lib/optparse.py(revision 68465) >> +++ Lib/optparse.py(working copy) >> @@ -994,7 +994,7 @@ >> """add_option(Option) >

Re: [Python-Dev] report on building of python 2.5.2 under msys under wine on linux.

2009-01-17 Thread Luke Kenneth Casson Leighton
> About 5 test fail in emulated environment due bugs in emulator. oh - nearly forgot: several of the ctypes tests fail quite spectacularly :) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscrib

Re: [Python-Dev] report on building of python 2.5.2 under msys under wine on linux.

2009-01-17 Thread Luke Kenneth Casson Leighton
hiya roumen, good to hear from you - i've been merging in the work that you did, on mingw native-and-cross compiles. got a couple of questions, will post them in the bugreport ok? On Sat, Jan 17, 2009 at 3:16 PM, Roumen Petrov wrote: > Luke Kenneth Casson Leighton wrote: > [SNIP] >> >> i'm going

Re: [Python-Dev] Deprecate PyNumber_Long?

2009-01-17 Thread Benjamin Peterson
On 1/17/09, Antoine Pitrou wrote: > Mark Dickinson gmail.com> writes: >> >> Benjamin wondered aloud about deprecating PyNumber_Long >> in the issue 4910 discussion; I suggested deprecating >> PyNumber_Int instead, but on reflection I think Benjamin's right: >> it seems neater to keep the PyNumbe

Re: [Python-Dev] report on building of python 2.5.2 under msys under wine on linux.

2009-01-17 Thread Roumen Petrov
Luke Kenneth Casson Leighton wrote: [SNIP] i'm going to _try_ to merge in #3871 but it's... the prospect of sitting waiting for configure to take THREE hours to complete, due to /bin/sh.exe instances taking TWO SECONDS _each_ to start up does not really fill me with deep joy. As from version 1.

[Python-Dev] issue2233: ... extra slash before $(DESTDIR) ... cygwin install fail

2009-01-17 Thread Roumen Petrov
Hi All, May I ask for a vote how issue to be resolved. The problem is command "... setup.py install ... --root=/$(DESTDIR)" if DESTDIR is specified: error: could not create '//...': No such host or network path Currently issue http://bugs.python.org/issue2233 propose three solutions: 1) replace

[Python-Dev] bundlebuilder broken in 2.6

2009-01-17 Thread Barry Scott
It seems that the packaging of Mac Python 2.6 is missing at least one file that is critical to the operation of bundlebuilder.py. I've logged the issue as http://bugs.python.org/issue4937. Barry ___ Python-Dev mailing list Python-Dev@python.org http

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Victor Stinner
Le Saturday 17 January 2009 04:45:28 Barry Warsaw, vous avez écrit : > The optparse one could easily be fixed for 2.6, if we agree it should > be fixed. This untested patch should do it I think: > > Index: Lib/optparse.py > === > ---

Re: [Python-Dev] Deprecate PyNumber_Long?

2009-01-17 Thread Antoine Pitrou
Mark Dickinson gmail.com> writes: > > Benjamin wondered aloud about deprecating PyNumber_Long > in the issue 4910 discussion; I suggested deprecating > PyNumber_Int instead, but on reflection I think Benjamin's right: > it seems neater to keep the PyNumber_Int <-> int() <-> nb_int > naming conne

Re: [Python-Dev] Deprecate PyNumber_Long?

2009-01-17 Thread Mark Dickinson
On Fri, Jan 16, 2009 at 10:42 PM, Brett Cannon wrote: > Assuming we have been moving the C API usage to PyInt and not PyLong, > then yes it makes sense. Hmm. I don't think there's been any such move. Maybe there should be. Benjamin wondered aloud about deprecating PyNumber_Long in the issue 49

Re: [Python-Dev] Problems with unicode_literals

2009-01-17 Thread Martin v. Löwis
> Index: Lib/optparse.py > === > --- Lib/optparse.py(revision 68465) > +++ Lib/optparse.py(working copy) > @@ -994,7 +994,7 @@ > """add_option(Option) > add_option(opt_str, ..., kwarg=val, ...) > "