On Sep 12, 2010, at 04:10 PM, Martin v. Löwis wrote:
>> Does PEP 3149 have any advantage for Windows installations?
>
>I don't see any immediate advantage. The problem that the PEP addresses
>typically doesn't exist on Windows.
Cool.
>>> 2. Why does the PEP recommend installing stuff
>>> into /u
> If it's useful on unix like systems, why shouldn't it be useful on
> windows? Multiple versions of python can be installed on windows
> too. And people might also like to share their packages between
> installations.
Multiple versions of Python install into distinct directories, so
extension mod
> I only mandated ./configure-based builds to be PEP 3149 conforming. I have no
> objection to expanding the PEP to include Windows builds, but I'm not sure
> it's necessary and it would take a Windows build expert to make and test those
> changes.
>
> Does PEP 3149 have any advantage for Windows
On Sep 08, 2010, at 09:42 AM, Ralf Schmitt wrote:
>If it's useful on unix like systems, why shouldn't it be useful on
>windows? Multiple versions of python can be installed on windows
>too. And people might also like to share their packages between
>installations.
I guess the point is *I* don't k
On Wed, Sep 8, 2010 at 5:42 PM, Ralf Schmitt wrote:
> Barry Warsaw writes:
>
>>
>> Section added:
>>
>> Windows
>> ===
>>
>> This PEP only addresses build issues on POSIX systems that use the
>> ``configure`` script. While Windows or other platform support is not
>> explicitly disallowed und
Barry Warsaw writes:
>
> Section added:
>
> Windows
> ===
>
> This PEP only addresses build issues on POSIX systems that use the
> ``configure`` script. While Windows or other platform support is not
> explicitly disallowed under this PEP, platform expertise is needed in
> order to evaluate,
On Sep 05, 2010, at 11:39 PM, Martin v. Löwis wrote:
>Notice, however, that the PEP also talks about creating different names
>for different compilation options of the same Python binary. This
>applies to Windows as well (as the PEP actually points out: there is
>_d.pyd and .pyd).
>
>In any case,
On Sep 06, 2010, at 03:40 PM, David Cournapeau wrote:
>Reading the related paragraph in the PEP, it seems to me that the use
>of package as in "these distributions install third party (i.e.
>non-standard library) packages ..." is too vague.
Rephrased as:
[...]these distributions install thir
On Sep 05, 2010, at 07:22 PM, Martin v. Löwis wrote:
>I know the PEP is accepted, but I would still like to see some
>changes/clarifications.
>
>1. What is the effect of this PEP on Windows? Is this a Linux-only
> feature? If not, who is going to provide the changes for Windows?
> (More specif
[Georg Brandl, 2010-09-05]
> Am 05.09.2010 19:22, schrieb "Martin v. Löwis":
> > 2. Why does the PEP recommend installing stuff into /usr/share/pyshared?
> >According to the Linux FHS, /usr/share is for Architecture-
> >independent data, see
> >
> > http://www.pathname.com/fhs/pub/fhs-2.3.
On Mon, Sep 6, 2010 at 3:16 AM, Georg Brandl wrote:
> Am 05.09.2010 19:22, schrieb "Martin v. Löwis":
>> I know the PEP is accepted, but I would still like to see some
>> changes/clarifications.
>>
>> 1. What is the effect of this PEP on Windows? Is this a Linux-only
>> feature? If not, who is
>> 1. What is the effect of this PEP on Windows? Is this a Linux-only
>>feature? If not, who is going to provide the changes for Windows?
>>(More specifically: if this is indeed meant for Windows, and
>>if no Windows implementation arrives before 3.2b1, I'd ask that
>>the changes be
Am 05.09.2010 19:22, schrieb "Martin v. Löwis":
> I know the PEP is accepted, but I would still like to see some
> changes/clarifications.
>
> 1. What is the effect of this PEP on Windows? Is this a Linux-only
>feature? If not, who is going to provide the changes for Windows?
>(More specif
I know the PEP is accepted, but I would still like to see some
changes/clarifications.
1. What is the effect of this PEP on Windows? Is this a Linux-only
feature? If not, who is going to provide the changes for Windows?
(More specifically: if this is indeed meant for Windows, and
if no Wi
14 matches
Mail list logo
