Summary: | dev-python/jinjia-2.7.3 fails tests with pypy3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paolo Pedroni <paolo.pedroni> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mgorny |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 529926 | ||
Bug Blocks: | |||
Attachments: | jinja-2.7.3:20141120-110741.log.gz |
Description
Paolo Pedroni
2014-11-20 11:29:41 UTC
This on the other hand is NOT fixed by rebuilding dev-python/pypy3 without LTO, so I think it warrants some more attention. This is actually the same failure as bug 529926; jinja uses markupsafe.escape internally. Upstream bug: https://github.com/mitsuhiko/jinja2/issues/384 Same (pending) resolution as markupsafe, as Jinja2 includes a verbatim copy of that same CAPI extension memory management test. This is apparently fixed in jinja-2.8 Requested 2.8 stabilization in bug 583264. |