Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Django 3 dropped support to django.utils.six

See original GitHub issue

I just try to upgrade my server to Django 3.0 release today for tests and as we can read the module django.utils.six will be dropped with the version 3 of Django.

Here you can find my Traceback:

  File "/home/user/.virtualenvs/dns/lib/python3.7/site-packages/pipeline/finders.py", line 9, in <module>
    from pipeline.conf import settings
  File "/home/user/.virtualenvs/dns/lib/python3.7/site-packages/pipeline/conf.py", line 15, in <module>
    from django.utils.six import string_types
ModuleNotFoundError: No module named 'django.utils.six'

Please evaluate the migration to six as suggested in the #removed-private-python-2-compatibility-apis section of the release note.

Thanks for this amazing library!

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

TheBukycommented, Dec 30, 2019

@eire1130 The Travis job to automatically publish package and PyPI.org is broken (authentication error). I open an issue to Jazzband for checking the credentials, and fix it.

Meanwhile you can, you can git clone the project, go in the django-pipeline repertory and do python3 setup.py sdist bdist_wheel. That will create new folder dist and you can install the package with pip install -U dist/django-pipeline-1.7.0.tar.gz (or something like that). Like explained there

0reactions

eire1130commented, Dec 30, 2019

@TheBuky thanks. I just need it to live in my requirements.txt for deploys. For now I have it pinned source, which works of course, but I prefer to use package / pypi names rather then pointing to github.

Again, thank you for being on top of this, I really appreciate it!

Top Results From Across the Web

ImportError: cannot import name 'six' from 'django.utils'

Django stopped supporting Python 2. Since django.utils.six provided "Utilities for writing code that runs on Python 2 and 3", it was not longer ......

Patching a missing django.utils.six | by Diederik van der Boor

With the start of Django 3.0, all Python 2 compatibility code was removed. This also meant that the module django.utils.six is gone.

Django 3.0 release notes

Following the release of Django 3.0, we suggest that third-party app authors drop support for all versions of Django prior to 2.2.

ImportError: cannot import name 'six' from 'django.utils'

The ImportError: cannot import name 'six' from 'django.utils' occurs because `django.utils.six` has been removed starting Django version 3.

Changelog — django-configurations 2.3.1 documentation

v2.3 (2021-10-27)¶. BACKWARD INCOMPATIBLE Drop support for Python 2.7 and 3.5. ... Replace django.utils.six with six to support Django >= 3.