#2081: Model Package import issues
--------------------------+-------------------------------------------------
Reporter: jorge.vargas | Owner: anonymous
Type: task | Status: new
Priority: high | Milestone: 2.0
Component: SQLAlchemy | Version: trunk
Severity: normal | Keywords:
--------------------------+-------------------------------------------------
Given the way SQLAlchemy is initialized it currently create a potential
name collision between the user defined modules (model/*.py) and ANY top
level module in the python installation.
I'm not saying this is a bug because it's documented but it is something
we should take care of. The chances of a name collision are too high and
the results too obscure specially to new developers just starting out.
For example Jon, creates project myfirstapp, then goes into model copies
over model.templates and names it well myfirstapp, when he runs setup-app
everything goes to hell because model.__init__.py is loading from
myfrstapp import * which basically throws things off.
The worst part of this is that any top level package is affect so if you
name your model file tg.py or even something on the stdlib things will go
wrong.
I'm setting this as a task because we should investigate how other big
project handle this issue.
--
Ticket URL: <http://trac.turbogears.org/ticket/2081>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
