Re: [Python-Dev] 2.7 and 3.2 release schedules

Benjamin Peterson schrieb: > After more thought, I think that separating the 2.7 and 3.2 releases > is not as big of an issue as I once thought. Therefore, I'd like to > adopt the schedule I posted a few weeks back for 2.7 only. > > This only means some other lucky victi... I mean volunteer can do

[Python-Dev] Making loggerClass an attribute of the logger manager?

Hi, recently I had a use case where I wanted to use logging in two completely separate parts of the same process. One of them needs to create instances a specific Logger subclass, while the other is fine with the default loggers. I got around the problem of the unique root node by using two Mana

Re: [Python-Dev] wpython is back

Cesare Di Mauro schrieb: > Hi Mart > > I'm back with some news about wpython. I completed all the work that I > was committed to do till the end of the year. I made a lot of changes to > the code, that I'll report here.. For those of us without an elephant's memory, could you please also recap wh

[Python-Dev] Rough 3.2 release schedule

... is in PEP 392. Nothing much to see, except that the final date is December 11, 2010. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not

Re: [Python-Dev] Rough 3.2 release schedule

Am 31.12.2009 00:48, schrieb Michael Foord: > On 30/12/2009 23:39, Georg Brandl wrote: >> ... is in PEP 392. Nothing much to see, except that the final date is >> December 11, 2010. >> >> Georg >> >> > The PEP index incorrectly lists PEP 375 as be

Re: [Python-Dev] Improve open() to support reading file starting with an unicode BOM

Am 08.01.2010 22:14, schrieb Tres Seaver: >> FWIW, I'm personally in favor of using the UTF-8 signature. If people >> consider them crazy talk, that may be because UTF-8 can't possibly have >> a byte order - hence I call it a signature, not the BOM. As a signature, >> I don't consider it crazy at

Re: [Python-Dev] PYTHON3PATH

Am 13.01.2010 21:27, schrieb Lennart Regebro: > On Wed, Jan 13, 2010 at 21:08, Oleg Broytman wrote: >> On Wed, Jan 13, 2010 at 08:50:59PM +0100, Lennart Regebro wrote: >>> What do you need to do in the PYTHONSTARTUP file? >>> Ten years of Python programming, and I didn't even know it existed. :-)

Re: [Python-Dev] Bazaar branches available (again) on Launchpad

Am 20.01.2010 03:43, schrieb David Lyon: >> Barry was talking about mirrors of the python code. It is true a >> "package manager" could be developed based on a SCM, however you need >> to implement this far away from the stdlib and get traction with it >> within the community long before inclusion

Re: [Python-Dev] Bazaar branches available (again) on Launchpad

Am 21.01.2010 04:33, schrieb Ben Finney: > Georg Brandl writes: > >> But I've no intention to restrict feature releases to "every 18-24 >> months". What now? > > Now we take further discussion to the ‘python-ideas’ forum. Whoever "we" is.

Re: [Python-Dev] patch to make list.pop(0) work in O(1) time

Am 28.01.2010 05:30, schrieb Steve Howell: > If you want tools that are easy to use correctly, make them bug-free and > document their behavior. If you want tools that are easy to use well, then > make them perform better. I am not sure how my patch contradicts either of > these goals. > > You

Re: [Python-Dev] PEP 3147: PYC Repository Directories

Am 31.01.2010 07:29, schrieb Nick Coghlan: > Vitor Bosshard wrote: >>> There is no one-to-one correspondence between Python version and pyc >>> magic numbers. Different runtime options may change the magic number and >>> different versions may reuse a magic number >> >> Good point. Runtime options

Re: [Python-Dev] PEP 3147: PYC Repository Directories

Am 31.01.2010 05:18, schrieb Ben Finney: > Nick Coghlan writes: > >> It won't be cluttered with subfolders - you will have at most one .pyr >> per source .py file. > > If that doesn't meet your threshold of “cluttered with subfolders”, I'm > at a loss for words to think where that threshold migh

Re: [Python-Dev] PEP 3147: PYC Repository Directories

Am 31.01.2010 07:18, schrieb Nick Coghlan: > Ben Finney wrote: >> Could we instead have a single subdirectory for each tree of module >> packages, keeping them tidily out of the way of the source files, while >> making them located just as deterministically:: > > Not easily. With the scheme curren

Re: [Python-Dev] PEP 3147: PYC Repository Directories

Am 31.01.2010 10:21, schrieb Ben Finney: > Nick Coghlan writes: > >> Actually, this is the first post I've seen noting objective problems >> with the use of a subdirectory. The others were just a subjective >> difference in perspective that saw subdirectory clutter as somehow >> being worse than

