How To Package Your Python Code

Re:How To Package Your Python Code by gvalkov on Sunday November 18, 2012 @05:48PM (#4801972)

It actually comes in handy if you're using Sphinx and don't want to maintain release and version in conf.py separately from the version in setup.py. There's no reasons why the data should be consumable only by setuptools .

[ Parent | on HN ]

Re:How To Package Your Python Code by Flimm on Sunday November 18, 2012 @06:28PM (#4802093)

You can use pkg_resources which comes with setuptools to look up the version number of your package in setup.py:

  import pkg_resources
  pkg_resources.get_distribution("PIL").version

[ Parent | on HN ]

Re:How To Package Your Python Code by borntyping on Sunday November 18, 2012 @05:51PM (#4801981)

I put the version information inside the package, then anything with access to the package (which both setup.py and sphinx have) can access it - quite useful for doing things like checking the version number from the REPL, for instance.

[ Parent | on HN ]

Re:How To Package Your Python Code by rhettg on Sunday November 18, 2012 @08:33PM (#4802429)

It can be problematic to import your package from setup.py if you want your dependency specification to be useful.

[ Parent | on HN ]