Re: [Python-Dev] No 2.x->3.x porting documentation?

> I'm making a naive stab at converting nose to Python3 so I can hopefully run > the lockfile test cases under Python 3. (Again, I'm offline and have no > idea at this point if it's been done already.) I ran 2to3 then tried > installing. I got an immediate error about the compiler.consts module

Re: [Python-Dev] No 2.x->3.x porting documentation?

pobox.com> writes: > > I'm making a naive stab at converting nose to Python3 so I can hopefully run > the lockfile test cases under Python 3. Apparently, Jason Pellerin has started a py3k branch for the same purpose: http://groups.google.com/group/nose-dev/browse_thread/thread/621c3767bbce3abc h

Re: [Python-Dev] Adding T_SIZET to structmember.h

Martin, I was not clear enough. Please, just tell me: Do you believe that this addition do make sense? Would you reject it for some reason (other than a bad patch) ? On Fri, Feb 13, 2009 at 10:35 PM, "Martin v. Löwis" wrote: >> Mark, the patch is not trivial, I cannot spend time on this until thi

Re: [Python-Dev] RELEASED Python 3.0.1

On Sun, Feb 15, 2009 at 9:15 PM, Ned Deily wrote: > > It would be great if someone could add OS X links for the 3.0.1 and > 2.6.1 to the main download page, too: > I've now added them to the main download page. -- Regards, Benjamin

Re: [Python-Dev] Mark old distutils as deprecated

2009/2/9 M.-A. Lemburg : > On 2009-02-08 11:15, Tarek Ziadé wrote: >> Hello >> >> To avoid confusion, as suggested by Akira who works on cleaning the >> Distutils pages on the python.org website, >> I would like to move http://svn.python.org/view/distutils/trunk into a >> branch and add a README.tx

Re: [Python-Dev] Irix still supported? (was Re: Tracker archeology)

Daniel (ajax) Diniz wrote: > Can I close these other IRIX issues? > > http://bugs.python.org/issue2048 > http://bugs.python.org/issue1086642 > http://bugs.python.org/issue1178510 > http://bugs.python.org/issue1070140 So, I'll close these later this week (citing that "Irix is long dead and we don't

[Python-Dev] Issues to be closed: objections?

Hi, I've marked some issues (25 now) to close, mostly because: - there was no reply from OP, nor a clear justification for the issue; - there are messages explaining why the issue is invalid; - the OSes/versions of the report suggest the issue is currently invalid; However, I've been mistaken abou

Re: [Python-Dev] Mark old distutils as deprecated

On 2009-02-16 17:54, Tarek Ziadé wrote: > 2009/2/9 M.-A. Lemburg : >> On 2009-02-08 11:15, Tarek Ziadé wrote: >>> Hello >>> >>> To avoid confusion, as suggested by Akira who works on cleaning the >>> Distutils pages on the python.org website, >>> I would like to move http://svn.python.org/view/dist

Re: [Python-Dev] Issues to be closed: objections?

On 2009-02-16 18:50, Daniel (ajax) Diniz wrote: > Hi, > I've marked some issues (25 now) to close, mostly because: > - there was no reply from OP, nor a clear justification for the issue; > - there are messages explaining why the issue is invalid; > - the OSes/versions of the report suggest the iss

Re: [Python-Dev] Issues to be closed: objections?

M.-A. Lemburg wrote: >> http://bugs.python.org/issue1231081 platform.processor() could be smarter Thanks, Marc-Andre! If anyone else feels like closing some of these issues, go ahead (no need to report back, I'll find it out later). My rather bureaucratic approach is just to avoid a possible trig

Re: [Python-Dev] Buildbots for 2.6 and 3.0

Martin v. Löwis wrote: Looking at http://www.python.org/dev/buildbot/, we are still missing buildbots for the release26-maint and release30-maint branches. Is someone working on that? Yes. I won't enable 2.6 build slaves until 2.5.3 is released, but will afterwards. How does one actually dow

[Python-Dev] To 3.0.2 or not to 3.0.2?

I discovered some remaining cmp() in 3.0.1, 38 minutes after Benjamin fixed them. :) Unfortunately, that means porting setuptools to 3.0.1 will be a bit difficult. So my question is: Will there be a 3.0.2 with those fixes, or should I add workaround code for 3.0.1? -- Lennart Regebro: Pythonista,

[Python-Dev] Tracker cleanup report

Hi, Here's a summary of what's been accomplished and what's almost done. This kinda marks the end of this Bug Season for me, but I'd like to do at least one more installment before PyCon. We have closed 51 issues so far (sorry if I missed some): * Barry ** Benja

Re: [Python-Dev] Wow!

On Fri, Feb 13, 2009 at 9:14 PM, Greg Ewing wrote: > Also it sounds like they could do with a really good > garbage collection algorithm just now. If only we had a second Earth to mess with, we could just copy and swap. -- Cheers, Leif ___ Python-Dev