Re: [Python-Dev] PEP 3147: PYC Repository Directories

Am 31.01.2010 13:03, schrieb Simon Cross: > On Sun, Jan 31, 2010 at 1:54 PM, Hanno Schlichting wrote: >> I'd be a big +1 to using a single ".pyr" directory per source directory. > > I don't know whether I in favour of using a single pyr folder or not > but if a single folder is used I'd definitel

Re: [Python-Dev] PEP 3147: PYC Repository Directories

Am 31.01.2010 13:29, schrieb Simon Cross: > On Sun, Jan 31, 2010 at 2:13 PM, Hanno Schlichting wrote: >> On Sun, Jan 31, 2010 at 1:03 PM, Simon Cross >> wrote: >>> I don't know whether I in favour of using a single pyr folder or not >>> but if a single folder is used I'd definitely prefer the fol

Re: [Python-Dev] PEP 3147: PYC Repository Directories

Am 31.01.2010 14:02, schrieb Nick Coghlan: > Georg Brandl wrote: >> Then why did Subversion choose to follow the CVS way and create a >> subdirectory in each versioned directory? IMO, this is much more >> annoying given the alternative of a single .hg/.bzr/whatever directory

Re: [Python-Dev] Fixed URL to 2.6 documentation

Am 04.02.2010 08:57, schrieb anatoly techtonik: > Greetings, > > I'm writing a module for current Python 2.6 and I would like to > reference documentation for Python 2.6, because I am not sure if > behavior won't be changed in further series. So far I can link only > to: > > http://docs.python.or

Re: [Python-Dev] Making loggerClass an attribute of the logger manager?

Am 25.11.2009 11:32, schrieb Vinay Sajip: > Georg Brandl gmx.net> writes: > >> Making the loggerClass configurable per manager would solve the >> problem for me, and AFAICS since most applications don't use >> different managers anyway, there should not be any

Re: [Python-Dev] PEP 385 progress report

Am 09.02.2010 04:47, schrieb Benjamin Peterson: > 2010/2/8 "Martin v. Löwis" : >> Benjamin Peterson wrote: >>> 2010/2/8 Dirkjan Ochtman : On Sun, Feb 7, 2010 at 22:51, Benjamin Peterson wrote: > Will you do test conversions of the sandbox projects, too? Got any particular proje

Re: [Python-Dev] PEP 385 progress report

Am 09.02.2010 04:39, schrieb "Martin v. Löwis": > Benjamin Peterson wrote: >> 2010/2/8 Dirkjan Ochtman : >>> On Sun, Feb 7, 2010 at 22:51, Benjamin Peterson wrote: Will you do test conversions of the sandbox projects, too? >>> Got any particular projects in mind? >> >> 2to3. > > Does Mercur

Re: [Python-Dev] PEP 385: Auditing

Am 13.02.2010 13:19, schrieb Antoine Pitrou: > Martin v. Löwis v.loewis.de> writes: >> >> Alterntively, the email notification sent to python-checkins could could >> report who the pusher was. > > This sounds reasonable, assuming it doesn't disclose any private information. How could it disclos

Re: [Python-Dev] PEP 385: Auditing

Am 13.02.2010 18:52, schrieb Dirkjan Ochtman: > On Sat, Feb 13, 2010 at 12:53, "Martin v. Löwis" wrote: >> Dirkjan: if you agree to such a strategy, please mention that in the PEP. > > Having a pushlog and/or including the pusher in the email sounds like > a good idea, I'll add something to that

Re: [Python-Dev] Proposal for virtualenv functionality in Python

Am 20.02.2010 06:37, schrieb Michael Foord: > > > > -- > http://www.ironpythoninaction.com Nice signature! > On 19 Feb 2010, at 22:52, Eric Smith wrote: > >> Glenn Linderman wrote: >>> On approximately 2/19/2010 1:18 PM, came the following characters >>> from the keyboard of P.J. Eby:

Re: [Python-Dev] 'languishing' status for the tracker

Am 22.02.2010 21:28, schrieb Florent Xicluna: > R. David Murray bitdance.com> writes: > >> >> I believe Brett mentioned the 'languishing' status for the tracker in >> passing in his notes from the language summit. >> > > I see a bunch of existing "Status / Resolution" choices. > "open" / "

Re: [Python-Dev] doctest, unicode repr, and 2to3

