[Python-Dev] x86 Leopard buildbot

Hello, As a leap of faith, I have added Stephen Hansen's x86 Leopard buildbot to the list of stable bots. Stephen has been very proactive in diagnosing and fixing issues (thank you!). Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://

[Python-Dev] issue 10212

On Fri, 29 Oct 2010 10:10:31 +0800 Kristján Valur Jónsson wrote: > > What finally drove me to write the original post, was that working with > the new bytearray and memoryview object in 2.7 made me realize that > they don't interoperate with other classes in a natural way and so > nullify their a

Re: [Python-Dev] Continuing 2.x

Brett Cannon writes: > I think people need to stop viewing the difference between Python 2.7 > and Python 3.2 as this crazy shift and view it from python-dev's > perspective; That phrasing *is* harsh. People also need to work with code bases that are incompatible with Python 3.2 for various r

Re: [Python-Dev] Continuing 2.x

2010/10/28 Kristján Valur Jónsson : > Hi all. > This has been a lively discussion. > My desire to keep 2.x alive in some sense is my own and I don't know if > anyone shares it but as a member of this community I think I'm allowed to > voice it.  So, just to clarify my particular position, let me

Re: [Python-Dev] [Python-checkins] r85902 - in python/branches/py3k/Lib: os.py test/test_os.py

2010/10/28 victor.stinner : > Author: victor.stinner > Date: Fri Oct 29 02:38:58 2010 > New Revision: 85902 > > Log: > Issue #10210: os.get_exec_path() ignores BytesWarning warnings > > > Modified: >   python/branches/py3k/Lib/os.py >   python/branches/py3k/Lib/test/test_os.py > > Modified: python/

Re: [Python-Dev] Continuing 2.x

Hi all. This has been a lively discussion. My desire to keep 2.x alive in some sense is my own and I don't know if anyone shares it but as a member of this community I think I'm allowed to voice it. So, just to clarify my particular position, let me explain where all this comes from. I am the

Re: [Python-Dev] Continuing 2.x

On Fri, Oct 29, 2010 at 3:47 AM, Tres Seaver wrote: > I think that assumption may not be warranted.  If the current core folks > are focused only on developing Python 3, but others are working on a > notional 2.8, there is no necessary correlation any longer between the > two.  In particular, the

Re: [Python-Dev] Fixing zipfile.BadZipfile to zipfile.BadZipFile

Le 28/10/2010 22:52, anatoly techtonik a écrit : > Can anybody summarize the outcome? > Is it that renaming BadZipfile to BadZipFile with backward compatible > alias and deprecation note breaks something? See #7351 or r85874. Regards ___ Python-Dev mai

Re: [Python-Dev] A sad state of doctests in the python manual

On Thu, Oct 28, 2010 at 5:30 PM, Alexander Belopolsky wrote: > On Thu, Oct 28, 2010 at 5:18 PM, Barry Warsaw wrote: > .. >> >> It would be really cool if you fixed this! >> > Working on it.  Stay tuned. :-) > See http://bugs.python.org/issue10224 ___

Re: [Python-Dev] A sad state of doctests in the python manual

On Thu, Oct 28, 2010 at 5:18 PM, Barry Warsaw wrote: .. > > It would be really cool if you fixed this! > Working on it. Stay tuned. :-) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: h

Re: [Python-Dev] A sad state of doctests in the python manual

On Oct 28, 2010, at 04:57 PM, Alexander Belopolsky wrote: >On Thu, Oct 28, 2010 at 4:52 PM, Alexander Belopolsky > wrote: >> On the second look, the problem may not be that bad ... > >Nope, the problem is even worse. It looks like Sphinx in py3k >requires 2.x python: > >$ ../python.exe tools/sphi

Re: [Python-Dev] A sad state of doctests in the python manual

On Thu, Oct 28, 2010 at 4:52 PM, Alexander Belopolsky wrote: > On the second look, the problem may not be that bad ... Nope, the problem is even worse. It looks like Sphinx in py3k requires 2.x python: $ ../python.exe tools/sphinx-build.py -b doctest -d build/doctrees -D latex_paper_size= . bu

