On Sun, Oct 16, 2011 at 6:10 AM, Terry Reedy wrote:
> On 10/15/2011 7:47 AM, "Martin v. Löwis" wrote:
>>
>> This may be a done deal, but: no. If a patch is reverted, the NEWS entry
>> that got in with it gets out again on reversal. The NEWS file
>> is for users of the release; there is no point te
On 13 October 2011 17:25, Éric Araujo wrote:
>> My expectation would be that the user would type pysetup install
>> some_binary_format_file.zip and have that file unpacked and all the
>> "bits" put in the appropriate place. Basically just like installing
>> from a source archive - pysetup install
Jeremy Kloth gmail.com> writes:
> That said, I have been working on a drop-in replacement for the current
> bdist_wininst executable stub with the following features:
[snip]
> http://www.flickr.com/photos/67460826 N04/sets/72157627653603530/
[snip]
Sounds interesting, but your flickr link di
Martin v. Löwis v.loewis.de> writes:
> In particular wrt. virtual environments: I see no need to actually
> *install* files multiple times. It's rather sufficient that the
> distributions to be installed are *available* in the virtual env after
> installation, and unavailable after being removed
Nick Coghlan gmail.com> writes:
> Compilation can be a problem on Linux systems as well, so a platform
> neutral format is a better idea. Just have a mechanism that allows
> pysetup to create a bdist_msi from a bdist_simple. Similar, bdist_rpm
> and bdist_deb plugins could be taught to interpret
Éric Araujo netwok.org> writes:
> [Vinay]
> > A simple change to packaging will allow an archive containing a
> > setup.cfg-based > > directory to be installed in the same way as a
> > source directory.
> Isn’t that already supported, as long as the tarball or zipfile contains
> source files? In
Paul Moore gmail.com> writes:
>
> On 13 October 2011 17:25, Éric Araujo netwok.org> wrote:
> >> My expectation would be that the user would type pysetup install
> >> some_binary_format_file.zip and have that file unpacked and all the
> >> "bits" put in the appropriate place. Basically just like
On 16 October 2011 22:32, Vinay Sajip wrote:
> There's one area of pysetup3 functionality which I don't think has been
> discussed in this thread, though it's pertinent to Windows users. Namely, a
> completely declarative approach to installation locations will not satisfy all
> requirements. For
On Sunday, October 16, 2011 02:24:58 PM Vinay Sajip wrote:
> Jeremy Kloth gmail.com> writes:
> > That said, I have been working on a drop-in replacement for the current
>
> > bdist_wininst executable stub with the following features:
> [snip]
>
> > http://www.flickr.com/photos/67460826 N04/se
Hi,
I don't understand why we kept modules of the plat-* directories (e.g.
Lib/plat-linux/CDROM.py). It looks like these modules are not used, except
maybe some DL constants used by PyKDE4. Can't we move used constants to
classic Python modules (e.g. the os module) and drop unused modules?
The
Le lundi 17 octobre 2011 01:16:36, Victor Stinner a écrit :
> For example, IN.INT_MAX is 2147483647, whereas it should
> be 9223372036854775807 on my 64-bit Linux.
Oops, wrong example: INT_MAX is also 2147483647 on 64 bits. I mean
IN.LONG_MAX.
IN.LONG_MAX is always 9223372036854775807 on Linux,
11 matches
Mail list logo