Am 05.03.2010 20:37, schrieb Terry Reedy: > On 3/4/2010 11:11 PM, "Martin v. Löwis" wrote: >> Johan Harjano ran into an interesting problem when trying to run the >> Django test suite under Python 3.1. >> >> Django has doctests of the form >> > a6.headline >> u'Default headline' >> >> Even when

Re: [Python-Dev] Desired changes to Hg emails to python-checkins

Am 04.03.2010 21:20, schrieb Brett Cannon: > 1) I miss not having the affected files listed in the subject line. I actually like the (first line of the) commit message better. It communicates much better what the change is about (and for me, if I want to look at/review it). However, what I miss

Re: [Python-Dev] argparse ugliness

Am 06.03.2010 03:28, schrieb Antoine Pitrou: > Le Fri, 05 Mar 2010 13:51:15 -0500, > Neal Becker a écrit : >> I generally enjoy argparse, but one thing I find rather >> ugly and unpythonic. >> >> parser.add_argument ('--plot', action='store_true') > > I would argue that a string is actually

Re: [Python-Dev] Modifying Grammar/grammar and other foul acts

Am 09.03.2010 14:42, schrieb Jeremy Hylton: > On Sat, Mar 6, 2010 at 11:27 AM, Gregg Lind wrote: >> Python-devs, >> >> I'm writing to you for some help in understanding the Python grammar. As an >> excuse to deep dive into Python's tokenizer / grammar, I decided (as a >> hideous, hideous joke) to

Re: [Python-Dev] interesting article on regex performance

Am 12.03.2010 20:29, schrieb s...@pobox.com: > > >> There are major practical problems associated with making such a leap > >> directly (Google's re2 engine is in C++ rather than C and we'd have > >> to keep the existing implementation around regardless to handle the > >> features

Re: [Python-Dev] Desired changes to Hg emails to python-checkins

Am 04.03.2010 21:20, schrieb Brett Cannon: > 1) I miss not having the affected files listed in the subject line. > > 2) The To field is set to h...@python.org which > gets rejected as an invalid email address if you reply. Would be better > to set it to python-checkins so

Re: [Python-Dev] Request for commit access

