Re: [Python-Dev] some notes from the first part of the lang summit
Brett Cannon wrote: > Could, but the code will go away some day and not everyone will read the > docs to realize that they might want to upgrade their code if they care > to use the shiniest thing in the standard library. I agree with Brett here - PendingDeprecationWarning for "there's a better option available, this approach is probably going to go away some day, but you're in no imminent danger of that happening any time soon". DeprecationWarning is significantly stronger, saying "this will go away some time within the next few years". The softest version (documentation warnings only) doesn't really apply in this case - optparse will almost certainly become a PyPI external package some day, even if that day is a decade or more from now. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial repository for Python benchmarks
Benjamin Peterson wrote: > 2010/2/21 Dirkjan Ochtman : >> I'd be happy to host stuff for people who are already Python >> committers, and limit it to stuff that would otherwise live somewhere >> in Python's svn repository. > > +1 Sounds like a good starting place. This is pretty much the same approach we use for creating subdirectories of /sandbox on the SVN side so it sounds reasonable to me too. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 'languishing' status for the tracker
R. David Murray wrote: > I believe Brett mentioned the 'languishing' status for the tracker in > passing in his notes from the language summit. Thanks for that. I had assumed Brett meant something along those lines, but it is good to have the rationale made explicit. Cheers, Nick. P.S. Not that it's needed, but +1 :) -- Nick Coghlan | [email protected] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
On Sun, Feb 21, 2010 at 23:15, Tarek Ziadé wrote: > Sounds good, thanks It's right here: ssh://[email protected]/repos/distutils2 Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
On Mon, Feb 22, 2010 at 12:04 PM, Dirkjan Ochtman wrote: > On Sun, Feb 21, 2010 at 23:15, Tarek Ziadé wrote: >> Sounds good, thanks > > It's right here: ssh://[email protected]/repos/distutils2 Thanks a lot ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
On Feb 22, 2010, at 12:04 PM, Dirkjan Ochtman wrote: > On Sun, Feb 21, 2010 at 23:15, Tarek Ziadé wrote: >> Sounds good, thanks > > It's right here: ssh://[email protected]/repos/distutils2 The checkout URL for non-ssh read-only access is: http://hg.python.org/distutils2/ in case anyone else is searching for it. S ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
2010/2/22 [email protected] : > The checkout URL for non-ssh read-only access is: > > http://hg.python.org/distutils2/ > > in case anyone else is searching for it. Right. As Maciej asked about this, let's discuss it here: there are currently no emails for these repositories. I'd like to get that going; should I just have it send emails for each push to the normal commits mailing list for now? Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 3.1 and 2.7 break format() when used with complex (sometimes)
This code works on 2.6 and 3.0:
>>> format(1+1j, '10s')
'(1+1j)'
That's because format ends up calling object.__format__ because complex
doesn't have its own __format__. Then object.__format__ calls str(self)
which returns '(1+1j)'. So the original call basically turns into
"format('(1+1j)', '10s')".
In 3.1 (released) and 2.7 (not yet released) I implemented __format__ on
complex. So now that same code is an error:
>>> format(1+1j, '10s')
Traceback (most recent call last):
File "", line 1, in
ValueError: Unknown format code 's' for object of type 'complex'
That's because complex._format__ doesn't recognize string formatting
codes, in particular 's'.
There's a general problem that types that sprout __format__ will break
existing usages of format() that use some string formatting codes,
unless the types recognize string formats in addition to their own. I
think we should change the documentation of format() to warn that you
should really call str() on the first argument if you're relying on the
second argument being a string formatting code.
But what to do about 3.1 and 2.7 with respect to complex? I see 2 options:
1. Leave it as-is, such that 3.1 and 2.7 might break some uses of
format(complex, str).
2. Modify format to understand 's' and do the conversion itself. But we
don't do this for int and float, that's why we added '!s'.
I'm sort of leaning toward #1, but I'd like to know if anyone has an
opinion. I haven't heard of anyone complaining about this yet; it would
only have tripped up people moving from 3.0 -> 3.1, or from 2.6 -> 3.1
who used format (or str.format()) while specifying 's' or some other
str-specific format codes.
Eric.
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial repository for Python benchmarks
On Sun, Feb 21, 2010 at 9:43 PM, Collin Winter wrote: > Hey Daniel, > > On Sun, Feb 21, 2010 at 4:51 PM, Daniel Stutzbach > wrote: >> On Sun, Feb 21, 2010 at 2:28 PM, Collin Winter >> wrote: >>> >>> Would it be possible for us to get a Mercurial repository on >>> python.org for the Unladen Swallow benchmarks? Maciej and I would like >>> to move the benchmark suite out of Unladen Swallow and into >>> python.org, where all implementations can share it and contribute to >>> it. PyPy has been adding some benchmarks to their copy of the Unladen >>> benchmarks, and we'd like to have as well, and Mercurial seems to be >>> an ideal solution to this. >> >> If and when you have a benchmark repository set up, could you announce it >> via a reply to this thread? I'd like to check it out. > > Will do. The benchmarks repository is now available at http://hg.python.org/benchmarks/. It contains all the benchmarks that the Unladen Swallow svn repository contains, including the beginnings of a README.txt that describes the available benchmarks and a quick-start guide for running perf.py (the main interface to the benchmarks). This will eventually contain all the information from http://code.google.com/p/unladen-swallow/wiki/Benchmarks, as well as guidelines on how to write good benchmarks. If you have svn commit access, you should be able to run `hg clone ssh://[email protected]/repos/benchmarks`. I'm not sure how to get read-only access; Dirkjan can comment on that. Still todo: - Replace the static snapshots of 2to3, Mercurial and other hg-based projects with clones of the respective repositories. - Fix the 2to3 and nbody benchmarks to work with Python 2.5 for Jython and PyPy. - Import some of the benchmarks PyPy has been using. Any access problems with the hg repo should be directed to Dirkjan. Thanks so much for getting the repo set up so fast! Thanks, Collin Winter ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 'languishing' status for the tracker
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" / "later" "open" / "postponed" "open" / "remind" I did not find any documentation about them in both places: * http://wiki.python.org/moin/TrackerDocs/ "Tracker documentation" * http://www.python.org/dev/workflow/ "Issue workflow" Maybe these 2 documentation entry points could be merged and improved, first. They are not available on the same menu, and there's no cross-link between them: * "Issue workflow" from http://www.python.org/dev/ * "Tracker documentation" from http://bugs.python.org/ -- Florent Xicluna ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.1 and 2.7 break format() when used with complex (sometimes)
Eric Smith wrote:
This code works on 2.6 and 3.0:
>>> format(1+1j, '10s')
'(1+1j)'
That's because format ends up calling object.__format__ because complex
doesn't have its own __format__. Then object.__format__ calls str(self)
which returns '(1+1j)'. So the original call basically turns into
"format('(1+1j)', '10s')".
Guido pointed out this should have been:
"""That's because format ends up calling object.__format__ because
complex doesn't have its own __format__. Then object.__format__ calls
str(self) which returns '(1+1j)'. So the original call basically turns
into "format('(1+1j)', '10s')".""" (I had inserted the spaces added by
str.__format__ too early.)
We discussed this at the sprint.
We agreed that we'd just allow this specific issue with complex
formatting to possibly break existing uses in 2.7, as it did in 3.1.
While that's unfortunate, it's better than the alternatives.
The root cause of this problem is object.__format__, which is basically:
def __format__(self, fmt):
return str(self).__format__(fmt)
So here we're changing the type of the object (to str) but still keeping
the same format string. That doesn't make any sense: the format string
is type specific. I think the correct thing to do here is to make it an
error if fmt is non-empty. In 2.7 and 3.2 I can make this a
PendingDeprecationWarning, then in 3.3 a DeprecationWarning, and finally
make it an error in 3.4.
Eric.
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial repository for Python benchmarks
On Mon, Feb 22, 2010 at 21:17, Collin Winter wrote: > If you have svn commit access, you should be able to run `hg clone > ssh://[email protected]/repos/benchmarks`. I'm not sure how to get > read-only access; Dirkjan can comment on that. > It would be http://hg.python.org/benchmarks (http, not ssh; no username; no '/repos' toplevel directory.) > > Still todo: > - Replace the static snapshots of 2to3, Mercurial and other hg-based > projects with clones of the respective repositories. > - Fix the 2to3 and nbody benchmarks to work with Python 2.5 for Jython and > PyPy. > - Import some of the benchmarks PyPy has been using. > > Any access problems with the hg repo should be directed to Dirkjan. > Thanks so much for getting the repo set up so fast! > > Thanks, > Collin Winter > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/thomas%40python.org > -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial repository for Python benchmarks
On Mon, Feb 22, 2010 at 15:42, Thomas Wouters wrote: > It would be http://hg.python.org/benchmarks (http, not ssh; no username; no > '/repos' toplevel directory.) Correct. Another todo is to get commit mails; I'm currently working on that. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
> Right. As Maciej asked about this, let's discuss it here: there are > currently no emails for these repositories. I'd like to get that > going; should I just have it send emails for each push to the normal > commits mailing list for now? I think sending them there "for now" is fine; in the long term, I propose to add an X-hgrepo header to the messages so that people can filter on that if they want to. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Sat, Feb 13, 2010 at 2:23 PM, Benjamin Peterson wrote: > 2010/2/13 "Martin v. Löwis" : >> I still think that the best approach for projects to use 2to3 is to run >> 2to3 at install time from a single-source release. For that, projects >> will have to adjust to whatever bugs certain 2to3 releases have, rather >> than requiring users to download a newer version of 2to3 that fixes >> them. For this use case, a tightly-integrated lib2to3 (with that name >> and sole purpose) is the best thing. > > Alright. That is reasonable. > > The other thing is that we will loose some vcs history and some > history granularity by switching development to the trunk version, > since just the svnmerged revisions will be converted. So the consensus is that 2to3 should be pulled out of the main Python tree? Should the 2to3 hg repository be deleted, then? Thanks, Collin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial repository for Python benchmarks
On Mon, Feb 22, 2010 at 3:17 PM, Collin Winter wrote: > The benchmarks repository is now available at > http://hg.python.org/benchmarks/. It contains all the benchmarks that > the Unladen Swallow svn repository contains, including the beginnings > of a README.txt that describes the available benchmarks and a > quick-start guide for running perf.py (the main interface to the > benchmarks). This will eventually contain all the information from > http://code.google.com/p/unladen-swallow/wiki/Benchmarks, as well as > guidelines on how to write good benchmarks. We now have a "Benchmarks" component in the bug tracker. Suggestions for new benchmarks, feature requests for perf.py, and bugs in existing benchmarks should be reported under that component. Thanks, Collin Winter ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
>> The other thing is that we will loose some vcs history and some >> history granularity by switching development to the trunk version, >> since just the svnmerged revisions will be converted. > > So the consensus is that 2to3 should be pulled out of the main Python > tree? Not sure what you mean by "pull out"; I had expect that the right verb should be "pull into": 2to3 should be pulled into the main Python tree. > Should the 2to3 hg repository be deleted, then? Which one? To my knowledge, there is no official 2to3 repository yet. When the switchover happens, 2to3 should not be converted to its own hg repository, yes. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Mon, Feb 22, 2010 at 4:27 PM, "Martin v. Löwis" wrote: >>> The other thing is that we will loose some vcs history and some >>> history granularity by switching development to the trunk version, >>> since just the svnmerged revisions will be converted. >> >> So the consensus is that 2to3 should be pulled out of the main Python >> tree? > > Not sure what you mean by "pull out"; I had expect that the right verb > should be "pull into": 2to3 should be pulled into the main Python tree. Sorry, I meant "pulled out" as in: I want an updated version for the benchmark suite, where should I get that? >> Should the 2to3 hg repository be deleted, then? > > Which one? To my knowledge, there is no official 2to3 repository yet. > When the switchover happens, 2to3 should not be converted to its own hg > repository, yes. This one: http://hg.python.org/2to3 Collin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Mon, Feb 22, 2010 at 16:09, Collin Winter wrote: > So the consensus is that 2to3 should be pulled out of the main Python > tree? Should the 2to3 hg repository be deleted, then? Wouldn't the former be reason to officialize the hg repository, instead of deleting it? Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
On Mon, Feb 22, 2010 at 16:06, "Martin v. Löwis" wrote: > I think sending them there "for now" is fine; in the long term, I > propose to add an X-hgrepo header to the messages so that people can > filter on that if they want to. We get the X-Hg-Notification header (which has the changeset ID) for free. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
Dirkjan Ochtman wrote: > On Mon, Feb 22, 2010 at 16:09, Collin Winter wrote: >> So the consensus is that 2to3 should be pulled out of the main Python >> tree? Should the 2to3 hg repository be deleted, then? > > Wouldn't the former be reason to officialize the hg repository, > instead of deleting it? I think the difference between "pull out" and "pull from" is causing confusion here (and no, I'm not sure which of those Collin actually meant either). Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Mon, Feb 22, 2010 at 5:03 PM, Nick Coghlan wrote: > Dirkjan Ochtman wrote: >> On Mon, Feb 22, 2010 at 16:09, Collin Winter wrote: >>> So the consensus is that 2to3 should be pulled out of the main Python >>> tree? Should the 2to3 hg repository be deleted, then? >> >> Wouldn't the former be reason to officialize the hg repository, >> instead of deleting it? > > I think the difference between "pull out" and "pull from" is causing > confusion here (and no, I'm not sure which of those Collin actually > meant either). Sorry, I meant "pull from". I want an updated snapshot of 2to3 for the benchmark suite, and I'm looking for the best place to grab it from. Collin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Mon, Feb 22, 2010 at 17:05, Collin Winter wrote: > Sorry, I meant "pull from". I want an updated snapshot of 2to3 for the > benchmark suite, and I'm looking for the best place to grab it from. Well, the server that has all the stuff for doing the conversions has annoyingly been down for about 24 hours now. I've got a friend coming in who should hopefully be fixing this tomorrow in the afternoon (Atlanta time), after which I should be able to make my conversion stuff update the hg.p.o repositories with more regularity. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 'languishing' status for the tracker
On Mon, 22 Feb 2010 20:28:41 +, Florent Xicluna wrote: > 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" / "later" > "open" / "postponed" > "open" / "remind" > > I did not find any documentation about them in both places: > * http://wiki.python.org/moin/TrackerDocs/ "Tracker documentation" > * http://www.python.org/dev/workflow/ "Issue workflow" > > Maybe these 2 documentation entry points could be merged and improved, first. > They are not available on the same menu, and there's no cross-link between > them: > * "Issue workflow" from http://www.python.org/dev/ > * "Tracker documentation" from http://bugs.python.org/ There is a plan to improve the dev docs, and to merge a bunch of stuff that is scattered here and there into them. Brett will presumably add this item to his his punch list if it isn't already on it; thanks for pointing it out. It's a good question what the difference between 'later' and 'postponed' is. I'm guessing that 'later' is equivalent to 'languishing' (ie: its a good idea but nobody wants to do it right now), while 'postponed' is for something that needs to wait until the next release is out the door, or something like that. There is exactly one open ticket with 'remind' set (by Skip, issue 1374063), and 10 closed tickets. I'll review the closed tickets and move them to languishing if appropriate. I suspect remind is not a particularly useful resolution value. It would probably be better as a keyword. So I would suggest removing the resolutions 'later' and 'remind', and adding a 'remind' keyword if anyone speaks up as wanting it. Postponed I think is useful for the 'wait for next release' case on open tickets, although again it might be more useful as a keyword (it isn't really a 'resolution'). --David ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Mercurial move?
An advantage of being at PyCon :) We *may* be able to get on mercurial very fast -- since all of the interested parties are here. I'm going to get an svndump now -- the downside to this is whatever anyone checks in during this in between stage would need to get re-checked in after we move. I'll let you know how it goes. -Frank ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial move?
On Mon, Feb 22, 2010 at 5:45 PM, Frank Wierzbicki wrote: > An advantage of being at PyCon :) > > We *may* be able to get on mercurial very fast -- since all of the > interested parties are here. I'm going to get an svndump now -- the > downside to this is whatever anyone checks in during this in between > stage would need to get re-checked in after we move. > > I'll let you know how it goes. Sorry python-dev autocomplete fail -- I meant this to go to jython-dev, sorry. Please ignore. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
Dirkjan Ochtman writes: Hi everybody! I hope you have fun at PyCon :-) > As for the current state of The Dreaded EOL Issue, there is an > extension which seems to be provide all the needed features, but it > appears there are some nasty corner cases still to be fixed. Martin > Geisler has been working on it over the sprint, but I think there's > more work to be done here. Anyone who wants to jump in would be quite > welcome (maybe Martin will clarify here what exactly the remaining > issues are). I'm sorry about the delay in my response -- but things have now finally moved forward after Benoit Boissinot (another Mercurial developer) looked at things. With the most recent fixes pushed to the eol repository[1], I can no longer break the tests by running them repeatedly in a loop. In other words, they finally appear to be stable. I feel this would be a good opportunity for people to begin testing the extension again. It seems that people has not done that so far, or at least we haven't gotten any feedback in a long time. It is now easier to test than before since changes to the .hgeol file is picked up immediatedly without it being committed. This means that you can enable eol (in .hg/hgrc, say) and play around *without* affecting others who use the repository. When you change patterns in .hgeol, you'll see the effects in the output of 'hg status' -- files that will be updated on the next commit appear modified. My dissertation is due this Friday(!), so I will not have much time to look at EOL issues this week (as usual). But please give it a spin anyway and let us hear what you think! [1]: http://bitbucket.org/mg/hg-eol/ -- Martin Geisler pgpQwH8TBxAhw.pgp Description: PGP signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial move?
On Mon, Feb 22, 2010 at 5:57 PM, Frank Wierzbicki wrote: > On Mon, Feb 22, 2010 at 5:45 PM, Frank Wierzbicki > wrote: >> An advantage of being at PyCon :) >> >> We *may* be able to get on mercurial very fast -- since all of the >> interested parties are here. I'm going to get an svndump now -- the >> downside to this is whatever anyone checks in during this in between >> stage would need to get re-checked in after we move. >> >> I'll let you know how it goes. > Sorry python-dev autocomplete fail -- I meant this to go to > jython-dev, sorry. Please ignore. In that case congrats on beating us to the punch! Let us know how it goes. -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Mon, Feb 22, 2010 at 18:38, Martin Geisler wrote: > My dissertation is due this Friday(!), so I will not have much time to > look at EOL issues this week (as usual). But please give it a spin > anyway and let us hear what you think! I've got about 48 more hours of PyCon sprints ahead of me, so if anyone comes up with bugs (preferably concrete and reproducible) in that time frame, I can look into them more or less directly. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
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" / "later" > "open" / "postponed" > "open" / "remind" Those are taken from SourceForge, and I'm not sure we need all of them, as David says. :) But the point of the "languishing" status is really to not have them in your results when searching for open issues. Searching for "open, but not with one of these three resolutions" is much harder. > I did not find any documentation about them in both places: > * http://wiki.python.org/moin/TrackerDocs/ "Tracker documentation" > * http://www.python.org/dev/workflow/ "Issue workflow" As David says, I have a plan to consolidate the dev docs and bring them into the source repo. Of course, just because it is my plan, it doesn't need to be done by me :) Aren't there people sprinting somewhere? :) Georg ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] small suggestion for a sprint project
Somebody at the sprint looking for a thankless task of drudgery could resolve the current svnmerge queue into the py3k branch. -- Regards, Benjamin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 'languishing' status for the tracker
On Tue, 23 Feb 2010 01:35:03 +0100, Georg Brandl wrote: > Am 22.02.2010 21:28, schrieb Florent Xicluna: > > I did not find any documentation about them in both places: > > * http://wiki.python.org/moin/TrackerDocs/ "Tracker documentation" > > * http://www.python.org/dev/workflow/ "Issue workflow" > > As David says, I have a plan to consolidate the dev docs and bring them > into the source repo. Of course, just because it is my plan, it doesn't > need to be done by me :) > > Aren't there people sprinting somewhere? :) Yeah, but none of the people who are good at driving doc stuff (you or Brett or Ezio) are here :) --David ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
>>> Should the 2to3 hg repository be deleted, then? >> Which one? To my knowledge, there is no official 2to3 repository yet. >> When the switchover happens, 2to3 should not be converted to its own hg >> repository, yes. > > This one: http://hg.python.org/2to3 Ah, this shouldn't be used at all for anything (except for studying how Mercurial works). Along with the cpython repository, it is Dirkjan's test conversion. Even if it survived the ultimate migration (which it probably won't), it would get regenerated from scratch, probably changing all revision numbers. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
> Sorry, I meant "pull from". I want an updated snapshot of 2to3 for the > benchmark suite, and I'm looking for the best place to grab it from. The 2to3 code currently still lives in the subversion sandbox. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
Dirkjan Ochtman wrote: > On Mon, Feb 22, 2010 at 16:06, "Martin v. Löwis" wrote: >> I think sending them there "for now" is fine; in the long term, I >> propose to add an X-hgrepo header to the messages so that people can >> filter on that if they want to. > > We get the X-Hg-Notification header (which has the changeset ID) for free. Can I use that to filter out distutils2 commits? Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Tue, Feb 23, 2010 at 00:55, "Martin v. Löwis" wrote: > Ah, this shouldn't be used at all for anything (except for studying how > Mercurial works). Along with the cpython repository, it is Dirkjan's > test conversion. Even if it survived the ultimate migration (which it > probably won't), it would get regenerated from scratch, probably > changing all revision numbers. Actually, since this one is much simpler, it's more or less ready to be the canonical repository, if Benjamin would like that. It's very different from the cpython repository in that respect. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
On Tue, Feb 23, 2010 at 00:57, "Martin v. Löwis" wrote: > Can I use that to filter out distutils2 commits? Well, I don't think we'll do commit emails for distutils2 or unittest2, only for benchmarks (to python-checkins, anyway). I'll make sure that you can filter something out by repository. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
> On Tue, Feb 23, 2010 at 00:55, "Martin v. Löwis" wrote: >> Ah, this shouldn't be used at all for anything (except for studying how >> Mercurial works). Along with the cpython repository, it is Dirkjan's >> test conversion. Even if it survived the ultimate migration (which it >> probably won't), it would get regenerated from scratch, probably >> changing all revision numbers. > > Actually, since this one is much simpler, it's more or less ready to > be the canonical repository, if Benjamin would like that. It's very > different from the cpython repository in that respect. I thought we decided not to have a 2to3 repository at all, but let this live in the Python trunk exclusively. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 385 progress report
On Tue, Feb 23, 2010 at 01:06, "Martin v. Löwis" wrote: > I thought we decided not to have a 2to3 repository at all, but let this > live in the Python trunk exclusively. That would be fine with me, I just remembered that Benjamin would like to start using hg sooner and having it as a separate repo was okay. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
On Tue, Feb 23, 2010 at 1:04 AM, Dirkjan Ochtman wrote: > On Tue, Feb 23, 2010 at 00:57, "Martin v. Löwis" wrote: >> Can I use that to filter out distutils2 commits? > > Well, I don't think we'll do commit emails for distutils2 or > unittest2, only for benchmarks (to python-checkins, anyway). I'll make > sure that you can filter something out by repository. Why is that ? I do want them as much as someone else would want the benchmarks ones I suppose. The whole subversion repository (including the sandbox) is sending mails to python-checkins, so I think we need to have the same policy here if possible, and use for example a subject prefix to make the filtering easier (which should be simpler with multiple mercurial repositories as a matter of fact) Tarek -- Tarek Ziadé | http://ziade.org ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
2010/2/23 Tarek Ziadé : > Why is that ? I do want them as much as someone else would want the > benchmarks ones I suppose. > > The whole subversion repository (including the sandbox) is sending > mails to python-checkins, so I think we need to have the same policy > here if possible, and use for example a subject prefix to make the > filtering easier (which should be simpler with multiple mercurial > repositories as a matter of fact) Some people expressed doubts, but maybe that was mainly about unittest2, not distutils2. I don't actually care either way. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
2010/2/23 Dirkjan Ochtman : > 2010/2/23 Tarek Ziadé : >> Why is that ? I do want them as much as someone else would want the >> benchmarks ones I suppose. >> >> The whole subversion repository (including the sandbox) is sending >> mails to python-checkins, so I think we need to have the same policy >> here if possible, and use for example a subject prefix to make the >> filtering easier (which should be simpler with multiple mercurial >> repositories as a matter of fact) > > Some people expressed doubts, but maybe that was mainly about > unittest2, not distutils2. I don't actually care either way. Note sure what do you mean by doubts. I have no doubts I want to receive those emails to work on this code ;) Tarek ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
2010/2/23 Tarek Ziadé : > Note sure what do you mean by doubts. I have no doubts I want to > receive those emails to work on this code ;) Some of the other committers didn't think they wanted email on python-checkins from all the projects that will ever be hosted on hg.python.org, so there should be some selection. I'll let you fight with them over where the email from distutils2 goes; I'm just maintaining this. Cheers, Dirkjan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Another mercurial repo
2010/2/23 Dirkjan Ochtman : > 2010/2/23 Tarek Ziadé : >> Note sure what do you mean by doubts. I have no doubts I want to >> receive those emails to work on this code ;) > > Some of the other committers didn't think they wanted email on > python-checkins from all the projects that will ever be hosted on > hg.python.org, so there should be some selection. I'll let you fight > with them over where the email from distutils2 goes; I'm just > maintaining this. Sorry I didn't mean to stress you on this, I just want to make sure I'll be able to get those mails at some point. The solution, I think, is to create one checking mailing list per hosted project at hg.python.org. And possibly reunite several projects under a single mailing list. Let me know if it fits your maintenance process. if so I'll ask for a mailing list for this particular repo. Thanks for your work, Tarek -- Tarek Ziadé | http://ziade.org ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
