| Summary: | dev-python/markupsafe-1.0 fails tests with pypy3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Paolo Pedroni <paolo.pedroni> |
| Component: | Current packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | mgorny |
| Priority: | Normal | Keywords: | PullRequest, TESTFAILURE |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/mitsuhiko/markupsafe/issues/39 | ||
| See Also: | https://github.com/gentoo/gentoo/pull/13094 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 529934 | ||
| Attachments: | markupsafe-0.23:20141120-102114.log.gz | ||
|
Description
Paolo Pedroni
2014-11-20 10:32:15 UTC
This bug, on the other hand, is NOT fixed by rebuilding dev-python/pypy3 without LTO, so I think it warrants some more attention. I can reproduce this one. Upstream bug: https://github.com/mitsuhiko/markupsafe/issues/39 for now leaving ebuild as is. Awaiting this to be addressed by upstream My fix has been accepted upstream. Unsure if a release is being prepared. (In reply to Alice Bevan-McGregor from comment #5) > My fix has been accepted upstream. Unsure if a release is being prepared. Using this patch it fails for python2.7. test_markup_leaks (markupsafe.tests.MarkupLeakTestCase) ... FAIL ====================================================================== FAIL: test_markup_leaks (markupsafe.tests.MarkupLeakTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/var/tmp/portage/dev-python/markupsafe-0.23/work/MarkupSafe-0.23-python2_7/markupsafe/tests.py", line 163, in test_markup_leaks assert len(counts) == 1, 'ouch, c extension seems to leak objects' AssertionError: ouch, c extension seems to leak objects ---------------------------------------------------------------------- Ran 16 tests in 0.163s For me it works perfectly with all python versions I have (2.7, 3.4, latest pypy, pypy3). Can we add this patch until upstream releases a new version? Please. (In reply to Paolo Pedroni from comment #7) > For me it works perfectly with all python versions I have (2.7, 3.4, latest > pypy, pypy3). Can we add this patch until upstream releases a new version? This patch doesn't work anymore. Probably it's because I upgraded to dev-python/pypy3-5.2.0_alpha1, but I don't have time to downgrade and try it out. Now it's started failing with python3.5... PR available which adds 1.1.1 (with fixed pypy3 test), and removes 1.0: https://github.com/gentoo/gentoo/pull/13094 Old version removed. Please reopen if you can reproduce it with the current one. |