Repository navigation
Conversation
|
Yes. This would be a good thing. Pyramid uses Markupsafe and errors when I try to install it: Running MarkupSafe-0.18/setup.py -q bdist_egg --dist-dir /tmp/easy_install-9q77mm/MarkupSafe-0.18/egg-dist-tmp-pm_q77 File "build/bdist.linux-x86_64/egg/markupsafe/tests.py", line 51 File "/home/XXXX/..../env/lib/python3.2/site-packages/MarkupSafe-0.18-py3.2-linux-x86_64.egg/markupsafe/init.py", line 68 File "/home/XXXX/....env/lib/python3.2/site-packages/MarkupSafe-0.18-py3.2-linux-x86_64.egg/markupsafe/tests.py", line 51 Adding MarkupSafe 0.18 to easy-install.pth file |
|
+1 |
|
Mako also pulls MarkupSafe. Please apply. |
|
I've released mako 0.8.1 that just skips markupsafe in setup.py for the various versions. by the time we finish arguing with armin everyone will be on 3.3. |
|
Thanks, @zzzeek! |
|
+1 |
|
I don't understand. Project restore Python 3 compatibility, or no? |
|
@gordio: As far as I know, @mitsuhiko hasn't merged my fixes, which means that markupsafe is only compatible with Python 3.3 (not 3.2). |
|
I currently have no plans to restore 3.2 support. None of my other libraries support 3.2 any more and for many of those the changes in 3.3 are necessary to make the codebase sane. You can already depend on an older version if you want to use 3.2 anyways so I don't see a huge reason to do this change. |
No description provided.