Am 23.03.2010 23:01, schrieb Antoine Pitrou: > Martin v. Löwis v.loewis.de> writes: >> >> Procedurally, I wonder where people got the notion from that you can or >> need to apply for commit access. IIUC, it used to be the case that you >> would be recommended for commit access, by some (more or l

Re: [Python-Dev] Why is nan != nan?

Am 24.03.2010 22:47, schrieb Mark Dickinson: > On Wed, Mar 24, 2010 at 10:36 PM, Alexander Belopolsky > wrote: >> On Wed, Mar 24, 2010 at 6:31 PM, Mark Dickinson wrote: >> .. >>> Neither is necessary, because Python doesn't actually use == as the >>> equivalence relation for containment testing:

Re: [Python-Dev] Why is nan != nan?

Am 25.03.2010 22:45, schrieb Greg Ewing: > Georg Brandl wrote: >> Thinking of each value created by float('nan') as >> a different nan makes sense to my naive mind, and it also explains >> nicely the behavior present right now. > > Not entirely: > >

Re: [Python-Dev] Code coverage metrics

Am 06.04.2010 13:50, schrieb anatoly techtonik: > On Tue, Apr 6, 2010 at 12:50 PM, Senthil Kumaran wrote: >>> Where can I find public reports with Python tests code coverage? >> >> Here: >> >> http://coverage.livinglogic.de/ > > Thank you. What is the status of getting these stats on python.org?

Re: [Python-Dev] PEP 3147, __cached__, and PyImport_ExecCodeModuleEx()

Am 10.04.2010 18:12, schrieb Guido van Rossum: > On Sat, Apr 10, 2010 at 8:58 AM, Barry Warsaw wrote: >> On Apr 09, 2010, at 05:41 PM, Guido van Rossum wrote: >> >>>On Fri, Apr 9, 2010 at 3:54 PM, Paul Moore wrote: Would it be better to name this one _PyImport_ExecCodeModuleExEx (with a

Re: [Python-Dev] PEP 3147, __cached__, and PyImport_ExecCodeModuleEx()

Am 11.04.2010 00:25, schrieb Barry Warsaw: > On Apr 10, 2010, at 08:28 PM, Georg Brandl wrote: > >>Am 10.04.2010 18:12, schrieb Guido van Rossum: >>> On Sat, Apr 10, 2010 at 8:58 AM, Barry Warsaw wrote: >>>> On Apr 09, 2010, at 05:41 PM, Guido van Rossum wrote: &

Re: [Python-Dev] Enhanced tracker privileges for dangerjim to do triage.

Am 26.04.2010 15:34, schrieb Lennart Regebro: > On Mon, Apr 26, 2010 at 12:58, Stephen J. Turnbull wrote: >> It is entirely *not* evident to me that it's too hard to get >> privileges in the Python development community (Python's development >> process works -- and it works really well by comparis

Re: [Python-Dev] Frequency of the dev docs autobuild

Am 29.04.2010 13:40, schrieb R. David Murray: > On Thu, 29 Apr 2010 20:16:14 +1000, Nick Coghlan wrote: >> Does the online dev version of the docs build in response to docs >> checkins, or just once a day? > > I believe it does it once a day. Georg recently changed how this is done, > so we shou

Re: [Python-Dev] Frequency of the dev docs autobuild

Am 02.05.2010 22:21, schrieb R. David Murray: > On Sun, 02 May 2010 00:44:22 +0200, > =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= wrote: >> R. David Murray wrote: >> > On Sat, 01 May 2010 16:18:19 +0100, Paul Moore wrote: >> >> On 1 May 2010 15:28, R. David Murray wrote: >> >>> Unless I'm missin

Re: [Python-Dev] Two small PEP ideas

Am 03.05.2010 18:40, schrieb Guido van Rossum: > On Mon, May 3, 2010 at 8:57 AM, Barry Warsaw wrote: >> On May 01, 2010, at 07:12 AM, Martin v. Löwis wrote: >> IIRC in the IETF this is done by the committee chair. I think it's a good idea to have this be a single person to avoid endless

Re: [Python-Dev] Two small PEP ideas

Am 05.05.2010 13:24, schrieb Michael Foord: > On 05/05/2010 12:15, Nick Coghlan wrote: >> Georg Brandl wrote: >> >>> I agree, and I wouldn't want to make these decisions. That person (or >>> group) needs to have some weight in the community, or there wi

Re: [Python-Dev] PEP 3148 ready for pronouncement

Am 24.05.2010 01:51, schrieb Greg Ewing: > Brian Quinlan wrote: > >> The good news in this case is that the same API has been used >> successfully in Java and C++ for years so it is unlikely that any major >> changes will need to be made. > > That doesn't follow. An API that's appropriate for J

Re: [Python-Dev] Python Library Support in 3.x (Was: email package status in 3.X)

Am 19.06.2010 15:09, schrieb Arc Riley: > Just because legacy Python needs to be kept around for a bit longer for > a few uses does not mean that "Python 3 is not ready yet". Any decent > package system can have two or more versions of Python installed at the > same time. > > It is not "critical

[Python-Dev] Adopt A Demo [was: Signs of neglect?]

Am 26.06.2010 00:38, schrieb Steve Holden: > I was pretty stunned when I tried this. Remember that the Tools > subdirectory is distributed with Windows, so this means we got through > almost two releases without anyone realizing that 2to3 does not appear > to have touched this code. > > Yes, I hav

Re: [Python-Dev] #Python3 ! ? (was Python Library Support in 3.x)

Am 22.06.2010 01:01, schrieb Terry Reedy: > On 6/21/2010 3:59 PM, Steve Holden wrote: >> Terry Reedy wrote: >>> On 6/21/2010 8:33 AM, Nick Coghlan wrote: >>> P.S. (We're going to have a tough decision to make somewhere along the line where docs.python.org is concerned, too - when do we fl

Re: [Python-Dev] Taking over the Mercurial Migration

Am 30.06.2010 07:37, schrieb "Martin v. Löwis": > It seems that both Dirkjan and Brett are very caught up > with real life for the coming months. So I suggest that > some other committer who favors the Mercurial transition > steps forward and takes over this project. > > If nobody volunteers, I pr

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 01.07.2010 23:25, schrieb Doug Hellmann: > > On Jul 1, 2010, at 10:31 AM, Daniel Stutzbach wrote: > >> On Thu, Jul 1, 2010 at 7:52 AM, anatoly techtonik > > wrote: >> >> 4. Even if I make patch in my Mercurial clone - you still can't pull >> it and I have to

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 09:27, schrieb anatoly techtonik: > On Thu, Jul 1, 2010 at 6:16 PM, Jesse Noller wrote: >> >> This migration is far from "rushed". Workflow will need to be >> documented and we need a working hg setup a little while before the >> official migration. Both of those said, I personally t

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 01:05, schrieb Antoine Pitrou: > On Thu, 1 Jul 2010 15:26:12 -0700 > Brett Cannon wrote: >> >> As I said, quick-and-dirty. It will take discussion to decide what we >> want to ask non-committers to do, > > I don't think we have to ask them to do anything special, as long as > they

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 15:48, schrieb anatoly techtonik: > On Fri, Jul 2, 2010 at 11:33 AM, Georg Brandl wrote: >>> >>> So, if I understand correctly - there are no Mercurial mirrors for >>> testing at the moment, >> >> There are repositories at http://hg.python

Re: [Python-Dev] Are you ready for Mercurial migration?

Am 02.07.2010 16:29, schrieb anatoly techtonik: > To shed some light on the readiness of Python community for the switch > I've opened public Google Wave. Please add your opinion if you can and > send this link to other contributors you may know: tl;dr: I failed forcing my notions upon the partici

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 16:17, schrieb anatoly techtonik: > On Fri, Jul 2, 2010 at 4:53 PM, Georg Brandl wrote: >>> >>> What is the problem with realtime synchronization and working with >>> already up to date Mercurial mirror of central SVN repository? >> >> The s

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 17:09, schrieb Tres Seaver: > Development will continue in SVN > repository until everybody is ready for final migration in X weeks > later. Is that right? No; as soon as we switch, SVN will be read-only. >>> Why don't allow people who already know Mercurial use Mercu

Re: [Python-Dev] Can Python implementations reject semantically invalid expressions?

Am 02.07.2010 18:51, schrieb Craig Citro: >> But you would be taking a module that will compile and making it >> uncompilable. >> > > You're absolutely right, and since I definitely *don't* think that the > program "raise TypeError" should cause a CompileError, you could say > it's safer to have

Re: [Python-Dev] SVN <-> HG workflow to split Python Library by Module

Am 02.07.2010 22:01, schrieb Jesse Noller: >> I am exhausted. > > fwiw - there is a/are plan(s) to break out the stdlib from "core" once > the transition is complete, to better allow re-use between the various > interpreters. I do not think that "lots of small mirrors/repos" for > each library is

Re: [Python-Dev] Mercurial migration readiness

Am 03.07.2010 01:54, schrieb "Martin v. Löwis": >> I don't know about "try" -- personally I don't see a difference for >> the release procedure, no matter where the source comes from. > > I guess you haven't done a release yet, then :-) That's possible :) > Assuming you are going to use > > htt

Re: [Python-Dev] Mercurial migration readiness

Am 04.07.2010 00:59, schrieb "Martin v. Löwis": >> This is perhaps a naive question, but hat do you gain with the >> intermediate mirror clone of upstream? (Other than filling more of your >> disk?) > > In addition to the answer you got: this way of working is also the > process that I arrived at,

Re: [Python-Dev] Mercurial migration readiness

Am 04.07.2010 13:29, schrieb Éric Araujo: > The other risk with history-editing extensions is that they use the > merge and rebase machinery to do their work, so they require a clean > working directory. Otherwise you may loose uncommitted changes. That's true. > Not requiring any Mercurial exten

Re: [Python-Dev] Mercurial migration readiness

Am 04.07.2010 13:53, schrieb Éric Araujo: >>> Not requiring any Mercurial extension to contribute to Python would be a >>> nice policy to lower the entry bar. >> >> That is already defeated by the need for the eol extension (which is now >> built-in in hg 1.6). Activating mq is something every de

Re: [Python-Dev] Mercurial migration readiness

Am 04.07.2010 13:37, schrieb Martin Geisler: > "Martin v. Löwis" writes: > >>> My question is basically the same as Terry Reedy's, but I'm going to >>> phrase it a bit differently: >>> >>> This is perhaps a naive question, but why do you create a second local >>> clone instead of just creating a

Re: [Python-Dev] Thank yous

Am 04.07.2010 22:45, schrieb Jesse Noller: > On Sun, Jul 4, 2010 at 1:26 PM, Tarek Ziadé wrote: >> On Sun, Jul 4, 2010 at 7:16 PM, Paul Moore wrote: >>> On 4 July 2010 17:02, Benjamin Peterson wrote: Now that Python 2.7 is out, I'd like to thank a few of the people who made it possible

Re: [Python-Dev] FWD: error: 3.2 release schedule has release in Jan 2010.

That's now fixed. The time machine disagreed with me. Georg Am 05.07.2010 18:28, schrieb Aahz: > - Forwarded message from Ric Johnson - > >> Date: Mon, 5 Jul 2010 08:49:29 -0700 (PDT) >> From: Ric Johnson >> Subject: error: 3.2 release schedule has release in Jan 2010. >> To: webmas..

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 07.07.2010 18:09, schrieb Michael Foord: >> Hi all, >> >> over on the fellowship o' the packaging mailing list, one of our GSoC >> students >> (merwok) asked about how much formatting info should go into Python >> stdlib >> docstrings. Right now the stdlib docstrings are prima

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 07.07.2010 19:53, schrieb Éric Araujo: >> I promised to write a PEP about that some time in the future. (Probably >> after >> 3.2 final.) > > Nice. > > It seems that projects putting Sphinxy reST in their doc are using > automatic doc generation. This is however not always the best way to >

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 07.07.2010 20:12, schrieb Barry Warsaw: > On Jul 07, 2010, at 07:30 PM, Georg Brandl wrote: > >>Overall, I think that we can make stdlib docstrings valid reST -- even >>if it's reST without much markup -- but valid, so that people pulling >>in stdlib doc- strin

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 07.07.2010 21:11, schrieb Fred Drake: > On Wed, Jul 7, 2010 at 2:27 PM, Georg Brandl wrote: >> I know, and this is what I originally intended for Sphinx. However, the >> calls >> for automatic doc generation are very loud, and it's understandable that most >&

Re: [Python-Dev] versioned .so files for Python 3.2

Am 07.07.2010 20:40, schrieb Barry Warsaw: > Getting back to this after the US holiday. Thanks for running these numbers > Scott. I've opened a bug in the Python tracker and attached my latest patch: > > http://bugs.python.org/issue9193 > > The one difference from previous versions of the patc

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 07.07.2010 21:52, schrieb Brett Cannon: > On Wed, Jul 7, 2010 at 10:30, Georg Brandl wrote: >> Am 07.07.2010 18:09, schrieb Michael Foord: >>>> Hi all, >>>> >>>> over on the fellowship o' the packaging mailing list, one of our GSoC &g

Re: [Python-Dev] versioned .so files for Python 3.2

Am 07.07.2010 23:04, schrieb Georg Brandl: > Am 07.07.2010 20:40, schrieb Barry Warsaw: > >> Getting back to this after the US holiday. Thanks for running these numbers >> Scott. I've opened a bug in the Python tracker and attached my latest patch: >> >&g

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 08.07.2010 17:44, schrieb Martin Geisler: > Steve Holden writes: > >> Martin Geisler wrote: >>> "Stephen J. Turnbull" writes: >>> Just ask Martin, there are too many possibilities here to worry about. If maybe we want it, and he is willing to contribute the parts he wrote to P

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 09.07.2010 00:01, schrieb Fred Drake: > On Thu, Jul 8, 2010 at 5:42 PM, Alexander Belopolsky > wrote: >> I am against mark-up in doc-strings, but this problem can be easily >> solved by placing a magic character at __doc__[0] to indicate that the >> rest is (mini)reST. Ugh. :) > Or __docform

Re: [Python-Dev] New regex module for 3.2?

Am 09.07.2010 02:35, schrieb MRAB: >> That's not what I'm asking. I'm asking what happens if you take an >> existing Python installation's re module, move it aside, and drop >> regex in its place as "re.py". >> >> Doing that and then running Python's own test suite as well as the >> test suites o

Re: [Python-Dev] A grammatical oddity: trailing commas in argument lists.

Am 09.07.2010 18:36, schrieb Eric Smith: > On 7/9/10 10:40 AM, Mark Dickinson wrote: >> While looking at a parser module issue >> (http://bugs.python.org/issue9154) I noticed that Python's grammar >> doesn't permit trailing commas after keyword-only args. That is, >> >> def f(a, b,): pass >>

Re: [Python-Dev] A grammatical oddity: trailing commas in argument lists.

Am 09.07.2010 22:26, schrieb Mark Dickinson: > On Fri, Jul 9, 2010 at 8:37 PM, Dino Viehland wrote: >> Terry wrote: >>> This violates the important principle that allowed def and call arg >>> sequences should match to the extent sensible and possible. In this >>> sense, the SyntaxError is a bug. S

Re: [Python-Dev] Switching dev docs URL to Py3k?

Am 10.07.2010 10:32, schrieb Nick Coghlan: > On Sat, Jul 10, 2010 at 6:27 PM, Antoine Pitrou wrote: >> On Sat, 10 Jul 2010 18:04:32 +1000 >> Nick Coghlan wrote: >> >>> With the trunk closed to new development, should we switch >>> http://docs.python.org/dev/ to show the docs built from the Py3k >

Re: [Python-Dev] Threading bug review + commit privs

Am 11.07.2010 15:23, schrieb Reid Kleckner: > I'm also expecting to be doing more work merging unladen-swallow into > the py3k-jit branch, so I was wondering if I could get commit > privileges for that. Sure -- send your public key to me, and I'll set you up. Georg -- Thus spake the Lord: Thou

Re: [Python-Dev] Removing IDLE from the standard library

Am 11.07.2010 20:59, schrieb Glyph Lefkowitz: > > On Jul 11, 2010, at 2:37 PM, Martin v. Löwis wrote: > >>> Initially (five years ago!) I tried to overcome these issues by >>> improving IDLE, solving problems and adding a few key features. >>> Without going into details, suffice to say that IDLE

Re: [Python-Dev] Removing IDLE from the standard library

Am 12.07.2010 00:51, schrieb Mark Lawrence: > I have been attempting to fill this hole and have been faced with > animosity from people who "hang out" on the python-dev IRC channel. I > thought it was a complete and utter waste of space, so I don't intend > going back. I agree with everything

Re: [Python-Dev] notifications form Hg to python-checkins

Am 14.07.2010 00:00, schrieb Nick Coghlan: > On Wed, Jul 14, 2010 at 7:45 AM, Dirkjan Ochtman wrote: >> On Tue, Jul 13, 2010 at 23:22, Nick Coghlan wrote: >>> No, I meant push. There's a separate discussion where it was pointed >>> out that publishing each commit as a separate email makes >>> pyt

Re: [Python-Dev] python-checkins replies

Am 13.07.2010 22:29, schrieb Brett Cannon: > Given how high traffic python-checkins is I don't consider that a > reasonable place to send follow-up and nor do I consider it the > responsibility of committers to monitor it. As you said earlier > this >

Re: [Python-Dev] New regex module for 3.2?

Am 16.07.2010 17:08, schrieb Vlastimil Brom: > 2010/7/9 Georg Brandl : >> Am 09.07.2010 02:35, schrieb MRAB: >> >>> >>> 1. Some of the inline flags are scoped; for example, putting "(?i)" at >>> the end of a regex will now have no effect becau

Re: [Python-Dev] query: docstring formatting in python distutils code

Am 16.07.2010 22:55, schrieb Terry Reedy: > On 7/7/2010 2:27 PM, Georg Brandl wrote: >> Am 07.07.2010 19:53, schrieb Éric Araujo: >>>> I promised to write a PEP about that some time in the future. (Probably >>>> after >>>> 3.2 final.) > >>

Re: [Python-Dev] IDLE contributors and committers

Am 18.07.2010 00:45, schrieb Mark Lawrence: > On 17/07/2010 22:57, Terry Reedy wrote: >> On 7/17/2010 8:41 AM, Mark Lawrence wrote: >> >>> IIRC Terry Reedy is also interested in moving IDLE forward. >> >> Interested, yes. But until either a) I can commit patches, or b) there >> is someone who will

