Christopher Lenz wrote: > Am 11.02.2007 um 11:26 schrieb Christian Boos: > >> As long as the setuptools changes are easy to merge in other branches >> (i.e. they don't involve any moving of files around), I'm OK for the >> setuptools related enhancements to go in trunk. >> > > So that's a "no", as you *know* that integrating the setuptools stuff > will require moving files around. >
I was then referring to setuptools improvements like #3229, using setuptools in setup.py, the namespace support, etc. I'm not sure if the moving is required for all of these, I think it will be only needed for the data packaging. > What "other branches" are we talking about anyway? I've lost track, > you seem to have merged half of the security branch already, and your > other branches are already in too AFAICT, or am I missing something > that would be horribly affected by the setuptools integration? > Well, I did that merge just _after_ sending the mail you've responded to ;-) Now there are only 7 files in templates/, with not many changes in. So feel free to do the required changes for the setuptools support. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
