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 host
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
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
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 ex
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'l
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 rep
> 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),
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.
Che
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 wou
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
> 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
Py
>>> 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
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
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
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsu
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" / "
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
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
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 -- t
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 b
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 l
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.
> "
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
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 rea
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
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
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
___
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
>> 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 me
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 bench
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 release
> 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
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
__
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://h...@hg.python.org/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
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 tur
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
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 Swall
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
2010/2/22 sstein...@gmail.com :
> 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 g
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://h...@hg.python.org/repos/distutils2
The checkout URL for non-ssh read-only access is:
http://hg.python.org/distutils2/
in case
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://h...@hg.python.org/repos/distutils2
Thanks a lot
___
Python-Dev mailing list
Python-Dev@pytho
On Sun, Feb 21, 2010 at 23:15, Tarek Ziadé wrote:
> Sounds good, thanks
It's right here: ssh://h...@hg.python.org/repos/distutils2
Cheers,
Dirkjan
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Uns
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 tha
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 app
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 op
44 matches
Mail list logo
