#5289 closed (wontfix)
[schema-evolution] global name 'set' is not defined
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Uncategorized | Version: | other branch |
Severity: | Keywords: | schema evolution | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | yes | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I'm using schema evolution version of django installed from svn, on a shared hosting account on site5.com. I have allready installed svn version of django with no sql-schema support, and I got it running. Now when I try to add the chema evolution support, and then run sqncdb I get this error:
[03:57:23][ *myhomedir* @ pan:~/django_projects/pulmus]$ ./manage.py syncdb Creating table auth_message Creating table auth_group Creating table auth_user Creating table auth_permission Creating table django_content_type Creating table django_session Creating table django_site Creating table django_admin_log Traceback (most recent call last): File "./manage.py", line 11, in ? execute_manager(settings) File "/home/myhomedir/lib/python2.3/django/core/management.py", line 1886, in execute_manager execute_from_command_line(action_mapping, argv) File "/home/myhomedir/lib/python2.3/django/core/management.py", line 1777, in execute_from_command_line action_mapping[action](int(options.verbosity), options.interactive) File "/home/myhomedir/lib/python2.3/django/core/management.py", line 713, in syncdb schema_fingerprint, introspected_upgrade, evolution = get_sql_evolution_detailed(app) File "/home/myhomedir/lib/python2.3/django/core/management.py", line 617, in get_sql_evolution_detailed output = schema_evolution.get_sql_evolution_check_for_dead_fields(klass, new_table_name) File "/home/myhomedir/lib/python2.3/django/core/schema_evolution.py", line 139, in get_sql_evolution_check_for_dead_fields suspect_fields = set(introspection.get_columns(cursor,db_table)) NameError: global name 'set' is not defined
anything you can do? I'm new to python, and I cannot figure it out mysqlf yet, sorry.
Attachments (1)
Change History (6)
comment:1 by , 17 years ago
Summary: | Schema evolution, an error after installing: → [schema-evolution] global name 'set' is not defined |
---|---|
Triage Stage: | Unreviewed → Accepted |
Version: | SVN → other branch |
by , 17 years ago
Attachment: | se_python23_fix.patch added |
---|
comment:2 by , 17 years ago
Has patch: | set |
---|---|
Needs tests: | set |
Hi guys.
As I said I'm just starting my way on python. I really don't know what the set function does. Yet on a quick look, it seem like my patch solves the problem.
Please test it properly, as I really had a wild guess more then proper debugging work.
comment:3 by , 17 years ago
Just to clarify the status of schema-evolution - it is a branch that was created for a Google Summer of Code 2006 project that was undertaken by Derek Anderson. It is not being maintained or developed by any of the core developers. Based on the most recent discussions about the branch, it is not likely to be accepted for merging in its current form.
This ticket has been kept open in case Derek wants to address it. However, I don't know if he is paying any attention to the ticket tracker, or if he is even actively developing the branch any more.
comment:4 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I'm boldly closing this, for now; as russellm points out, this only applies when using an experimental branch with an old version of Python. If the branch will get merged, this will be handled by QA as part of compatibility testing (the patch is a standard 2.3 compatibility fix).
comment:5 by , 17 years ago
i have pulled this fix into my local schema-evolution branch. it will be commited as soon as i finish my update from HEAD.
A fix for schema evolution