On Aug 4, 2017, at 8:42 PM, Lucas Boppre Niehues <lucasboppre@gmail.com> 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.

https://pypi.python.org/pypi/mouse/0.6.0
https://test.pypi.org/project/mouse/0.6.0

The long description was originally Markdown, and converted to RST by pandoc. I would 100% understand if this conversion triggered some bug. My gripe was that one by one my debugging tools failed in confusing ways.

So you uploaded the wheel first, which means that’s where PyPI would have gotten the long_description from. When I download that wheel and open it up and look at mouse-0.6.0.dist-info/METADATA I see a file that looks like:

---

Metadata-Version: 2.0

Name: mouse

Version: 0.6.0

Summary: Hook and simulate global mouse events in pure Python

Home-page: https://github.com/boppreh/mouse

Author: BoppreH

Author-email: boppreh@gmail.com

License: MIT

mouse

---

So it appears that the wheel isn’t being properly generated. I would expect the full contents of your long description to show up, and not just the word “mouse’. I didn’t dig into it further to see if this is setuptools, wheel, or your pandoc version at fault, but my guess is it’s one of those. Given lots of people are successfully uploading, my first guess would be something in the pandoc build pipeline you have— but it could also be an edge case triggering a latent bug in setuptools or wheel.

>> I cannot even report the issues. [ ... ] because there's no clear location to report them.
> This is a problem, and we don’t really have a good solution for them. I think generally what happens is people just open them on whichever tool they think is the best fit, and the authors of these tools all know each other, and if it ends
> up getting filed in the incorrect place, we just redirect people tot he correct place.

Just my 2 cents, but I often not post a bug report at all for fear of wasting the wrong person's time. I'll keep this case in mind, but you may be missing some important reports with this configuration. The "packaging-problems" repo was almost perfect, but I avoided it due to the feeling of being abandoned or exclusive for PyPI developers. An explicit "It's ok to post X, Y and Z bugs here if you are unsure" would have changed my mind.

I’ll see what I can do here. It might just make sense for these related set of tools to just ditch the Github issue trackers and share an issue tracker that can divide things up by project somehow, but where we can readily move issues between them. Maybe we just need something (or someones) able to triage incoming issues on a meta tracker and redirect people. Not sure, I’ll give it some thought.