On Dec 26, 4:24 pm, Stefan Krah wrote:
> It is quite reasonable that changed archives with the same version number
> are not accepted. Very helpful, not condescending.
The message helps you remember to bump your version number. Try:
"Please either increment your version number, or use your Pack
Phlip schrieb:
I have no alternative, to fix bugs in PyPi, _not_ in "that file", but
to continue burning up version numbers that nobody cares about. The
message is condescending because I am aware of the reason we version
packages, and the message is _not_ helping me apply that reason!
Aaand I
Phlip wrote:
> On Dec 26, 6:01 am, "Martin v. Loewis" wrote:
>
> > > Now my next problem - how to get pypi.python.org to stop burning up
> > > version numbers each time I test this?
> >
> > I don't speak English well enough to understand what "to burn up"
> > means - to my knowledge, PyPI does n
> I have no alternative, to fix bugs in PyPi, _not_ in "that file", but
> to continue burning up version numbers that nobody cares about. The
> message is condescending because I am aware of the reason we version
> packages, and the message is _not_ helping me apply that reason!
Aaand I just found
On Dec 26, 6:01 am, "Martin v. Loewis" wrote:
> > Now my next problem - how to get pypi.python.org to stop burning up
> > version numbers each time I test this?
>
> I don't speak English well enough to understand what "to burn up"
> means - to my knowledge, PyPI does no such thing.
I don't know
Phlip wrote:
>> What you want is a source distribution (sdist).
>
> Thanks. Yes, this is prob'ly documented somewhere.
>
> Now my next problem - how to get pypi.python.org to stop burning up
> version numbers each time I test this?
I don't speak English well enough to understand what "to burn up
On Dec 24, 3:32 am, "Martin v. Loewis" wrote:
> > Any tips?
>
> A binary distribution won't have a setup.py, because
> you can install it by other means (such as Windows Installer),
> instead of running setup.py
>
> What you want is a source distribution (sdist).
Thanks. Yes, this is prob'ly docu
> Any tips?
A binary distribution won't have a setup.py, because
you can install it by other means (such as Windows Installer),
instead of running setup.py
What you want is a source distribution (sdist).
Even if you want to create a binary distribution, don't use the
bdist command, but some spec
And the next question in the series - how to make sure the resulting
package has a setup.py file?
The basic steps are...
- build a python package
- create a minimal setup.py
- (github it, natch)
- throw it at pypi with:
python setup.py bdist upload
- attempt to install it with:
sud
And the next question in the series - how to make sure the resulting package has
a setup.py file?
The basic steps are...
- build a python package
- create a minimal setup.py
- (github it, natch)
- throw it at pypi with:
python setup.py bdist upload
- attempt to install it with:
s
10 matches
Mail list logo