Re: [Python-Dev] Markup of command-line options in Python's .rst documentation

Am 19.07.2010 04:28, schrieb Eli Bendersky: > On Mon, Jul 19, 2010 at 05:57, Eli Bendersky > wrote: > > On Sat, Jul 17, 2010 at 16:44, Éric Araujo > wrote: > > > The "--help" option appears as a hyperlink leading to > >

Re: [Python-Dev] What to do with languishing patches?

Am 20.07.2010 06:37, schrieb Stephen J. Turnbull: > Mark Lawrence writes: > > > Is this the same login as for the issue tracker or is a new one needed? > > It's different. Both trackers are supposed to support OpenID logins, > I believe. (However, there are somewhat frequent reports of > diffi

Re: [Python-Dev] What to do with languishing patches?

Am 20.07.2010 23:09, schrieb Terry Reedy: > In any case, a module list should be separate from components. > > On 7/20/2010 4:43 PM, Oleg Broytman wrote: > >> In this particular case I'd rather tend to agree - an editable >> single-line box to enter space-*and*-comma-separated modules list wo

Re: [Python-Dev] New regex module for 3.2?

Am 13.07.2010 15:35, schrieb Antoine Pitrou: > On Tue, 13 Jul 2010 15:20:23 +0100 > Michael Foord wrote: >> On 13/07/2010 15:17, Reid Kleckner wrote: >> > On Mon, Jul 12, 2010 at 2:07 PM, Nick Coghlan wrote: >> > >> >> MRAB's module offers a superset of re's features rather than a subset >> >

