Hi All,
Would anyone have a problem if I added the necessary security
declarations to allow the python logging module to be used from
restricted code?
I'd like do this both for the trunk and the 2.8 branch, unless anyone
has huge objections...
Furthermore, I'd like to change zope.conf to a
Andreas Jung wrote:
Argh...there is also a gadfly package coming from Zope 3. So when we
remove it from the Zope 2 core we get it back with Zope 3 :-)
Well, having a lightweight semi-functional rdb engine in the distro has
always seemed handy for me, mainly for testing rdb-related components
On 10 Oct 2005, at 08:58, Chris Withers wrote:
Andreas Jung wrote:
Argh...there is also a gadfly package coming from Zope 3. So when
we remove it from the Zope 2 core we get it back with Zope 3 :-)
Well, having a lightweight semi-functional rdb engine in the distro
has always seemed ha
Chris Withers wrote:
Hi All,
Would anyone have a problem if I added the necessary security
declarations to allow the python logging module to be used from
restricted code?
I'd like do this both for the trunk and the 2.8 branch, unless anyone
has huge objections...
I think you need to be v
On Mon, Oct 10, 2005 at 08:58:53AM +0100, Chris Withers wrote:
| Andreas Jung wrote:
| >Argh...there is also a gadfly package coming from Zope 3. So when we
| >remove it from the Zope 2 core we get it back with Zope 3 :-)
|
| Well, having a lightweight semi-functional rdb engine in the distro has
SQLite implements enough of a subset of SQL to be genuinely useful
and it's performance isn't too bad either. There is a Zope DA for it
somewhere too.
We've never been able to use Gadfly for testing as it's so far from
standard SQL that it just causes more problems than it solves - as we
--On 10. Oktober 2005 11:03:54 -0300 Sidnei da Silva
<[EMAIL PROTECTED]> wrote:
If I'm allowed to say anything, I would like to see gadfly being
replaced by sqlite. It's available mostly everywhere except in Windows
by default, as many products already use it. sqlite itself is 'public
doma
(sorry for the cross-post)
I'm currently facing an issue that seems to be a result of a bad
interaction between CMF, TALES and Restricted Python.
The issue currently happens when:
1. A TALES 'Path Expression' in 'Caching Policy Manager' is evaluated
2. The result of evaluating a sub-expressi
