Since I have less direct personal involvement, I'll say this:
Yes, there are problems. A lot of them are around documentation, and timing
of when things switch over (the whole Python packaging ecosystem has been
in a state of flux/rewrite for a while now; this is unfortunate, but also
necessary).
I just had a dreadful day dealing with PyPI and the migrations that are
happening. I'm posting this rant here in hopes of reaching the people who
can fix it (apologies if I'm in the wrong list), or at least offer an
explanation of the events that happened.
Disclaimers:
- Any and all feedback is
> On Aug 4, 2017, at 4:43 PM, Lucas Boppre Niehues
> wrote:
>
> I just had a dreadful day dealing with PyPI and the migrations that are
> happening. I'm posting this rant here in hopes of reaching the people who can
> fix it (apologies if I'm in the wrong list), or at
On Fri, Aug 4, 2017 at 2:29 PM, James Bennett wrote:
> I'm sorry that you're frustrated. You're not the only person who's
> frustrated, and in fact I'd bet a lot of the people who are trying to get
> this stuff to work seamlessly and perfectly for you are at least as
>
> On Aug 4, 2017, at 8:42 PM, Lucas Boppre Niehues
> wrote:
>
>
> >> I can't even specify the description of a package, not even during
> >> registration or upload.
> > Tell me your package name privately or publicly and I’ll figure out what
> > went wrong.
>
>
Thank you for the kind responses.
I hope I haven't offended anybody, and please know that I'm incredibly
grateful for all the sweat and blood that has been poured into these
projects. I'm complaining about the current situation to show the largest
pain points from my perspective. That's also why
> So it appears that the wheel isn’t being properly generated.
Ah, this helps a lot. I didn't realize it's the first upload that defines
the description for the package.
Testing different configurations I found that the wheel generation chokes
and ignores everything after the first Windows-style
Donald, thanks for the thoughtful and complete reply to the original
poster.
On Fri, Aug 4, 2017 at 3:52 PM Donald Stufft wrote:
> Going through your text, there’s a mixture of things that sort of combined
> here, I’m kind of just going to stream of conscious reply to them
On Fri, Aug 4, 2017 at 2:51 PM, Donald Stufft wrote:
> This API is also considered “legacy” (it just doesn’t have a
> replacement yet). So the legacy in https://upload.pypi.org/legacy/ has to do
> with the API rather than the location/deployment.
>
> I probably should have named
I created an issue on setuptools tracker about Windows newlines (
https://github.com/pypa/setuptools/issues/1126), and another on Warehouse
about the "Invalid file extension" message and PEP 517 (
https://github.com/pypa/warehouse/issues/2281). I'm not creating one for
ignoring duplicated files in
10 matches
Mail list logo