Re: [Python-Dev] module shutdown procedure

Am 22.07.2010 13:29, schrieb Antoine Pitrou: > Le jeudi 22 juillet 2010 à 07:23 -0500, Benjamin Peterson a écrit : >> 2010/7/22 Antoine Pitrou : >> > On Thu, 22 Jul 2010 08:51:57 +0100 >> > Brett Cannon wrote: >> >> >> >> That's an option. I just remember Tim bringing up something about that >> >>

Re: [Python-Dev] New regex module for 3.2?

Am 22.07.2010 14:12, schrieb Nick Coghlan: > On Thu, Jul 22, 2010 at 9:34 PM, Georg Brandl wrote: >> So, I thought there wasn't a difference in performance for this use case >> (which is compiling a lot of regexes and matching most of them only a >> few times in comp

Re: [Python-Dev] Set the namespace free!

Am 22.07.2010 15:04, schrieb Bartosz Tarnowski: > > Hello, guys. > > Python has more and more reserved words over time. It becomes quite annoying, > since you can not use variables and attributes of such names. Suppose I want > to > make an XML parser that reads a document and returns an objec

Re: [Python-Dev] Set the namespace free!

Am 22.07.2010 21:49, schrieb Reid Kleckner: > On Thu, Jul 22, 2010 at 11:49 AM, Alexander Belopolsky > wrote: >> On Thu, Jul 22, 2010 at 12:53 PM, wrote: >>> I'm very amused by all the jokes about turning python into perl, but there's >>> a good idea here that doesn't actually require that... >>

