On Feb 2, 2011, at 2:49 PM, Matt Chaput wrote:
> Is there a way to set this value to "py2.5" as a configuration option, other
> than running setup.py using the Python 2.5 executable? Or not have it be part
> of the egg filename at all? I'm using Python 2.7 as my default Python install
> but I m
At 10:17 AM 2/3/2011 -0500, Matt Chaput wrote:
When I create an egg the Python version used to create the egg is
encoded in the egg filename, e.g. Whoosh-1.6.0-py2.7.egg.
Is this version number used to decide what egg a user gets from
PyPI? I didn't think it was, but a user is seeming to indic
On 03/02/2011 11:28 AM, Carl Meyer wrote:
On 02/03/2011 11:24 AM, Matt Chaput wrote:
Can people still use easy_install/pip to install it if it's not an egg?
Yes. In fact, pip can only install from source distributions.
Interesting. So long bdist_egg!
Thanks all,
Matt
__
On 02/03/2011 11:24 AM, Matt Chaput wrote:
> Can people still use easy_install/pip to install it if it's not an egg?
Yes. In fact, pip can only install from source distributions.
A source .tar.gz is the most broadly-compatible distribution format
available, unless your package includes compiled e
I use buildout, which uses setuptools/distribute. So for that, the answer is
yes.
"Matt Chaput" wrote:
>On 03/02/2011 10:34 AM, Eric Smith wrote:
>> I use source distributions (python setup.py sdist) and then
>distribute
>> the resulting .tar.gz file. Since it's a source (not binary)
>> distr
On 03/02/2011 10:34 AM, Eric Smith wrote:
I use source distributions (python setup.py sdist) and then distribute
the resulting .tar.gz file. Since it's a source (not binary)
distribution, it can potentially run with any version of Python.
You see this a lot on PyPI, where the only thing uploaded
On 02/03/2011 10:17 AM, Matt Chaput wrote:
When I create an egg the Python version used to create the egg is encoded in
the egg filename, e.g. Whoosh-1.6.0-py2.7.egg.
Is this version number used to decide what egg a user gets from PyPI? I didn't
think it was, but a user is seeming to indicate
