anatoly techtonik <techto...@gmail.com> added the comment: On Tue, Oct 6, 2009 at 4:04 PM, Marc-Andre Lemburg <rep...@bugs.python.org> wrote: >> >> Please, be specific. PyPi maintainer or trac-plugin package maintainer >> or debian package maintainer? Which should be mentioned in debian >> package for a trac plugin uploaded to PyPi for easy_install? > > The maintainer of the plugin. >
So, the maintainer of the plugin is mentioned in setup.py, but this field is also used in PyPi and the person who maintains it there wants some attribution. Should this person change maintainer field to himself? >> Is distutils format extensible? Can you create example of extending >> distutils format using this maintainer use case, so that every project >> can add their own maintainer fields if they need them? If it is >> impossible then I suggest to stop this discussion and start planning >> extensible distutils2 format with setup2.py and other2 files. > > The meta-data format is versioned, so it's well possible to > add new fields to it or make changes in core distutils. No, that's not the way. Suppose we have three independent external frameworks that use setup.py files for deploying their plugins/components. All three need to extend distutils format. Which version should they choose? What if official distutils release will decide to use this version? Will other tools parse all these new versions correctly? > It's even possible to extend if in custom setup scripts, > provided you know your way around in distutils. Have a > look at dist.py. You'll need to write a Distribution sub-class > and register this via the distclass setup() parameter. As you may see I definitely do not know my way in distutils. =) Can you show the example of extending setup.py with pypi_maintainers field, that includes emails that should be granted maintainer rights by PyPi automatically on setup.py submission? It is not that I am challenging you to something - I just want to say that there are not many people who knows distutils like you to create the best solution for this user story. Even if it can be a tedious task the outcome is really important for further distutils usability improvement. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6992> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
