I didn't think of this problem. I personally really like having the version number in my release egg, and setuptools does this automatically, by looking at the .svn folder and retrieving it. How is this going to work with Hg? Tracking down errors with people's widgets is going to get hairy unless we have some way of keeping track of the version numbers.
About a setup folder: Gosh, I really hate when packages do that. Haven't we all realized that our developers need to get with the program and have easy_install working first? For this reason none of my packages will contain a setup/ and if a paster script creates one, I will promptly remove it. Maybe I am missing the problem that it solves. -chris On Apr 2, 9:43 am, Christopher Arndt <[EMAIL PROTECTED]> wrote: > percious schrieb: > > > 2) set up the Hg repo, and provide good documentation about how to use > > the repository. > > Have you tested whether all the setuptools machinery works properly with > mercurial? AFAIK, the "include_package_data" setup() option only works > with CVS & SVN by default. Don't know if any TW widget uses this, but > this should be checked. Also, what about including "ez_setup.py" as a > repo external? > > Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
