Hi John, Had the same issue on a test server i was setting up on raspbian (virtualenv with python3). With me it got busted whe i wanted to run python manage.py createdb. Thanks to kenbolton on #mezzanine, I was able to get the thing working.
Seems there is a problem with the Bleach 2.0 build dependency. Heres the entire procedure: 1. pip uninstall bleach 2. change metadata.json and METADATA inside Mezzanine-4.2.2.dist-info: bleach(>=1,4*, <2.0*) // Note: I dont think this had any impact in the end because i tried running pip install bleach with this and still got 2.0.0 dist; just left it here for clarification 3. pip install Bleach==1.5 >From then on I could create a db with no errors :] Hope it works for you too! Jošt On Thursday, 9 March 2017 05:30:23 UTC+1, John Barham wrote: > > Hi all, > > I just installed current version of Mezzanine 4.2.2 but when I run "python > manage.py shell" after creating a project I get the following error: > > File > "/home/jbarham/.virtualenvs/foo/lib/python3.5/site-packages/mezzanine/utils/html.py", > > line 36, in <module> > if "tel" not in sanitizer.BleachSanitizer.allowed_protocols: > AttributeError: module 'bleach.sanitizer' has no attribute > 'BleachSanitizer' > > The installed version of Bleach is 2.0 which was released literally 14 > hours ago (https://github.com/mozilla/bleach/releases). If I manually > revert to the previous release 1.5, the error goes away, so it's evidently > due a backwards-incompatible change in the bleach API. > > ISTM this is a fairly serious issue since it will break any new installs > of Mezzanine. A quick workaround may be to change the Mezzanine setup.py > requirement for bleach from "bleach >= 1.4" to "bleach >= 1.4, < 2.0". > > Thoughts? > > Cheers, John > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
