On Wed, Feb 9, 2011 at 9:21 PM, Terry Reedy tjre...@udel.edu wrote:
On 2/9/2011 12:32 PM, s...@pobox.com wrote:
Passing this along from webmaster.
It is hard to reply to an attachment rather than inline forwarded message.
However, with rc1
import sqlite3
sqlite3.version
'2.6.0'
On Thu, Feb 10, 2011 at 10:08 PM, Georg Brandl g.bra...@gmx.net wrote:
Am 10.02.2011 19:27, schrieb Brett Cannon:
On Wed, Feb 9, 2011 at 23:10, Georg Brandl g.bra...@gmx.net wrote:
Am 09.02.2011 23:58, schrieb brett.cannon:
brett.cannon pushed 7101df1bd817 to devguide:
Well, it's no good to keep using CVCS terms and mislead users. That the
checkout is not a checkout but a full repository is about the most important
fact about a hg (or any DVCS) clone.
Well, to really use the Mercurial terms, what you have when you get
stuff from a remote server to your disk
import sqlite3
sqlite3.version
'2.6.0'
sqlite3.sqlite_version
'3.7.4'
That's not intuitive. It is better to point sqlite3.version to the
actual version of sqlite3 used.
We can’t break compatibility for such a small thing. However, it should
be documented in
I would like the next release called 3.2.0 rather than just 3.2.
'x.y' is known to be ambiguous and confusing.
In most actual usages, I believe, it refers to the latest x.y.z release.
On the site, the 'x.y' docs are almost always the latest version of the
docs (actually x.y.z+additional
On Wed, Feb 16, 2011 at 09:34, Terry Reedy tjre...@udel.edu wrote:
I would like the next release called 3.2.0 rather than just 3.2.
'x.y' is known to be ambiguous and confusing.
In most actual usages, I believe, it refers to the latest x.y.z release. On
the site, the 'x.y' docs are almost
On Feb 16, 2011, at 12:34 PM, Terry Reedy wrote:
I would like the next release called 3.2.0 rather than just 3.2.
+1
(I'd have said +0 for the humor of it :).
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
On Thu, Feb 17, 2011 at 5:05 AM, Barry Warsaw ba...@python.org wrote:
On Feb 16, 2011, at 12:34 PM, Terry Reedy wrote:
I would like the next release called 3.2.0 rather than just 3.2.
+1
(I'd have said +0 for the humor of it :).
+0
I actually *am* only +0, since I like the idea in
Le mercredi 16 février 2011 à 14:05 -0500, Barry Warsaw a écrit :
On Feb 16, 2011, at 12:34 PM, Terry Reedy wrote:
I would like the next release called 3.2.0 rather than just 3.2.
+1
(I'd have said +0 for the humor of it :).
Should we write +1.0, +1.3 or just +1? Mark can maybe
On Wed, 2011-02-16 at 12:34 -0500, Terry Reedy wrote:
I would like the next release called 3.2.0 rather than just 3.2.
- -1
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Feb 16, 2011, at 2:39 PM, Nick Coghlan wrote:
On Thu, Feb 17, 2011 at 5:05 AM, Barry Warsaw ba...@python.org wrote:
On Feb 16, 2011, at 12:34 PM, Terry Reedy wrote:
I would like the next release called 3.2.0 rather than just 3.2.
+1
(I'd have said +0 for the humor of it :).
+0
On 2/16/2011 5:39 PM, Nick Coghlan wrote:
On Thu, Feb 17, 2011 at 5:05 AM, Barry Warsawba...@python.org wrote:
On Feb 16, 2011, at 12:34 PM, Terry Reedy wrote:
I would like the next release called 3.2.0 rather than just 3.2.
+1
(I'd have said +0 for the humor of it :).
+0
I actually
Am 17.02.2011 03:08, schrieb Raymond Hettinger:
On Feb 16, 2011, at 2:39 PM, Nick Coghlan wrote:
On Thu, Feb 17, 2011 at 5:05 AM, Barry Warsaw ba...@python.org wrote:
On Feb 16, 2011, at 12:34 PM, Terry Reedy wrote:
I would like the next release called 3.2.0 rather than just 3.2.
+1
On Thu, Feb 17, 2011 at 1:34 AM, Terry Reedy tjre...@udel.edu wrote:
'x.y' is known to be ambiguous and confusing.
Not really.
x.y seems to be saying it is a milestone (major release) and we all
have got used to that convention.
In most actual usages, I believe, it refers to the latest x.y.z
14 matches
Mail list logo
