Georg Brandl, el 27 de mayo a las 22:03 me escribiste: > >> I'd suggest putting it into the new contrib repository. You can have > >> access; you just need to sign up at bitbucket and give me your user > >> name. > > > > Sounds fair. But I must warn you that I don't know anything about egs, > > PYPI and easy_install, so I might need help with that. > > No problem. > > > I completed the templates generated by make-ext.py where I thought it made > > sense. Are you going to generate the extensions documentation in some way? > > If so, will be the README used or should I put the documentation in the > > module itself? > > To be honest I haven't much thought about documentation.
How ironic, being a documentation tool ;) > If it's short, a custom README in your subfolder would be fine. If it's > longer, perhaps a Sphinx doc root could be used for all extensions. I've put the documentation in a README file. > > Well, here are the results of my first try. Review is greatly appreciated > > =) > > > > BTW, my bitbucket user is 'luca'. > > You should now be able to commit your change yourself. Thanks. Have you, or anyone else, took a look at the code, or at least at the setup.py and other "support" stuff, which I don't know very well? I'd like to get some reviewing before doing the actual commit =) -- Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/ ---------------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
