Let's improve the tracker UI to better fit our needs. Then, classify
them bugs and separate garbage from real development. Lastly, bug
reporters should get a better UI. That's it, any help is welcome.
The plan sounds great. I can help with the deployment aspects (reviewing
tracker patches,
Hello all,
Issue 5287 is a patch for the logging module for compatibility with
IronPython. IronPython provides sys._getframe but it throws an exception
if you call it with a non-zero depth. This may be fixed in a future
version of IronPython.
http://bugs.python.org/issue5287
It doesn't at all
Le Tuesday 17 February 2009 08:52:20 Lennart Regebro, vous avez écrit :
On Tue, Feb 17, 2009 at 00:50, Guido van Rossum gu...@python.org 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
Michael Foord wrote:
Hello all,
Issue 5287 is a patch for the logging module for compatibility with
IronPython. IronPython provides sys._getframe but it throws an exception
if you call it with a non-zero depth. This may be fixed in a future
version of IronPython.
Victor Stinner wrote:
Le Tuesday 17 February 2009 08:52:20 Lennart Regebro, vous avez écrit :
On Tue, Feb 17, 2009 at 00:50, Guido van Rossum gu...@python.org wrote:
Can you explain the difficulty with porting setuptools in more detail?
Oh, it just exposes a bug in distutils.
On Tue, 17 Feb 2009 11:04:35 +1300, Greg Ewing wrote:
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
On 15 Feb, 2009, at 21:13, Daniel (ajax) Diniz wrote:
Hi,
In the discussion of a feature request for MacPython[1], the OP
(hhas) said:
As of Python 2.6/3.0, all Mac-specific modules are deprecated/
eliminated
from the standard library and there are no longer any plans to
submit
Benjamin Peterson schrieb:
On Sun, Feb 15, 2009 at 10:59 AM, Guido van Rossum gu...@python.org wrote...
Something like this?
3.1a1 March 7
3.1a2 April 4
3.1b1 May 2
3.1rc1 May 30
3.1rc2 June 13
3.1 Final June 27
That sounds reasonable. I will try to enforce a fairly strict
On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se wrote:
Didn't a test fail because of this? seems the underlying issue is that this
part of the stdlib didn't have enough test coverage. It seems that having
very good/improving test coverage like is recommended for 3rd-party
Dear Python Group,
First of all sorry for the unsolicited email,
I have attached two very interesting long term Python projects in the
Frankfurt area, Financial industry.
I am working exclusively with the client on both requirements,
interviews and contracts can be arranged very
On Tue, Feb 17, 2009 at 7:55 AM, Gregor Lingl gregor.li...@aon.at wrote:
I've started a list on the release PEP [1].
[1] http://www.python.org/dev/peps/pep-0375/
Is the intention to release 2.7 and 3.1 in parallel?
No.
I suspect, comparing this to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 17, 2009, at 8:55 AM, Gregor Lingl wrote:
Is the intention to release 2.7 and 3.1 in parallel?
I don't think we should this time. We want to get 3.1 out sooner than
the typical 18 month development cycle, and I think we should
Dear Python Development Group,
First of all sorry for the unsolicited email,
I have attached two very interesting long term Python projects in the
Frankfurt area, Financial industry.
I am working exclusively with the client on both requirements,
interviews and contracts can be arranged
Paul Moore wrote:
2009/2/16 Daniel (ajax) Diniz aja...@gmail.com:
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
Hi Ned,
Ned Deily wrote:
Other than Mac/Modules, the rest of the Mac/ directory is mainly stuff
used for building or going into the OS X installer images, including
things like IDLE.app. These are used in 2.x and in 3.x.
Thanks, knowing that makes the ticket handling easier!
There are 40 C
On Tue, Feb 17, 2009, David Russell wrote:
Dear Python Development Group,
First of all sorry for the unsolicited email,
This is spam, and you have now jeopardized your correct posting to the
Python Job Board. The other website administrators will be informed and
we will discuss whether
Hi, Ronald,
Ronald Oussoren wrote:
On 15 Feb, 2009, at 21:13, Daniel (ajax) Diniz wrote:
Hi,
In the discussion of a feature request for MacPython[1], the OP (hhas) said:
As of Python 2.6/3.0, all Mac-specific modules are deprecated/eliminated
from the standard library and there are
Brett Cannon wrote:
Ditto from me! And I will eventually get to the bugs assigned to me
(hopefully starting some time this week).
No hurry, just let me know if you see stupid mistakes on my part (I've
once or twice added an issue as its own dependency) :)
Daniel
Jack Jansen wrote:
I had a cursory look at these issues as they came by, and I didn't see any
that struck me as still being relevant.
Thanks a lot for the feedback, Jack!
Daniel
___
Python-Dev mailing list
Python-Dev@python.org
Dear Aahz,
I understand your point but the line should be drawn between somebody
selling Viagra or insurance to someone like me who is offering an
opportunity to a suitable candidate to work on a Python project
developing a new global trading system for a world leading financial
institution.
I
[Aahz]
...
This is spam, and you have now jeopardized your correct posting to the
Python Job Board. The other website administrators will be informed and
we will discuss whether spamming python-dev warrants withdrawing it.
To be fair, a python-dev moderator approved the posting, so in their
David:
Perhaps you'd like to give me your company's internal mailing list
address so I can drop your staff a line when I hear of Python
conferences going on your area. Or maybe that's not what the list is for?
This list, as is clearly stated at
http://www.python.org/community/lists/
is for
Steve Holden wrote:
David:
Perhaps you'd like to give me your company's internal mailing list
address so I can drop your staff a line when I hear of Python
conferences going on your area. Or maybe that's not what the list is for?
[...]
Just to close this out Aahz and I received an
Tim Peters wrote:
[Aahz]
...
This is spam, and you have now jeopardized your correct posting to the
Python Job Board. The other website administrators will be informed and
we will discuss whether spamming python-dev warrants withdrawing it.
To be fair, a python-dev moderator approved
On 17/02/2009 17:55, Steve Holden wrote:
is for work on developing Python. Hence your posting (and your
protestations of innocence) is unsolicited commercial email, AKA spam.
Python users who are looking for jobs know about the jobs board, where
you have already submitted vacancy notices (now
A few months ago there was a discussion [1] about changing
Python's long integer type to use base 2**30 instead of base
2**15. http://bugs.python.org/issue4258 was opened for this.
With much help from many people (but especially Antoine
and Victor), I've finally managed to put together an
I'd like to get this in for 3.1. Any objections or comments?
Can you please upload it to Rietveld also?
Is this PEP territory?
I don't think so.
Martin
___
Python-Dev mailing list
Python-Dev@python.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thinking again about 3.0.2.
If we'd like to do bug fix releases before Pycon, I suggest Monday
March 9th for code freeze and tagging. That would mean a Tuesday
March 10th release.
What do you think?
Barry
-BEGIN PGP SIGNATURE-
On Tue, Feb 17, 2009 at 7:49 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Can you please upload it to Rietveld also?
Will do. I'm getting a 500 Server Error at the moment, but I'll keep trying.
Mark
___
Python-Dev mailing list
Python-Dev@python.org
Use the upload.py script (/static/upload.py) rather than the Create Issue page.
On Tue, Feb 17, 2009 at 12:36 PM, Mark Dickinson dicki...@gmail.com wrote:
On Tue, Feb 17, 2009 at 7:49 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Can you please upload it to Rietveld also?
Will do. I'm
On Tue, Feb 17, 2009 at 8:42 PM, Guido van Rossum gu...@python.org wrote:
Use the upload.py script (/static/upload.py) rather than the Create Issue
page.
Thanks. That worked.
http://codereview.appspot.com/14105
___
Python-Dev mailing list
Benjamin Peterson schrieb:
On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se wrote:
Didn't a test fail because of this? seems the underlying issue is that this
part of the stdlib didn't have enough test coverage. It seems that having
very good/improving test coverage like is
On Mon, 16 Feb 2009, Daniel (ajax) Diniz wrote:
http://bugs.python.org/issue809887 Improve pdb breakpoint feedback
Why this one?
John
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Tue, Feb 17, 2009 at 3:02 PM, Georg Brandl g.bra...@gmx.net wrote:
Benjamin Peterson schrieb:
On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se wrote:
Didn't a test fail because of this? seems the underlying issue is that this
part of the stdlib didn't have enough test
If someone sets the -3 option to get py3k warnings, should the classic division
warning get turned-on automatically?
Right now, I get no warnings for:
python -3 -c 9 / 5
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
On Tue, Feb 17, 2009 at 4:50 PM, Raymond Hettinger pyt...@rcn.com wrote:
If someone sets the -3 option to get py3k warnings, should the classic
division warning get turned-on automatically?
Right now, I get no warnings for:
python -3 -c 9 / 5
I think you have a point.
--
--Guido van
John J Lee wrote:
On Mon, 16 Feb 2009, Daniel (ajax) Diniz wrote:
http://bugs.python.org/issue809887 Improve pdb breakpoint feedback
Why this one?
Nice catch, this makes no sense. The patch even applies almost
cleanly. I'll update it and set the others to pending, so further
objections can
On Tue, Feb 17, 2009 at 00:15, Martin v. Löwis mar...@v.loewis.de wrote:
Let's improve the tracker UI to better fit our needs. Then, classify
them bugs and separate garbage from real development. Lastly, bug
reporters should get a better UI. That's it, any help is welcome.
The plan
38 matches
Mail list logo
