[Python-checkins] commit of r41744 - in python/trunk: Doc/api/init.texModules/getbuildinfo.c Python/sysmodule.c
M.-A. Lemburg
mal at egenix.com
Mon Dec 19 15:13:56 CET 2005
Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
>> Martin v. Löwis wrote:
>>
>>> M.-A. Lemburg wrote:
>>>
>>>> It's the users of tools which use the final distributed versions
>>>> which would run into problems they can't easily solve.
>>> In the final distributed version, this code is dead: there won't
>>> be a .svn directory to get information from.
>>
>> Sorry, I was talking about compiled distributions versions.
>
> Neither was I: I was talking about the final distributed
> source versions. They will not contain a .svn directory,
> as they will be created through svn export.
>
>> These will contain the build number, right ?
>
> My current view is that the answer to this question is "no";
> the build number should go away.
>
>> Or should we tell people to only distribute compiled versions
>> that were created from the source distribution ? (which then
>> have the .svn dir and thus no issues)
Shouldn't be writing emails late at night. This should have
read: (which then *don't* have the .svn dir and thus no issues)
> No, the source distribution will not be a subversion working
> copy, just as it previously never was a CVS sandbox (i.e.
> it never contained a CVS directory).
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1, Dec 19 2005)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
________________________________________________________________________
::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
More information about the Python-checkins
mailing list