Re: [Python-Dev] python 3.2 (fwd)
On Wed, Feb 9, 2011 at 9:21 PM, Terry Reedy wrote: > On 2/9/2011 12:32 PM, [email protected] 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' sqlite3.sqlite_version > '3.7.4' That's not intuitive. It is better to point sqlite3.version to the actual version of sqlite3 used. -- anatoly t. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] devguide: Fix a silly statement.
On Thu, Feb 10, 2011 at 10:08 PM, Georg Brandl wrote: > Am 10.02.2011 19:27, schrieb Brett Cannon: >> On Wed, Feb 9, 2011 at 23:10, Georg Brandl wrote: >>> Am 09.02.2011 23:58, schrieb brett.cannon: brett.cannon pushed 7101df1bd817 to devguide: http://hg.python.org/devguide/rev/7101df1bd817 changeset: 291:7101df1bd817 branch: hg_transition tag: tip user: Brett Cannon date: Wed Feb 09 14:58:17 2011 -0800 summary: Fix a silly statement. files: setup.rst diff --git a/setup.rst b/setup.rst --- a/setup.rst +++ b/setup.rst @@ -34,8 +34,7 @@ :abbr:`VCS`. It also means you will have better tool support through the VCS as it will provide a diff tool, etc. -To get a read-only checkout of CPython's source, you need a working copy the -source code. To get a read-only checkout of +To get a read-only checkout of the :ref:`in-development ` branch of Python, run:: hg clone http://hg.python.org/cpython >>> >>> This statement is still somewhat silly, as a) you get a clone, not a >>> checkout >>> and b) it is not read only in any way: you can commit just fine. The only >>> difference will be the entry in .hg/hgrc pointing the default repo to >>> something >>> you can't push to. >>> >>> Skimming through, the whole section "Checking out the code" is still way too >>> SVN-point of viewy (e.g. you always get all branches anyway). >> >> I'll take another pass, but do realize this needs to be something that >> can easily be understood by someone who has never used hg before, so I >> can't get too technically accurate while ignoring a possible base >> ignorance of hg and DVCSs as a whole. > > 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. +1 -- anatoly t. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] devguide: Fix a silly statement.
> 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 is a clone, which contains a full repository and may contain a working copy (also called checkout). IOW, “check out” is used with Mercurial, as a synonym for “update”, an operation from the (local) repo to the working directory; the CVCS-inspired mistake is to use that to refer to an operation from a remote server to the local disk (“clone”, “pull”). HTH Regards ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python 3.2 (fwd)
> 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 http://docs.python.org/dev/library/sqlite3#module-functions-and-constants Could you report the bug? Thanks in advance. Regards ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 3.2.0
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 fixes). In discussions on python-list, for instance, advice to use 'x.y' means to download and use the latest x.y.z release, not the initial x.y(.0) release. Similarly on the tracker, 'what happens with x.y' means the same. So the alternate use of 'x.y' to mean x.y(.0) is both confusing and correctable, at least for the future. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
On Wed, Feb 16, 2011 at 09:34, Terry Reedy 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 always the latest version of the docs > (actually x.y.z+additional fixes). In discussions on python-list, for > instance, advice to use 'x.y' means to download and use the latest x.y.z > release, not the initial x.y(.0) release. Similarly on the tracker, 'what > happens with x.y' means the same. > > So the alternate use of 'x.y' to mean x.y(.0) is both confusing and > correctable, at least for the future. With all of the writing I have been doing recently, I agree that disambiguating 3.2.0 from 3.2 is a good thing. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
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 [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
On Thu, Feb 17, 2011 at 5:05 AM, Barry Warsaw 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 principle, but it is Georg, Ronald and Martin that would need to do the work, and I'm not sure it's a great idea to be messing with it a couple of days out from the release. So it may be better to do this for 3.3.0, rather than 3.2.0. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
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 help us on this question. Victor ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
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 [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
On Feb 16, 2011, at 2:39 PM, Nick Coghlan wrote: > On Thu, Feb 17, 2011 at 5:05 AM, Barry Warsaw 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 principle, but it is > Georg, Ronald and Martin that would need to do the work, and I'm not > sure it's a great idea to be messing with it a couple of days out from > the release. So it may be better to do this for 3.3.0, rather than > 3.2.0. The basic idea is reasonable, but it's a little late in the game to make any changes. This is ready to ship and we're doing our best to make no changes at all to RC3. The web page and announcement can say 3.2.0 but I'm opposed to changing anything in the release at this point. We have some real bugfixes that we're delaying until 3.2.1, so why would we make an exception for a non-essential changes such as this. Raymond ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
On 2/16/2011 5:39 PM, Nick Coghlan wrote: On Thu, Feb 17, 2011 at 5:05 AM, Barry Warsaw 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 principle, but it is Georg, Ronald and Martin that would need to do the work, and I'm not sure it's a great idea to be messing with it a couple of days out from the release. So it may be better to do this for 3.3.0, rather than 3.2.0. My immediate suggestion is predicated on the assumption that it would be easy and safe to change '3.2rc2' in the various places it appears to '3.2.0' instead of '3.2'. If that is not true, then my suggestion is that after 3.2 is released, that trunk be regarded as 3.3.0a0 rather than 3.3a0 as soon as it make any difference anywhere. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
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 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 principle, but it is >> Georg, Ronald and Martin that would need to do the work, and I'm not >> sure it's a great idea to be messing with it a couple of days out from >> the release. So it may be better to do this for 3.3.0, rather than >> 3.2.0. > > The basic idea is reasonable, but it's a little late in the game to make > any changes. This is ready to ship and we're doing our best > to make no changes at all to RC3. > > The web page and announcement can say 3.2.0 but I'm opposed to > changing anything in the release at this point. We have some > real bugfixes that we're delaying until 3.2.1, so why would we > make an exception for a non-essential changes such as this. Quite right. I will see where I can put "3.2.0" on the website, but I will not fiddle with the release tools (much of this is automated) at this stage in the process. Georg ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.2.0
On Thu, Feb 17, 2011 at 1:34 AM, Terry Reedy 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 release. On While I agree with all these points, I feel calling the release itself as x.y.0 may be distracting the convention which is being followed so far. So, it is -1 from me. In the mailing list we can say that use the 'latest' of python 2.x version or 'latest' of python 3.x version and on the web-pages, pointers can be properly set to the correct version. -- Senthil ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
