#10669 closed (invalid)
The import of third-party libraries in the project
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | third-party libraries | |
| Cc: | import, of, third-party, libraries, in, the, project | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Third-party libraries are generally installed in the python site-packages directory to facilitate the direct import, but sometimes do not have permission to import, sometimes, different projects require different versions of third-party libraries; want to add in the project directory a library directory (such as lib), when the server at run-time, automatic import of third-party libraries inside.
Between the different projects so do not affect each other. Especially in the use of virtual hosts, or the same service running on a number of projects, which use a third-party libraries, very important, convenient and flexible.
Note:
See TracTickets
for help on using tickets.
I don't see a bug report here. If this is a question please take it to the django-users mailing list.