On Thu, Feb 25, 2016 at 3:19 AM, anatoly techtonik <
tech...@gmail.com> wrote:
> The problem is distutils, which is frozen in Python stdlib.
> setuptools could support it, but does not, because there is no way to
> specify the format of long_description field - filename is not preserved and
> you can't reference filename with description inside of sdist archive to
> figure out format by extension.
> reST parser may choke on markdown.
Right, but there have been otherwise productive discussions on what
could be done to support this via metadata and via Warehouse (aka PyPI
2.0)
>> As a related note, this made me notice that it appears Markdown formatting
>> is not supported in PyPI package information? I assume the two issues are
>> related. Any advice on how difficult this might be to update?
>
>
> It is difficult, because of bus factor - there are no people trustful enough
> to maintain PyPI and keep everyone else sure that PyPI won't be broken by
> them.
>
https://bitbucket.org/pypa/pypi/issues/148/support-markdown-for-readmes
The reality is that PyPI is presently an old and fragile code-base.
All new features are being asked to target Warehouse (PyPI 2.0) which
may or may not be included in the "Become PyPI" milestone. This has
nothing to do with people being trustworthy, it has to do with
justified caution around modifying something used by an incredibly
large number of people. When a system is that fragile but also that
necessary for other people's work flows you get to the point where you
accept that changing it is more of a risk than replacing it with
something more maintainable that is backwards compatible of sorts.
tl;dr, Ian you may want to look at
https://github.com/pypa/warehouse/issues/869