How to handle sys.path in bigger projects?
Martin von Loewis
loewis at informatik.hu-berlin.de
Fri Oct 12 05:52:30 EDT 2001
More information about the Python-list mailing list
Fri Oct 12 05:52:30 EDT 2001
- Previous message (by thread): How to handle sys.path in bigger projects?
- Next message (by thread): How to handle sys.path in bigger projects?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Georg Lohrer <GeorgLohrer at gmx.de> writes: > What are your ways of handling? If you are relying on a lot of third-party packages, I'd require that those packages get properly installed, ie. into site-packages or site-python. Then you only need to find your own code. If that grows in size, organizing it into multiple packages seems to be appropriate. I then see no problem in keeping all these packages in a single directory. Regards, Martin
- Previous message (by thread): How to handle sys.path in bigger projects?
- Next message (by thread): How to handle sys.path in bigger projects?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list