Jens Vagelpohl
Jens Vagelpohl
Dieter, was this fixed as part of Chameleon 3.7.0?
FYI, this is still unfixed with Chameleon 3.8.1
I am totally fine with that - as long as any changes we make don't suddenly expose methods and functions that were not exposed before.
@ale-rt You mean nothing should be published that has no security declarations? The only publishable filesystem code should be code covered by some kind of security declaration.
Putting that general extension mechanism for `ZPublisher` converters would be my preferred solution as well, then everyone can register their own more easily or publish add-ons that contain such registrations...
Creating the registration mechanism is a matter of adding one single function as a clean entry point for adding converters. Even that isn't strictly necessary because as the OP proves...
malthe/chameleon#311 is a duplicate of malthe/chameleon#177
You're welcome to create a PR that integrates functionality directly, meaning without introducing dependencies to outside packages.
FWIW, it is **slightly** tested now... https://coveralls.io/builds/23283011/source?filename=src/Zope2/Startup/serve.py
The missing WSGI documentation has been added at https://zope.readthedocs.io