On Mon, Mar 31, 2008 at 7:27 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> 1. What directory structure must Leo have to make leo a package? The current structure should be ok, but it may make sense to rename 'src' to 'core' (as talked before). > 2. My guess is that setup.py should be at the top-most directory, but > if that is so, how does it manage to refer to files in inner folders? What do you mean? You should use the 'packages' statement. > 3. At present, the createLeoDistribution.py script, which may (or not) > form the basis for setup.py, uses the manifest.in file to include/ > exclude files. Is this a good idea? No, it's a bad idea. I don't think it's all too well supported in distutils; only for making source distributions, not installation. > 4. At present, running 'python setup.py install' just creates an .egg > file in in Python25/Lib/site-packages. What in blazes is going on? .egg can be a .zip file that contains stuff that will be zipimported. The biggest problem I can see are the data files (icons etc). We have a brutal hack in setup.py for IPython to handle the files in UserConfig, but I think it might make sense to require setuptools and use that. setuptools provides more advanced ways to discover data files etc., and could generally be an easier route. At least the setuptools documentation makes sense, which can't be said for distutils, and there is may too much "can't go there from here" in distutils. -- Ville M. Vainio - vivainio.googlepages.com blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio' --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
