parse_lookup deleted

[GoogleCodeExporter]

django-tagging depends on django.db.models.query import parse_lookup, but
that particular function has been removed from Django.  This prevents the
user from using syncdb.

Original issue reported on code.google.com by rcoy...@gmail.com on 2 Aug 2008 at 3:59

[GoogleCodeExporter]

I tried to use django-tagging with the 1.0 alpha release of Django today, and
received the same error:

Traceback (most recent call last):
  File "runtests.py", line 6, in <module>
    failures = run_tests(None, verbosity=9)
  File
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/d
jango/test/simple.py",
line 135, in run_tests
    for app in get_apps():
  File
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/d
jango/db/models/loading.py",
line 97, in get_apps
    self._populate()
  File
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/d
jango/db/models/loading.py",
line 57, in _populate
    self.load_app(app_name, True)
  File
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/d
jango/db/models/loading.py",
line 72, in load_app
    mod = __import__(app_name, {}, {}, ['models'])
  File "/users/153654/Django/django_projects/tagging/models.py", line 9, in <module>
    from tagging.managers import TagManager, TaggedItemManager
  File "/users/153654/Django/django_projects/tagging/managers.py", line 6, in <module>
    from django.db.models.query import QuerySet, parse_lookup
ImportError: cannot import name parse_lookup

Original comment by patrickb...@gmail.com on 4 Aug 2008 at 10:10

[GoogleCodeExporter]

this was fixed at some earlier point.
closing.

Original comment by doug.nap...@gmail.com on 12 Aug 2008 at 4:48

• Changed state: Fixed

[GoogleCodeExporter]

I thought this issue was fixed? I just upgrade my Django install to 1.0. Then I 
started received the error mentioned above. I thought that I might have to 
upgrade 
my django-taggings package, so I did - but I'm still receiving this error.

Is there a patch or something?

Original comment by michaels...@comcast.net on 8 Oct 2008 at 6:34

[GoogleCodeExporter]

Definitely not fixed.  The 0.2.1 windows installer gives a version that can be
imported into the command line python.  But does not seem to work with django.  
The
svn checkout cannot even be imported into python.

Original comment by joet...@gmail.com on 13 Oct 2008 at 12:05

[GoogleCodeExporter]

The issue is not fiexed.
Still got error during syncdb.

Original comment by StephanF...@gmail.com on 26 Mar 2009 at 7:02

[GoogleCodeExporter]

up

Original comment by j60017...@gmail.com on 20 Apr 2009 at 1:51

[GoogleCodeExporter]

Same problem.

Original comment by jad...@gmail.com on 13 May 2009 at 6:59

[GoogleCodeExporter]

Solution: don't use the published packaged distribution (which contains the 
error),
use the svn trunk which is fixed.

Original comment by jad...@gmail.com on 13 May 2009 at 7:13

[GoogleCodeExporter]

same

Original comment by mattoma...@gmail.com on 30 Nov 2011 at 3:07

[GoogleCodeExporter]

5 years and this is still an issue? Why is it marked fixed?

Original comment by jon.mo...@gmail.com on 6 Mar 2013 at 6:32

[GoogleCodeExporter]

/usr/local/bin/django-admin.py runserver --pythonpath /opt/graphite/webapp 
--settings graphite.settings 0.0.0.0:8080
Validating models...

Unhandled exception in thread started by <bound method Command.inner_run of 
<django.core.management.commands.runserver.Command object at 0x7fd430f85310>>
Traceback (most recent call last):
  File "/usr/local/lib/python2.6/dist-packages/django/core/management/commands/runserver.py", line 92, in inner_run
    self.validate(display_num_errors=True)
  File "/usr/local/lib/python2.6/dist-packages/django/core/management/base.py", line 280, in validate
    num_errors = get_validation_errors(s, app)
  File "/usr/local/lib/python2.6/dist-packages/django/core/management/validation.py", line 35, in get_validation_errors
    for (app_name, error) in get_app_errors().items():
  File "/usr/local/lib/python2.6/dist-packages/django/db/models/loading.py", line 166, in get_app_errors
    self._populate()
  File "/usr/local/lib/python2.6/dist-packages/django/db/models/loading.py", line 75, in _populate
    self.load_app(app_name)
  File "/usr/local/lib/python2.6/dist-packages/django/db/models/loading.py", line 96, in load_app
    models = import_module('.models', app_name)
  File "/usr/local/lib/python2.6/dist-packages/django/utils/importlib.py", line 35, in import_module
    __import__(name)
  File "/opt/graphite/webapp/graphite/events/models.py", line 6, in <module>
    from tagging.managers import ModelTaggedItemManager
  File "/usr/local/lib/python2.6/dist-packages/tagging/managers.py", line 6, in <module>
    from django.db.models.query import QuerySet, parse_lookup
ImportError: cannot import name parse_lookup
# django-admin.py --version
1.5

Original comment by jon.mo...@gmail.com on 6 Mar 2013 at 6:33

[GoogleCodeExporter]

Guys, I think you just all need to install the “django-tagging” package 
instead of the deprecated “tagging” package.

Original comment by kalessin...@gmail.com on 5 Jun 2013 at 1:58

[GoogleCodeExporter]

Nice, Thanks kalessin. django-tagging does the job.

Original comment by al...@pagewoo.com on 12 Feb 2014 at 5:38

[GoogleCodeExporter]

 1008  yum erase python-django-tagging
 1009  yum install django-tagging
 1010  yum install graphite-web

In my case graphite-web was deinstalled but it did the job.

Original comment by martijn....@gmail.com on 4 Sep 2014 at 3:36

[GoogleCodeExporter]

Still an issues in 2015

Original comment by guillaum...@econsultancy.com on 12 Jun 2015 at 2:51