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 any 'real'
On Thu, Jan 7, 2010 at 00:17, Barry Warsaw ba...@python.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have a Python package called 'munepy' https://launchpad.net/munepy which
provides yet another flavor of enums. I'm working on the code for various
reasons and I thought I'd
On Jan 7, 2010, at 6:09 AM, Lennart Regebro wrote:
...
use_2to3 = True,
convert_2to3_doctests = [
'munepy/docs/README.txt',
],
...
but I never see that the README.txt is ever 'fixed'. Indeed, the test fails
because of a syntax error when the doctest tries to
This quote is taken from the distutils thread current preferred way
to specify dependencies? future?,
On Wed, Jan 6, 2010 at 10:55 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Wed, Jan 6, 2010 at 3:35 PM, John Gabriele jmg3...@gmail.com wrote:
I'm a bit confused myself... PEP-345 says it
Brad Allen wrote:
This quote is taken from the distutils thread current preferred way
to specify dependencies? future?,
On Wed, Jan 6, 2010 at 10:55 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Wed, Jan 6, 2010 at 3:35 PM, John Gabriele jmg3...@gmail.com wrote:
I'm a bit confused myself...
On Thu, Jan 7, 2010 at 12:48 PM, Eric Smith e...@trueblade.com wrote:
[..]
Normally the word 'distribution' is reserved for what lands in the
'dist' directory, such as a tarball or an egg...right?
Right.
We should use the terminology as defined in
Tarek Ziadé wrote:
On Thu, Jan 7, 2010 at 12:48 PM, Eric Smith e...@trueblade.com wrote:
[..]
Normally the word 'distribution' is reserved for what lands in the
'dist' directory, such as a tarball or an egg...right?
Right.
We should use the terminology as defined in
Hi Tarek
On Wed, Jan 06, 2010 at 06:13:21PM +0100, Tarek Ziadé wrote:
Besides the PEP-related features, I would like to add some tiny
features in Distutils for Python 2.7 before the alpha stage is over :
- a test command, that just uses the new unittest discovery to run
unittest-compatible
On Thu, Jan 7, 2010 at 12:31, Barry Warsaw ba...@python.org wrote:
Hi Lennart, thanks for the response. However, I don't think this is quite
it. I read this in the docs and deleted the entire build directory. Then
when I re-run the tests I can see that the .py files get fixed but it never
On Thu, Jan 7, 2010 at 7:03 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Thu, Jan 7, 2010 at 12:48 PM, Eric Smith e...@trueblade.com wrote:
[..]
We should use the terminology as defined in
http://docs.python.org/distutils/introduction.html#distutils-specific-terminology
So technically
On Thu, Jan 7, 2010 at 3:52 PM, John Gabriele jmg3...@gmail.com wrote:
The only inconsistency, I think, is that operating systems like Debian
refer to their software distributions as packages (as in, a packaged
up piece of software that you can download and install). Packages is
a great name
On Thu, Jan 7, 2010 at 9:56 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Thu, Jan 7, 2010 at 3:52 PM, John Gabriele jmg3...@gmail.com wrote:
The only inconsistency, I think, is that operating systems like Debian
refer to their software distributions as packages (as in, a packaged
up piece
On Thu, Jan 7, 2010 at 1:44 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
Hi Tarek
On Wed, Jan 06, 2010 at 06:13:21PM +0100, Tarek Ziadé wrote:
Besides the PEP-related features, I would like to add some tiny
features in Distutils for Python 2.7 before the alpha stage is over :
-
On Jan 07, 2010, at 02:34 PM, Lennart Regebro wrote:
I just checked out munepy, and tried it, and with me the problem is
that it doesn't even copy it. That's because Distribute sees any
non-python file as Package data, which means you have to set
include_package_data = True in setup().
Ah yes,
On Thu, Jan 7, 2010 at 9:12 AM, John Gabriele jmg3...@gmail.com wrote:
On Thu, Jan 7, 2010 at 9:56 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Thu, Jan 7, 2010 at 3:52 PM, John Gabriele jmg3...@gmail.com wrote:
The only inconsistency, I think, is that operating systems like Debian
refer to
At 10:29 AM 1/7/2010 -0600, Brad Allen wrote:
On Thu, Jan 7, 2010 at 9:12 AM, John Gabriele jmg3...@gmail.com wrote:
On Thu, Jan 7, 2010 at 9:56 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Thu, Jan 7, 2010 at 3:52 PM, John Gabriele jmg3...@gmail.com wrote:
The only inconsistency, I think,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
This quote is taken from the distutils thread current preferred way
to specify dependencies? future?,
On Wed, Jan 6, 2010 at 10:55 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Wed, Jan 6, 2010 at 3:35 PM, John Gabriele
On Thu, Jan 07, 2010 at 04:25:52PM +0100, Tarek Ziadé wrote:
On Thu, Jan 7, 2010 at 1:44 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
Hi Tarek
On Wed, Jan 06, 2010 at 06:13:21PM +0100, Tarek Ziadé wrote:
Besides the PEP-related features, I would like to add some tiny
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 platform
py
8614 *projects*, some of which have one or more *versions*, which in
turn may have one or more source or binary *distributions*.
Instead of version, I really like PyPI's term more: *releases*.
As for projects: fine with me; PyPI would then be the Python Project
Index.
Regards,
Martin
At 09:20 PM 1/7/2010 +0100, Martin v. Löwis wrote:
8614 *projects*, some of which have one or more *versions*, which in
turn may have one or more source or binary *distributions*.
Instead of version, I really like PyPI's term more: *releases*.
Not all versions are released versions, so I
Instead of version, I really like PyPI's term more: *releases*.
Not all versions are released versions
Actually, from a PyPI point of view, they are :-)
Regards,
Martin
___
Distutils-SIG maillist - Distutils-SIG@python.org
On Thu, Jan 7, 2010 at 2:40 PM, P.J. Eby p...@telecommunity.com wrote:
As for projects: fine with me; PyPI would then be the Python Project
Index.
+1
If this gets general agreement, there are probably some places where
the word 'package' should be replaced with the word 'project', right?
For
On Thu, Jan 7, 2010 at 10:29 PM, Brad Allen bradallen...@gmail.com wrote:
On Thu, Jan 7, 2010 at 2:40 PM, P.J. Eby p...@telecommunity.com wrote:
As for projects: fine with me; PyPI would then be the Python Project
Index.
+1
If this gets general agreement, there are probably some places
Tarek Ziadé wrote:
On Thu, Jan 7, 2010 at 10:29 PM, Brad Allen bradallen...@gmail.com wrote:
On Thu, Jan 7, 2010 at 2:40 PM, P.J. Eby p...@telecommunity.com wrote:
As for projects: fine with me; PyPI would then be the Python Project
Index.
+1
If this gets general agreement, there are
On Thu, Jan 7, 2010 at 3:51 PM, M.-A. Lemburg m...@egenix.com wrote:
I don't think we need to change anything - most Python software
components come as Python packages nowadays, so the terminology
'package' we've used all these years is correct.
Do you mean only 'package' in the sense of an
Brad Allen wrote:
On Thu, Jan 7, 2010 at 2:40 PM, P.J. Eby p...@telecommunity.com wrote:
As for projects: fine with me; PyPI would then be the Python Project
Index.
+1
If this gets general agreement, there are probably some places where
the word 'package' should be replaced with the word
Brad Allen wrote:
On Thu, Jan 7, 2010 at 3:51 PM, M.-A. Lemburg m...@egenix.com wrote:
I don't think we need to change anything - most Python software
components come as Python packages nowadays, so the terminology
'package' we've used all these years is correct.
Do you mean only
28 matches
Mail list logo
