Ticket #494 (closed task: fixed)
[WG] Can we make the python packages eggable?
| Reported by: | lawrence | Owned by: | spascoe |
|---|---|---|---|
| Priority: | critical | Milestone: | External Product Definition |
| Component: | community | Version: | |
| Keywords: | python | Cc: |
Description (last modified by spascoe) (diff)
Even if we don't want the bundles to be eggable, and packages may have dependencies, can we at least deal with interpackage dependencies in an eggaciouis manner. If not, how can we simplify the pick n mix installation and/ the within bundle installations?
... see Packages.
Stephen: PythonEggs and PythonSetupTools? have many attractive features that NDG could use, however we shouldn't believe eggs will solve all installation issues. For instance any egg that contains a C extension module will be platform and library version (glibc) specific, therefore well designed setup scripts will still be required for each NDG component. There are also ramifications for scripts (cgi and webservices) and resource files that will require refactoring some of our code.
These issues will be further explored in the wiki pages PythonEggs and PythonSetupTools?.
This ticket has a strong overlap with #496 since the solution will probably involve eggs. I am therefore going to merge it under this ticket.
