Opened 2 years ago

Closed 2 years ago

#20490 closed Uncategorized (invalid)

Project-wise versus System-wise

Reported by: lorinkoz@… Owned by: nobody
Component: Uncategorized Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I really think we should make Python-Django packages installable project-wise instead of system-wise, that is, copying them into the project itself instead of Python's site-packages. This is something that NuGet already does for .NET. It basically manages packages the usual way, resolving dependencies and such, but copies the packages into the project folder, which helps portability and modularity a lot. It's a pain having to install all packages on every computer you want your project to run. I truly believe that except for essential core packages, everything on Django should be installed project-wise. Things like South, Forms-bootstrap, Rest-framework, etc. should be on the project folder and ported everywhere with the project.

Change History (1)

comment:1 Changed 2 years ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

You're describing a package manager. That doesn't belong in a web framework such as Django!

I recommend you look at virtualenv, pip and friends.

Note: See TracTickets for help on using tickets.
Back to Top