> I do this with my stuff, but instead of keeping a common setup.py I have an
> elaborate and clumsy system that rolls a package or module distro on the
> fly, writing a setup.py file in the process.
>
> So each package/module I publish has a dict names "DISTINFO" in the top
> level file, looking like this:
>
> DISTINFO = {
> 'keywords': ["python2", "python3"],
> 'classifiers': [
> "Programming Language :: Python",
> "Programming Language :: Python :: 2",
> "Programming Language :: Python :: 3",
> ],
> 'install_requires': [
> 'cs.app.flag',
> 'cs.env',
> 'cs.logutils',
> 'cs.pfx',
> 'cs.psutils',
> ],
> 'entry_points': {
> 'console_scripts': [
> 'svcd = cs.app.svcd:main'
> ],
> },
> }
I think I will head this direction. And with `setup.cfg
<https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files>`_,
it is quite easy to keep the package's metadata in a standard way and
feed this to setup().
Regards,
Jimmy
--
https://mail.python.org/mailman/listinfo/python-list
