| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
I don't know how it actually passes, though, since test_engine.py
includes a bunch of other regexes to normalize, and if I take those
out then running the unittest doctest fails.
|
|
|
|
|
|
| |
Fixes #8
Run doctests with Sphinx on all versions as well.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #9
Two potentially important changes:
- Removed unused code in the tests/ package. If other packages were
using it, they will need updates. (They shouldn't be, but that's
happened before.)
- Changed TraversableModuleImporter to catch ImportError instead of
KeyError. There's no way the underlying SimpleModuleImporter can
raise a KeyError anymore. I think this is the desired semantic but I
am not 100% sure.
|
| |
|
|
|
|
| |
'type'. This turns out to be a bug in the zope.security.proxy.removeSecurityProxy function under pure-Python, so the build won't be green until zopefoundation/zope.security#11 or something like it is released.
|
|
|
|
|
|
|
|
|
|
|
| |
PyPy doesn't support assigning to __builtins__, even in eval(), so
this means that zope.untrusted.builtins is not helpful, even though it
can be installed. Therefore, HAVE_UNTRUSTED must always be False under
PyPy, just like under Python 3.
Minor doctest renormalization to deal with the changed class name of the proxy.
A pure-Python proxy can't lie about its type, so use __class__ in one doctest.
|
|
|
|
|
|
|
|
|
|
|
| |
This change is based on
https://code.launchpad.net/~wallyworld/zope.pagetemplate/fix-isinstance/+merge/38499
by Ian Booth.
The original approach in that branch broke tests, because they rely on
subclassing dict with an implementer of ITraversable. Rather than changing
this, it seems safer to only extend the dict special-case to non-proxied
subclasses.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I can tell these are unused by doing
strace -e open -f -o /tmp/wtf.zpt bin/test
and then grepping for 'testpackage' in /tmp/wtf.zpt.
I wanted to remove these because pyflakes complains about an undefined
ViewPageTemplateFile in there.
|
|
|
|
| |
Fixes https://github.com/zopefoundation/zope.pagetemplate/issues/2
|
| |
|
|
|
|
|
| |
I assume it is unused because otherwise this would've been fixed long
ago, right?
|
| |
|
|
|
|
|
|
| |
There are ZCML files out there (zope.app.pagetemplate) that want to
define permissions for ZopePythonExpr and PythonExpr, and get conflicts
if these are two names referring to the same class.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
When using Chameleon/z3c.ptcompat there are minor differences that are irrelevant.
|
|
|
|
|
| |
in case of an old template that does not accept this argument.
Refs LP#732972
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See https://bugs.launchpad.net/zope.pagetemplate/+bug/732972
This implements the short workaround version of the solution mentioned in the
bug: let's skip macro expansion checking while we're formatting an error
traceback (with the default recursion limit of 100 this still burns a lot of
CPU: ~20 seconds on a 2.5 GHz Core i5).
The test can be easily extended for the better suggested solution (some time in
the future): just drop check_macro_expansion=False and make sure METAL silently
stops recursing iff it notices a loop and TAL evaluation is disabled.
|
|
|
|
|
|
|
|
|
| |
Replace 'zope.interface.classProvides' usage with equivalent
'zope.interface.provider' decorator.
Replace 'zope.interface.implements' usage with equivalent
'zope.interface.implementer' decorator.
|
|
|
|
| |
This is an error in test setup of a different package that creates a too simply dummy site manager context.
|
|
|
|
| |
use the default PageTemplateEngine.
|
|
|
|
| |
to do it twice. This behavior has now been documented in the interface method description of ``pt_edit``.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This volatile attribute is relied upon by some legacy code such as the
Zope 2 product ``PageTemplates``.
In this changeset, the interface is changed to match that of the TAL
parser's ``getCode`` method which returns a tuple ``(program,
macros)``. These are in turn assigned to the volatile attributes
``_v_program`` and ``_v_macros``.
|
| |
|
| |
|
|
|
|
| |
implementation replacement via a utility component registration.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
o Moved / cleaned up related test scaffolding too.
|
|
|
|
|
| |
Change package's mailing list address to zope-dev at zope.org.
Change `cheeseshop` to `pypi` in the packages' homepage url.
|
|
|
|
| |
Ref: http://mail.zope.org/pipermail/zope-dev/2009-March/035277.html
|
|
|
|
|
|
| |
regarding
trailing newline characters.
|
| |
|
|
|
|
| |
(appearently being a cruft) without removing the method from the interface
|
| |
|
|
and then used find_packages.
Changed the try, except statement in __init__.py.
Removed setup.cfg.in, INSTALL.txt, develop.py, CHANGES.txt, test.py,
MANIFEST.in and README.txt because they were no longer needed.
|