Re: [Python-Dev] New regex module for 3.2?

Am 23.07.2010 12:20, schrieb Nick Coghlan: > On Fri, Jul 23, 2010 at 8:16 PM, Hrvoje Niksic wrote: >> The performance trade-off should make regex slower with sufficiently small >> compiled regex cache, when a lot of time is wasted on compilation. But as >> the cache gets larger (and, for fairness

Re: [Python-Dev] New regex module for 3.2?

Am 23.07.2010 11:16, schrieb Hrvoje Niksic: > On 07/22/2010 01:34 PM, Georg Brandl wrote: >> Timings (seconds to run the test suite): >> >> re 26.689 26.015 26.008 >> regex 26.066 25.797 25.865 >> >> So, I thought there wasn't a difference i

Re: [Python-Dev] Thoughts fresh after EuroPython

Am 25.07.2010 08:54, schrieb Stefan Behnel: > Nick Coghlan, 25.07.2010 08:29: >> We knew PEP 380 would be hurt by the moratorium when the moratorium >> PEP went through. >> >> The goals of the moratorium itself, in making it possible to have a >> 3.2 release that is fully supported by all of the ma

Re: [Python-Dev] Thoughts fresh after EuroPython

Am 26.07.2010 13:02, schrieb Tarek Ziadé: > On Sat, Jul 24, 2010 at 4:08 PM, Guido van Rossum wrote: > [...] >> - A lot of things seem to be happening to make PyPI better. Is this >> being summarized somewhere? Based on some questions I received during >> my keynote Q&A (http://bit.ly/bdflqa) I th

Re: [Python-Dev] View tracker patches with ViewVC?

Am 26.07.2010 14:41, schrieb Nick Coghlan: > On Mon, Jul 26, 2010 at 10:35 AM, "Martin v. Löwis" > wrote: >> Am 26.07.2010 02:24, schrieb Terry Reedy: >>> To review a patch on the tracker, I have to read and try to make sense >>> of the raw diff file. Sometimes that is easy, sometimes not. >>> >>

Re: [Python-Dev] Readability of hex strings (Was: Use of coding cookie in 3.x stdlib)

Am 26.07.2010 20:42, schrieb Alexandre Vassalotti: > [+Python-ideas -Python-Dev] > > import binascii > def h(s): > return binascii.unhexlify("".join(s.split())) > > h("DE AD BE EF CA FE BA BE") In Py3k: h = bytes.fromhex Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No

Re: [Python-Dev] Fwd: Readability of hex strings (Was: Use of coding cookie in 3.x stdlib)

Am 26.07.2010 22:28, schrieb anatoly techtonik: > Don't you think it is a bad idea to require people to subscribe to > post to python-ideas of redirected there? It doesn't matter *why* you post to a mailing list -- you just have to be subscribed to post. Whoever redirects you there is usually not

Re: [Python-Dev] Define a place for code review in Python workflow

Am 26.07.2010 22:18, schrieb anatoly techtonik: > Small introduction for insiders not familiar with outsider's problem > of maintaining patches in tracker. Please forgive the tone I write > about things I dislike, but I am not devoting my life to earn a title > of polite bastard (this one is oblig

<    1   2   3   4   5   6   7   8   9   10   >