On 6 January 2017 at 07:37, Nick Timkovich wrote:
> No. My build command was: `python setup.py sdist bdist_wheel` which doesn't
> generate a zip.
We've seen behaviour like this before with the old upload server
implementation, where it was possible to get a particular
No. My build command was: `python setup.py sdist bdist_wheel` which doesn't
generate a zip.
On Thu, Jan 5, 2017 at 2:13 PM, Ethan Furman wrote:
> On 01/05/2017 11:37 AM, Nick Timkovich wrote:
>
> I never determined what was causing my problem, I couldn't reproduce it
>> on
On 01/05/2017 11:37 AM, Nick Timkovich wrote:
I never determined what was causing my problem, I couldn't reproduce it
on testpypi so I gave up (it's a small package, and if someone wants the
source, they can look at the GH link I have in the metadata).
Do you have both a .zip and a .tar
I never determined what was causing my problem, I couldn't reproduce it on
testpypi so I gave up (it's a small package, and if someone wants the
source, they can look at the GH link I have in the metadata).
Specifically, why does it say that the file exists, but I *can not see it
anywhere*,
On 01/05/2017 09:58 AM, Donald Stufft wrote:
.tar.gz is the recommended format ...
.tar.gz it is! Thanks!
--
~Ethan~
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
> On Jan 5, 2017, at 12:55 PM, Ethan Furman wrote:
>
> On 01/05/2017 08:46 AM, Donald Stufft wrote:
>>> On Jan 5, 2017, at 11:45 AM, Ethan Furman wrote:
>
>>> Do I need to choose between zip and tar sdists?
>>
>> Yes.
>
> I haven't followed Windows O/Ses for a while now
On 01/05/2017 08:46 AM, Donald Stufft wrote:
On Jan 5, 2017, at 11:45 AM, Ethan Furman wrote:
Do I need to choose between zip and tar sdists?
Yes.
I haven't followed Windows O/Ses for a while now -- are they able to easily
access tar files? Or do *nix machines come standard with unzip
> On Jan 5, 2017, at 11:45 AM, Ethan Furman wrote:
>
> Do I need to choose between zip and tar sdists?
Yes.
—
Donald Stufft
___
Distutils-SIG maillist - Distutils-SIG@python.org
On 12/22/2016 12:41 PM, Donald Stufft wrote:
There is a fairly new restriction that you can only have *one* sdist per
release now. That should not apply at all to Wheels and if it is, then it
is a bug. I can’t reproduce this issue though, so I’m going to guess
there was some bit of confusion
Nick Timkovich writes:
> Generally, is it OK (recommended/socially acceptable) to upload
> universal wheels only or is the sdist still nice to have available? I
> guess maybe for pip, but it considering universal, pure-Python wheels
> as "binaries" seems quirky.
None
There is a fairly new restriction that you can only have *one* sdist per
release now. That should not apply at all to Wheels and if it is, then it is a
bug. I can’t reproduce this issue though, so I’m going to guess there was some
bit of confusion about exact errors here. If someone actually
> On Dec 22, 2016, at 8:54 AM, Ian Cordasco wrote:
>
> On Thu, Dec 22, 2016 at 9:49 AM, Brett Cannon wrote:
>> Because you already uploaded a wheel for version 0.1.2 you can't upload any
>> other files for that version, else people could
On Thu, Dec 22, 2016 at 9:49 AM, Brett Cannon wrote:
> Because you already uploaded a wheel for version 0.1.2 you can't upload any
> other files for that version, else people could accidentally upload e.g. an
> sdist with code different from what was already uploaded in the
So upload the sdist first in the future? What's the difference between
uploading an sdist second with code that differs from what's in the wheel
and vice versa, is PyPI doing some checking?
Generally, is it OK (recommended/socially acceptable) to upload universal
wheels only or is the sdist still
Because you already uploaded a wheel for version 0.1.2 you can't upload any
other files for that version, else people could accidentally upload e.g. an
sdist with code different from what was already uploaded in the wheel. If
you want an sdist then I would do another release as version 0.1.2post1
I have a little package "huffman" where I build an sdist and wheel (python
setup.py sdist bdist_wheel) and both seem to get built and can install
fine. I can't seem to upload both to PyPI because the "File already exists":
$ twine upload dist/*
Uploading distributions to
16 matches
Mail list logo