Am 18.08.2010 20:59, schrieb "Martin v. Löwis":
> Am 18.08.2010 17:11, schrieb Michael Foord:
>> Could (and should) the online Python 3.1 docs be updated to show Python
>> 2.7 as stable?
>
> I think the answer is "no, it could not".
>
> How many old documentation sets would you want to go through
On 18/08/2010 21:59, "Martin v. Löwis" wrote:
Am 18.08.2010 17:11, schrieb Michael Foord:
Could (and should) the online Python 3.1 docs be updated to show Python
2.7 as stable?
I think the answer is "no, it could not".
How many old documentation sets would you want to go through, and
Am 18.08.2010 17:11, schrieb Michael Foord:
> Could (and should) the online Python 3.1 docs be updated to show Python
> 2.7 as stable?
I think the answer is "no, it could not".
How many old documentation sets would you want to go through, and
regenerate them? There is also
http://docs.python.org
Could (and should) the online Python 3.1 docs be updated to show Python
2.7 as stable?
All the best,
Michael
Original Message
Subject:Old link text in documentation
Date: Sun, 15 Aug 2010 15:49:34 -0700
From: Aaron DeVore
To: webmas...@python.org
The link
On Tue, Aug 17, 2010 at 7:00 PM, Benjamin Peterson wrote:
> 2010/8/17 martin.v.loewis :
>> Author: martin.v.loewis
>> Date: Wed Aug 18 00:58:42 2010
>> New Revision: 84166
>>
>> Log:
>> Add Ask Solem.
>>
>>
>> Modified:
>> python/branches/py3k/Misc/developers.txt
>>
>> Modified: python/branches/
Michael Foord wrote:
> On 18/08/2010 15:34, Neal Becker wrote:
>> Is there any proposal to accommodate having parallel-installed multiple
>> versions of modules?
You can easily implement such a setup by placing the module versions
into a separate dir and then adding the right version dir to you
sy
On 18/08/2010 15:34, Neal Becker wrote:
Is there any proposal to accommodate having parallel-installed multiple
versions of modules?
I have client code in multiple projects using version x.y of a C-compiled
module A.
I want to test a new version x.z of module A, but all client software needs
to
Is there any proposal to accommodate having parallel-installed multiple
versions of modules?
I have client code in multiple projects using version x.y of a C-compiled
module A.
I want to test a new version x.z of module A, but all client software needs
to be recompiled against the new version.