Jim Fulton schreef op 28-12-14 om 16:33:
So what is the recommended route for debugging the problem? I would really
>like to fix it but without know the problem I would just to make random
>guesses.
I run:
setup.py --long-description
and pipe the output into a ReST processor to check for errors.
Blowing my own horn here... :-)
If you install zest.releaser (which many people use to release their
packages to save them lots of manual work), as an added bonus you get
the "longtest" script. This does exactly what Jim suggests: it takes the
long description, sends it through docutils and even opens it for you in
your browser. Easiest way to check for errors :-)
See http://zestreleaser.readthedocs.org/
Reinout
--
Reinout van Rees http://reinout.vanrees.org/
rein...@vanrees.org http://www.nelen-schuurmans.nl/
"Learning history by destroying artifacts is a time-honored atrocity"
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
