> Also -- I know that the various tools involved are maintained by different
> people, but it sure would be nice if, for instance, the latest versions of
> setuptools and twine would not try to upload non longer supported file types!
The tools should have better reporting on the errors pypi give
On Fri, Aug 4, 2017 at 5:42 PM, Lucas Boppre Niehues
wrote:
>
> The long description was originally Markdown, and converted to RST by
> pandoc. I would 100% understand if this conversion triggered some bug.
>
It's a good idea to run docutils on it yourself -- but in any case, broken
RST has alwa
one point:
I probably should have named it something other than /legacy/,
>
yes, it should have -- names matter! and having a "legacy" in teh name when
there is not "modern" or "current", or, indeed, anything else is very
confusing.
pypi.org, might as well get it all done at once. It might be
On Wed, Aug 2, 2017, at 01:05 PM, Nick Coghlan wrote:
> I wouldn't say that, as the two most clearly side effect free ways of
> putting the source directory on sys.path are:
>
> 1. make it the current working directory for a "python -m" or "python
> -c" invocation, so that the current directory ge
On 5 August 2017 at 03:12, Donald Stufft wrote:
> 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
