On Saturday 14 July 2007 10:38:35 Mark Ramm wrote: > > Should we make the TurboGears 2 toolbox a separate project itself? We > can ship with it but keep it outside the core.
If it is a separate project, I don't see why we should ship it with the core. We don't ship CherryPy, we don't ship Kid, we don't ship Genshi. Separate project is separate project. The approach I'd use would be to ship Toolbox2 as a separate project and require a range of versions from TG to make it work. setuptools can take care of the integration very well, so this is a non-issue on the integration side. > I'm not sure what to think here, I think the Toolbox is an important > component, an the toolbox itself isn't much work to maintain, because > there's very little code. But, I kind of like the idea that the > core TurboGears2 project is just the code needed for the basic > turbogears api, and all the extras live in separate eggs. What can be done is a set of recommended eggs. Then, include Toolbox2 on this set. > So, I can go either way on this one. What do you all think? I'm all for separating eggs and recommending things. That's how I do in my own projects and this brings me a huge reusability and I don't have to worry all that much: setuptools + entry points is working perfectly to me. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
