For example, let's project dates for closing 2.6 and 3.0 now, and add
them to PEP 361.
My view is that they should be closed when 2.7 and 3.1 are released.
Following another informal policy, we were going for an 18 months
release cycle at some time (2.6 clearly took longer), which would
mean
On 2008-08-14 08:43, Martin v. Löwis wrote:
For example, let's project dates for closing 2.6 and 3.0 now, and add
them to PEP 361.
My view is that they should be closed when 2.7 and 3.1 are released.
Since we don't have a fixed release cycle, making the 2.(n-1)
maintenance time frame depend
Jesus Cea wrote:
I plan to release pybsddb 4.7.3 in mid-september, ready to be delivered
bundled in Python 2.6/3.0 (to be released early in october).
Jesus, I think your target date is off by a month - it may be better to
try and land an initial cut of this in Python SVN for beta 3 (August
The goal
should be to produce something like a unittest-ng, distribute it via
the Cheeseshop, and gather consensus around it for possible inclusion
in Python 2.7/3.1.
IMO test support in Python needs some enhancements. I also think there
are great libraries available today in
On Aug 14, 2008, at 8:13 AM, Olemis Lang wrote:
What I do think is that we need a mail list (or equivalent) dedicated
to discuss such things... because (again IMO) python-dev might not be
It's not, but this list is the right place:
http://lists.idyll.org/listinfo/testing-in-python
-Fred
Hi,
I thought I'd bring this up on both the tracker and mailing list, since it's
important. It seems the test suite breaks as of r65661. I've posted details
to the bug tracker and a patch which fixes the module in question (uuid.py).
http://bugs.python.org/issue3552
Cheers
Matt
Abstract
This PEP proposes frequently-requested additions to the standard
library `unittest` module that are natural extensions of its existing
functionality.
I had not seen this proposal... I will post a few comments.
Motivation
==
The
I was going through our list of email addreses for committers and
realized that I don't have an address for john.benediktsson that
works; his ewtllc.com address is bouncing. Anyone have an up-to-date
one?
-Brett
___
Python-Dev mailing list
Christian Heimes wrote:
Perhaps we could adopt a release plan similar to Ubuntu. They have
releases with cool, new and bleeding edge stuff followed by a release
that focuses on stability and long term support. Python 2.6 and
especially 3.0 are releases with new features. What do you think
Brett Cannon wrote:
I was going through our list of email addreses for committers and
realized that I don't have an address for john.benediktsson that
works; his ewtllc.com address is bouncing. Anyone have an up-to-date
one?
Replied privately.
___
On Thu, Aug 14, 2008, M.-A. Lemburg wrote:
On 2008-08-14 08:43, Martin v. L?wis wrote:
For example, let's project dates for closing 2.6 and 3.0 now, and add
them to PEP 361.
My view is that they should be closed when 2.7 and 3.1 are released.
Since we don't have a fixed release cycle, making
11 matches
Mail list logo