Re: [Python-Dev] Issues to be closed: objections?

Daniel (ajax) Diniz wrote: Hi, I've marked some issues (25 now) to close, mostly because: - there was no reply from OP, nor a clear justification for the issue; - there are messages explaining why the issue is invalid; - the OSes/versions of the report suggest the issue is currently invalid; How

Re: [Python-Dev] Tracker cleanup report

2009/2/16 Daniel (ajax) Diniz : > Hi, > Here's a summary of what's been accomplished and what's almost done. > This kinda marks the end of this Bug Season for me, but I'd like to do > at least one more installment before PyCon. Can I, for one, offer a *huge* round of applause for what you've achie

Re: [Python-Dev] Issues to be closed: objections?

On Mon, Feb 16, 2009 at 2:14 PM, Terry Reedy wrote: > Daniel (ajax) Diniz wrote: >> >> Hi, >> I've marked some issues (25 now) to close, mostly because: >> - there was no reply from OP, nor a clear justification for the issue; >> - there are messages explaining why the issue is invalid; >> - the O

Re: [Python-Dev] Tracker cleanup report

On Mon, Feb 16, 2009 at 12:37, Paul Moore wrote: > 2009/2/16 Daniel (ajax) Diniz : > > Hi, > > Here's a summary of what's been accomplished and what's almost done. > > This kinda marks the end of this Bug Season for me, but I'd like to do > > at least one more installment before PyCon. > > Can I,

Re: [Python-Dev] Tracker cleanup report

Paul Moore wrote: > 2009/2/16 Daniel (ajax) Diniz : >> Hi, >> Here's a summary of what's been accomplished and what's almost done. >> This kinda marks the end of this Bug Season for me, but I'd like to do >> at least one more installment before PyCon. > > Can I, for one, offer a *huge* round of ap

Re: [Python-Dev] Adding T_SIZET to structmember.h

> Martin, I was not clear enough. Please, just tell me: Do you believe > that this addition do make sense? Would you reject it for some reason > (other than a bad patch) ? I would be +0. All other integral types support both signed and signed fields, why not size_t. Regards, Martin __

Re: [Python-Dev] Tracker cleanup report

On 16-Feb-2009, at 20:40 , Daniel (ajax) Diniz wrote: There are about 20 Mac-related, 24 invalid/outdated and four IRIX issues on the 'will be closed unless someone voices disagreement' queue, so we have a good chance of totaling a hundred closed issues in ten days. I had a cursory look at

Re: [Python-Dev] Wow!

Leif Walsh wrote: If only we had a second Earth to mess with, we could just copy and swap. Or we could use a generational approach, doing all our messy stuff around the moon and copying to earth when we've got our traffic control issues sorted out. -- Greg

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

[Resend, hopefully bag.python.org is fixed now.[ Can you explain the difficulty with porting setuptools in more detail? On Mon, Feb 16, 2009 at 11:08 AM, Lennart Regebro wrote: > I discovered some remaining cmp() in 3.0.1, 38 minutes after Benjamin > fixed them. :) Unfortunately, that means port

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

On Mon, Feb 16, 2009 at 5:50 PM, Guido van Rossum wrote: > Can you explain the difficulty with porting setuptools in more detail? Basically setuptools invokes a functions in distutils that was still using cmp(). (See the latest messages in issue #1717 for all the details.) -- Regards, Benjami

[Python-Dev] Anyone want to lead the sprints at PyCon this year?

Or am I doing it again as usual because I was stupid enough to ask this question? -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

FWIW; I think a 3.0.2 would be useful socially (even volunteer projects have marketting issues to consider). It says "we are committed to making 3.x work", while the quick jump to 3.1 with only a limited minor fix release to 3.0 says "we stumbled into this and have to just brush this under the rug.

[Python-Dev] Tracker cleanup roadmap

This is the janitorial plan I mentioned earlier... It's so humongously huge by now that I'm not sure whether I should submit it to e.g. the Python Papers or just print it and set it on fire and run screaming. Fortunately, a tl;dl summary is provided :) Daniel Summary Let's improve the tracker UI

Re: [Python-Dev] Issues to be closed: objections?

Daniel (ajax) Diniz writes: > M.-A. Lemburg wrote: > >> http://bugs.python.org/issue1231081 platform.processor() could be smarter > > Thanks, Marc-Andre! > > If anyone else feels like closing some of these issues, go ahead (no > need to report back, I'll find it out later). My rather burea

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

On Tue, Feb 17, 2009 at 00:50, Guido van Rossum wrote: > Can you explain the difficulty with porting setuptools in more detail? Oh, it just exposes a bug in distutils. It probably means I'll have to make a test for python version, and if it is 3.0.1, monkey-patch distutils. I haven't really looke