Re: [Python-Dev] Fixing zipfile.BadZipfile to zipfile.BadZipFile

Can anybody summarize the outcome? Is it that renaming BadZipfile to BadZipFile with backward compatible alias and deprecation note breaks something? -- anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo

Re: [Python-Dev] A sad state of doctests in the python manual

On the second look, the problem may not be that bad - "make doctest" picks up system python instead of the one from the source tree. I'll try to figure out how to rerun the doctests properly. On Thu, Oct 28, 2010 at 4:48 PM, Alexander Belopolsky wrote: > I have just discovered that sphinx suppor

[Python-Dev] A sad state of doctests in the python manual

I have just discovered that sphinx supports running doctests embedded in ReST documentation. It looks like it is as simple as "cd Doc; make doctest". The result, however is not encouraging: $ make doctest ... Doctest summary === 1162 tests 262 failures in tests 0 failures in

Re: [Python-Dev] Continuing 2.x

Am 28.10.2010 18:07, schrieb l...@rmi.net: > Kristj?n Valur J?nsson writes: >> James Y Knight said: >> The python community has already decided many times over that Python2 is >> dead >> and Python3 is the future >> >> But the patient is very much alive and kicking, no matter what the good >> d

Re: [Python-Dev] Continuing 2.x

> (and, believe me, not having to backport new 3.x features to the 2.x > branch makes our work much easier than it was; people generally seem > to underestimate the amount of care needed for such things, especially > in areas where 2.x is significantly more complex - old-style classes, > two paral

Re: [Python-Dev] Continuing 2.x

l...@rmi.net writes: > But one can't help but wonder if most of the development community > is focused on some imaginary future user base, at the expense of > the much larger current user base. Of course not. Most of the development community is *focused* on a very real, very current, and ver

Re: [Python-Dev] Continuing 2.x

On 28/10/2010 13:20, R. David Murray wrote: On Thu, 28 Oct 2010 16:07:50 -, l...@rmi.net wrote: I hope 3.X use expands; in fact, I've bet the future of at least one book on it. And even 1/4 of new users seems a large enough subset to care about too. But one can't help but wonder if most of

Re: [Python-Dev] Continuing 2.x

On Thu, 28 Oct 2010 10:25:28 -0700 Ian Bicking wrote: > > Thinking about language features and core type this seems reasonable, but > with the standard library this seems less reasonable -- there's lots of > conservative changes to the standard library which aren't bug fixes, and the > more the s

Re: [Python-Dev] Continuing 2.x

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2010 09:33 AM, Nick Coghlan wrote: > 2010/10/28 Kristján Valur Jónsson : >> Hello all. >> So, python 2.7 is in bugfix only mode. ‘trunk’ is off limit. So, where >> does one make improvements to the distinguished, and still very much alive, >

Re: [Python-Dev] Continuing 2.x

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2010 12:04 PM, Barry Warsaw wrote: > Who is the target audience for a Python 2.8? What exactly would a Python 2.8 > accomplish? > > If Python 2.8 doesn't include new features, well, then what's the point? > Python 2.7 will be bug fix mainta

Re: [Python-Dev] Continuing 2.x

Barry Warsaw writes: > Maybe so, but I think it's actually more fun to be working on > something other people will actually use. ;) I think that the point is that the people will be doing this are supporting software to pay for Johnny's piano lessons, not for personal pleasure. I imagine many,

Re: [Python-Dev] Continuing 2.x

On Wed, Oct 27, 2010 at 11:48 PM, Georg Brandl wrote: > Am 28.10.2010 06:13, schrieb Daniel Stutzbach: >> 2010/10/27 Kristján Valur Jónsson > > >> >>     Firstly, the ease of integrating changes.  It would be possible to port >>     those bugfixes that release-27 gets

Re: [Python-Dev] Continuing 2.x

On Thu, Oct 28, 2010 at 9:04 AM, Barry Warsaw wrote: > Who is the target audience for a Python 2.8? What exactly would a Python > 2.8 > accomplish? > > If Python 2.8 doesn't include new features, well, then what's the point? > Python 2.7 will be bug fix maintained for a long time, longer in fact

Re: [Python-Dev] Continuing 2.x

On Thu, 28 Oct 2010 16:07:50 -, l...@rmi.net wrote: > I hope 3.X use expands; in fact, I've bet the future of at > least one book on it. And even 1/4 of new users seems a > large enough subset to care about too. But one can't help > but wonder if most of the development community is focused

Re: [Python-Dev] Continuing 2.x

On Oct 28, 2010, at 04:07 PM, l...@rmi.net wrote: >I hope 3.X use expands; in fact, I've bet the future of at >least one book on it. And even 1/4 of new users seems a >large enough subset to care about too. But one can't help >but wonder if most of the development community is focused >on som

Re: [Python-Dev] Continuing 2.x

On Thu, Oct 28, 2010 at 12:07 PM, wrote: .. > Has anyone here analyzed download stats on py.org lately? > Please feel free to prove me wrong, but by my reckoning, > and at least for Windows MSI installer files, people are > still downloading Python 2.X roughly 3 to 4 times more often > than Pytho

Re: [Python-Dev] Continuing 2.x

Kristján Valur Jónsson wrote: > Let's move the current 'trunk' into /branches/afterlife-27. Open it > for submissions from people such as myself that use 2.7 on a regular > basis and are willing to give it some extra love. Though I'm not personally convinced it's a good idea, I can see where so

Re: [Python-Dev] Continuing 2.x

Am 28.10.2010 18:07, schrieb l...@rmi.net: > Kristj?n Valur J?nsson writes: >> James Y Knight said: >> The python community has already decided many times over that Python2 is >> dead >> and Python3 is the future >> >> But the patient is very much alive and kicking, no matter what the good >>

Re: [Python-Dev] Continuing 2.x

On Oct 28, 2010, at 04:17 PM, exar...@twistedmatrix.com wrote: >On 04:04 pm, ba...@python.org wrote: >> >>I'd *much* rather this enthusiasm be spent on making Python 3 rock, and >in >>porting third party code to Python 3. > >Enthusiasm isn't fungible. Maybe so, but I think it's actually more fun

Re: [Python-Dev] Continuing 2.x

On 04:04 pm, ba...@python.org wrote: I'd *much* rather this enthusiasm be spent on making Python 3 rock, and in porting third party code to Python 3. Enthusiasm isn't fungible. Jean-Paul ___ Python-Dev mailing list Python-Dev@python.org http://mai

Re: [Python-Dev] Continuing 2.x

Kristj?n Valur J?nsson writes: > James Y Knight said: > The python community has already decided many times over that Python2 is dead > and Python3 is the future > > But the patient is very much alive and kicking, no matter what the good > doctor > declares. Python 2.x is in widespread use, w

Re: [Python-Dev] Continuing 2.x

Who is the target audience for a Python 2.8? What exactly would a Python 2.8 accomplish? If Python 2.8 doesn't include new features, well, then what's the point? Python 2.7 will be bug fix maintained for a long time, longer in fact than previous Python 2 versions. So a no-feature Python 2.8 can'

Re: [Python-Dev] Buildbot for AIX

On Fri, 15 Oct 2010 17:38:47 +0200 Sébastien Sablé wrote: > > Could you please take a look at those modifications in master.cfg, > provide me some password for the bot slaves and apply the corrections in > those issues? About the master.cfg modifications: there should be no need for separate e

Re: [Python-Dev] Buildbot for AIX

> I got no reply concerning those modifications to the buildbot script so > that I could run 2 slaves on AIX. I'm really really reluctant here. The proposed/requested changes are fairly intrusive, even though AIX is just a minority platform. So I need to find some time to rewrite them, which I hav

Re: [Python-Dev] MemoryError... how much memory?

On Thu, 28 Oct 2010 15:54:50 +0200 Georg Brandl wrote: > Am 28.10.2010 15:14, schrieb "Martin v. Löwis": > >> Furthermore, our server is fairly complex: we're using quite some > >> libraries to do different jobs, and one of the approaches (not the > >> only one) that we're taking to deal with this

Re: [Python-Dev] MemoryError... how much memory?

Am 28.10.2010 15:14, schrieb "Martin v. Löwis": >> Furthermore, our server is fairly complex: we're using quite some >> libraries to do different jobs, and one of the approaches (not the >> only one) that we're taking to deal with this beast is to analyze its >> memory-related behaviour from an ext

Re: [Python-Dev] MemoryError... how much memory?

On Thu, Oct 28, 2010 at 11:14 PM, "Martin v. Löwis" wrote: >> Furthermore, our server is fairly complex: we're using quite some >> libraries to do different jobs, and one of the approaches (not the >> only one) that we're taking to deal with this beast is to analyze its >> memory-related behaviour

Re: [Python-Dev] Continuing 2.x

2010/10/28 Kristján Valur Jónsson : > Hello all. > So, python 2.7 is in bugfix only mode.  ‘trunk’ is off limit.  So, where > does one make improvements to the distinguished, and still very much alive, > 2.x series of Python? > > The answer would seem to be “one doesn’t”.  But must it be that way?

Re: [Python-Dev] MemoryError... how much memory?

> Furthermore, our server is fairly complex: we're using quite some > libraries to do different jobs, and one of the approaches (not the > only one) that we're taking to deal with this beast is to analyze its > memory-related behaviour from an external POV (thinking it as a black > box). > > So, b

Re: [Python-Dev] Continuing 2.x

> Let’s move the current ‘trunk’ into /branches/afterlife-27. Open it for > submissions from people such as myself that use 2.7 on a regular basis > and are willing to give it some extra love. Host it there without the > usual stringent python quality assurance, buildbot support, release > manage

Re: [Python-Dev] MemoryError... how much memory?

On Thu, Oct 28, 2010 at 9:14 PM, Facundo Batista wrote: > So, beyond it's arguable utility, do you think that having that > information could harm us in some way? I think the idea is sound in principle, but may run into some practical implementation problems due to special cases when raising Memo

Re: [Python-Dev] MemoryError... how much memory?

On Wed, Oct 27, 2010 at 8:27 PM, Nick Coghlan wrote: > If you see MemoryError (5 bytes), the things you go looking for are > very different from those you look for when you see MemoryError(1 > gajillion bytes). (i.e. for the former, you look for a memory or other > resource leak, for the latter,

Re: [Python-Dev] Continuing 2.x

On Wed, 27 Oct 2010 23:05:37 -0500 Benjamin Peterson wrote: > 2010/10/27 Kristján Valur Jónsson : > > Firstly, the ease of integrating changes.  It would be possible to port > > those bugfixes that release-27 gets, and also backport selected things from > > py3k using the tools already in place su

Re: [Python-Dev] Continuing 2.x

Le jeudi 28 octobre 2010 05:12:09, James Y Knight a écrit : > The python community has already decided many times over that Python2 is > dead and Python3 is the future. ... I think you'd be best off doing > so on your own infrastructure: convincing the python developers to support > such a thing is

Re: [Python-Dev] Buildbot for AIX

Hi Martin, I got no reply concerning those modifications to the buildbot script so that I could run 2 slaves on AIX. I am able to spend some time at the moment on Python for AIX because we are migrating the product in my company from AIX 5.3 to AIX 6.1. However once this is done, by the end o

Re: [Python-Dev] Continuing 2.x

2010/10/28 Kristján Valur Jónsson : > But the patient is very much alive and kicking, no matter what the good > doctor declares. No no! 'E's pining! Schiavo Simon ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/

Re: [Python-Dev] Continuing 2.x

On Thu, Oct 28, 2010 at 08:48, Georg Brandl wrote: > I believe we'll eventually have the ability to create user repos as well, so > that Kristjan can simply put his branch into one of these and still have it > on hg.python.org. +1. Cheers, Dirkjan ___