#4850: Having a project named "code" breaks things
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: django-admin.py
Version: | Resolution:
Keywords: project name | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Changes (by mtredinnick):
* stage: Ready for checkin => Design decision needed
Comment:
Simon: it's a never-ending arms-race to try and catch all clashes. At the
end of the day, standard Python rules apply: package names must be unique.
So we have to check every possible importable package name
({{{__builtins___}}} is of no help there). This will be time-consuming and
error-prone as well (it's not future-error-proof once you start installing
third-party packages, for example).
I don't know what the right solution is, beyond asking programmers to
think like Python programmers. Maybe there's something, but it's never
going to be bullet-proof.
--
Ticket URL: <http://code.djangoproject.com/ticket/4850#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
