tickets: 8280
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8280 | 2008-08-13 07:08:07 | 2015-01-05 16:19:23 | 2022-03-06 03:41:50.160805 | Ready for checkin | closed | Core (Management commands) | Bug | Normal | dev | fixed | Commands framework doesn't support alternate import methods | From this thread on the developer mailing list http://groups.google.com/group/django-developers/browse_thread/thread/78975372cdfb7d1a# I understand that the Django team is keen on supporting alternate ways of packaging django: in a zip-file, in a jar-file(Jython) or other "frozen" formats. One place that'll need fixing to achieve this is to update the command framework. [[BR]] The find available commands, the current Django code is browsing the command subdirectories and looking for files that end with a .py extension[[BR]] To support alternate packaging, the code should use the proper Python APIs to iterate over the available modules in a package. A patch along these lines was already included with #5825. (The patch would need updating to the SVN version however - Once this ticket is accepted I can take care of it.) | nobody | jdetaeye | command zip | 0 | 1 | 0 | 0 | 0 | 0 |