Is it possible you create your virtual environments with global site-packages? >From what I'm seeing this is caused primarily by version mismatches of the six library and using OS site-packages with virtualenv would certainly do it as setuptools and pip both use six.
The difference with 1.10/1.11 I cannot explain though. On Mon, Sep 4, 2017 at 9:03 PM, Derek Zeng <zen1...@gmail.com> wrote: > Hi Melvyn, > > Renaming MIDDELWARE_CLASSES doesn't help either. > > These are the requirements I have: > > django==1.10.5 > djangorestframework > markdown > django-filter > django-jinja > pytest > factory_boy > > fabric3 > pytest-django > > feedparser==5.2.1 > pytz > PyYAML > lxml > requests > > django-extensions > Werkzeug > > django-cors-headers > psycopg2 > django_compressor > django-libsass > livereload > > --- > > I tried to comment out the code you quoted. But that has no effects. > > > On Mon, Sep 4, 2017 at 12:37 PM, Melvyn Sopacua <m.r.sopa...@gmail.com> > wrote: >> >> Rename MIDDLEWARE_CLASSES to >> MIDDLEWARE in settings to see if that changes anything. >> If not, remove one by one (except static). There are some changes to >> the static files middleware [1], but I can't really relate that to >> your error. >> >> Is there anything in your project requirements that also uses six? >> >> There's no diff between 1.10.x and 1.11.x on six.py, but this code >> looks like a possible root cause: >> >> # Here's some real nastiness: Another "instance" of the six module might >> # be floating around. Therefore, we can't use isinstance() to check for >> # the six meta path importer, since the other six instance will have >> # inserted an importer with different class. >> if (type(importer).__name__ == "_SixMetaPathImporter" and >> importer.name == __name__): >> del sys.meta_path[i] >> break >> >> [1] >> https://docs.djangoproject.com/en/1.11/releases/1.11/#django-contrib-staticfiles >> >> On Mon, Sep 4, 2017 at 3:32 PM, Derek Zeng <zen1...@gmail.com> wrote: >> > If I turn off debug mode, it gives me 500 error and showing the same >> > stack >> > trace in the console. >> > >> > I also tried 1.11.4, still the same error. >> > >> > On Mon, Sep 4, 2017 at 2:33 AM, Raffaele Salmaso <raffa...@salmaso.org> >> > wrote: >> >> >> >> On Sun, Sep 3, 2017 at 4:26 PM, Derek Zeng <zen1...@gmail.com> wrote: >> >>> >> >>> When I use django==1.10.7, this does not happen. >> >>> When I use django==1.11a1 this happens. >> >> >> >> Why 1.11a1? Current is 1.11.4 >> >> >> >> -- >> >> | Raffaele Salmaso >> >> | https://salmaso.org >> >> | https://bitbucket.org/rsalmaso >> >> | https://github.com/rsalmaso >> >> >> >> -- >> >> You received this message because you are subscribed to a topic in the >> >> Google Groups "Django users" group. >> >> To unsubscribe from this topic, visit >> >> https://groups.google.com/d/topic/django-users/49blpAjNxYc/unsubscribe. >> >> To unsubscribe from this group and all its topics, send an email to >> >> django-users+unsubscr...@googlegroups.com. >> >> To post to this group, send email to django-users@googlegroups.com. >> >> Visit this group at https://groups.google.com/group/django-users. >> >> To view this discussion on the web visit >> >> >> >> https://groups.google.com/d/msgid/django-users/CABgH4Js1z0e7yypGD4f7z_eKbMrYWQEMT9viCSCshA1ROhMA_A%40mail.gmail.com. >> >> >> >> For more options, visit https://groups.google.com/d/optout. >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Django users" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to django-users+unsubscr...@googlegroups.com. >> > To post to this group, send email to django-users@googlegroups.com. >> > Visit this group at https://groups.google.com/group/django-users. >> > To view this discussion on the web visit >> > >> > https://groups.google.com/d/msgid/django-users/CAAzyz%2BG2MjxRv001kjq%3DpkpzReVAHw03Jv9FW6Ry7sHPwKMsSQ%40mail.gmail.com. >> > >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Melvyn Sopacua >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Django users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/django-users/49blpAjNxYc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> django-users+unsubscr...@googlegroups.com. >> To post to this group, send email to django-users@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/CA%2Bgw1GV3fMt5w4wUjOSviZzkdaHRU%2BFj4fHJqRSJnMGpcdLUNA%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CAAzyz%2BEiQYvTZO41n9QsFiZ_%3DxgH3Hkrsu%2BZ6erX7CO74VKNEw%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Bgw1GXa-x_N-%2BZU9a4gvECL6rVxsPZB1aF64SqGbkHeppUirQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
