On Jan 11, 2010, at 8:01 PM, David Lyon wrote:
> When I run the same thing:
>
>> import platform
>> platform.machine()
>> 'x86'
Just as a data point, I get:
import platform
platform.machine()
'i386'
on a dual processor quad core Mac Pro.
S
___
Distu
Martin,
> py> import platform
> py> platform.machine()
> 'i686'
>
> 'i686' maps very well to a real machine on the market, namely to the
> machine on which I'm typing this right now.
Ok.
When I run the same thing:
>import platform
>platform.machine()
>'x86'
So what is being proposed isn
>>> Haven't seen a '386 for over ten years.. Intel have standardised
>>> to calling everything 'Pentium' pretty much since at least 2000.
>> Irrelevant:
>
> I don't see how it is irrelevent that the constants don't
> map to any 'real' machines on the market.
Why do you say that?
py> import platf
>> > os.machine == 'i386'
>
> It should be platform.machine, not os.machine.
>
>> Haven't seen a '386 for over ten years.. Intel have standardised
>> to calling everything 'Pentium' pretty much since at least 2000.
>
> Irrelevant:
I don't see how it is irrelevent that the constants don't
map to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Gabriele wrote:
> On Tue, Jan 5, 2010 at 10:44 PM, David Lyon wrote:
>> Hi John,
>>
>>> What is expected to be the standard way to do this in the near future?
>> PEP-345 says:
>>
>> > Requires-Dist: pywin32 (>1.0); sys.platform == 'win32'
>> >
On Wed, Jan 6, 2010 at 3:35 PM, John Gabriele wrote:
> On Tue, Jan 5, 2010 at 10:44 PM, David Lyon wrote:
>>
>> Hi John,
>>
>>> What is expected to be the standard way to do this in the near future?
>>
>> PEP-345 says:
>>
>> > Requires-Dist: pywin32 (>1.0); sys.platform == 'win32'
>> > Obsolete
On 1/6/2010 8:23 AM, John Gabriele wrote:
On Wed, Jan 6, 2010 at 11:07 AM, Carl Meyer wrote:
>
> {snip} Following the principle of least surprise I would assume
> they would be requires_dist, provides_dist, etc, and would take lists of
> strings, in the same format as in the PEP (name follow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi John,
Isn't distutils-sig fun? Ask a simple question, get a recycled rant that
doesn't answer your question... ;-)
John Gabriele wrote:
[snip]
> I'm a bit confused myself... PEP-345 says it "describes a mechanism
> for adding metadata to Python pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Gabriele wrote:
> Great. Thanks. Then, I'd like to put:
>
> requires_dist=['CoolStuff>=2.0.0', 'ReallyNeatStuff>=1.5.5'],
>
> into my `setup()` call. Currenlty, I've got this at the top of my `setup.py`:
>
> from distutils.core import s
On Wed, Jan 6, 2010 at 11:07 AM, Carl Meyer wrote:
>
> {snip} Following the principle of least surprise I would assume
> they would be requires_dist, provides_dist, etc, and would take lists of
> strings, in the same format as in the PEP (name followed by version spec
> in parenths).
> {snip}
>
>>
Hello John
I'll attempt to actually answer your question instead of just voicing
disagreement with a current proposal about meta-data.
On Tue, Jan 05, 2010 at 10:29:45PM -0500, John Gabriele wrote:
> What is currently the preferred way to specify (in your simple
> setup.py file) that your distrib
On Tue, Jan 5, 2010 at 10:44 PM, David Lyon wrote:
>
> Hi John,
>
>> What is expected to be the standard way to do this in the near future?
>
> PEP-345 says:
>
> > Requires-Dist: pywin32 (>1.0); sys.platform == 'win32'
> > Obsoletes-Dist: pywin31; sys.platform == 'win32'
> > Requires-Dist: foo
> > os.machine == 'i386'
It should be platform.machine, not os.machine.
> Haven't seen a '386 for over ten years.. Intel have standardised
> to calling everything 'Pentium' pretty much since at least 2000.
Irrelevant:
Python 2.5.4 (r254:67916, Nov 19 2009, 19:46:21)
[GCC 4.3.4] on linux2
Type
Hi John,
> What is expected to be the standard way to do this in the near future?
PEP-345 says:
> Requires-Dist: pywin32 (>1.0); sys.platform == 'win32'
> Obsoletes-Dist: pywin31; sys.platform == 'win32'
> Requires-Dist: foo (1,!=1.3); os.machine == 'i386'
> Requires-Dist: bar; python_versi
Hi,
What is currently the preferred way to specify (in your simple
setup.py file) that your distribution depends upon a couple of other
distributions? (All located at the PyPI)
What is expected to be the standard way to do this in the near future?
Also, is it better to specify that your distribu
15 matches
Mail list logo
