#800: SQLalchemy selection in 0.9a5 does not generate requires
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: anonymous
Type: enhancement | Status: new
Priority: lowest | Milestone:
Component: TurboGears | Version: 0.9a5
Severity: trivial | Resolution:
Keywords: |
--------------------------------+-------------------------------------------
Comment (by godoy):
The problem is that then everybody's installation will have two ORMs: SQL
Object and SQL Alchemy.
Today, SQL Object is the official -- hence required -- ORM. SQL Alchemy
is supported and will, probably, be the official ORM one day. On that
day, then, SQL Object *won't* be required and SQL Alchemy will.
Who chooses SQL Alchemy is going to have to handle more stuff manually
than who chooses SQL Object.
On the other hand, I'm not sure but it might work if the "requires.txt"
file had the chosen ORM in it, just for consistency. It will probably
make it impossible to run the project unless SQL <something> is installed.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/800>
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.
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/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---
