Dieter Maurer wrote:
yuppie wrote at 2006-3-10 20:20 +0100:
...
To support WebDAV as widely as possible, I would prefer to
get rid of all id restrictions. I do not like to see
new restrictions emerging...
You just don't like it or do you know a better alternative?
We need a way to make sure
Philipp von Weitershausen wrote:
yuppie wrote:
In Zope 3 the NameChooser makes sure you can't use content IDs starting
with '+' or '@'.
Zope 2 doesn't allow '+' in content IDs (actually the error message says
the ID contains characters illegal in URLs), but you can use content IDs
like
Hi!
Philipp von Weitershausen wrote:
Chris McDonough wrote:
and should be fixed in Zope 2.8, 2.9 and trunk.
We'd be changing Zope 2's behaviour (not fixing a Five bug), I would
therefore vote for making this change on the Zope 2 trunk only.
I'd be apt to not further restrict the set of
On 13 Mar 2006, at 15:15, Andreas Jung wrote:
Due to some changes in my email configuration I would like to use
another email address for checkin notifications email other than the
current one. Is there a way to configure this on my own or do I
have to
beg before the svn admistrator?
The
I doubt this will break a significant amount of code. The
restriction was removed 5 months ago and AFAICS it was removed to
allow email addresses as IDs. That use case will not be broken if
we disallow again IDs starting with '@'.
It seems that you can reasonably easily apply the @
Andreas Jung wrote:
Due to some changes in my email configuration I would like to use
another email address for checkin notifications email other than the
current one. Is there a way to configure this on my own or do I have to
beg before the svn admistrator?
Just update your email address on
Hi Chris!
Chris McDonough wrote:
I doubt this will break a significant amount of code. The restriction
was removed 5 months ago and AFAICS it was removed to allow email
addresses as IDs. That use case will not be broken if we disallow
again IDs starting with '@'.
It seems that you can
On Mar 13, 2006, at 1:22 PM, Chris McDonough wrote:
On Mar 13, 2006, at 1:06 PM, yuppie wrote:
I'm not concerned about my own app code. I know the problem and
how to fix it.
And I'm not concerned about people like you who monkeypatch that
code. You know that monkeypatching is always on
yuppie wrote at 2006-3-13 10:07 +0100:
...
In order to support WebDAV as widely as possible, I
have removed almost all id restrictions quite some time ago.
I hope that this will happen in the official Zope as well.
The current state of affairs is not really justified.
To reach that goal more
yuppie wrote at 2006-3-13 10:09 +0100:
...
I don't understand that differentiation. Five is part of Zope 2, so each
Five issue is also a Zope 2 issue.
But you can fix this issue either in Five or in ObjectManager.
You propose a change in ObjectManager which affects not Five
use of Zope2.
--
Chris McDonough wrote at 2006-3-13 10:21 -0500:
... silly id restrictions ...
Here's my current monkeypatch to Zope to unrestrict a good number of
characters:
def patch_objectmanager_badid():
Causes Zope to be less restrictive in the set of characters it
accepts as valid within
On Mar 13, 2006, at 1:06 PM, yuppie wrote:
I'm not concerned about my own app code. I know the problem and how
to fix it.
And I'm not concerned about people like you who monkeypatch that
code. You know that monkeypatching is always on your own risk and
you know how to modify your monkey
http://www.zope.org/Members/rossp/PDBDebugMode
PDBDebugMode - PDB post-mortem debugging on exceptions when debug-mode=on
If a relevant error log object is found, exceptions included in the
error log's ignored exception types will be ignored and the debugger
won't be invoked.
It also enables the
Hi Paul!
Paul Winkler wrote:
On Mon, Mar 13, 2006 at 07:06:28PM +0100, yuppie wrote:
I'm concerned about the people we encourage to use Five technology.
Views are a major feature of Five. Should we warn people not to use
views? Or instruct them how to patch Zope 2 to protect views against
Hi --
I have a fix for http://www.zope.org/Collectors/Zope/2037 and would like
to write a unit test for it. However, I don't seem to be able to run the
existing unit tests for SiteAccess with zopectl test.
I created a new instance, then in my instance run
bin/zopectl test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geoff Davis wrote:
Hi --
I have a fix for http://www.zope.org/Collectors/Zope/2037 and would like
to write a unit test for it. However, I don't seem to be able to run the
existing unit tests for SiteAccess with zopectl test.
I created a new
Dieter Maurer wrote:
Chris McDonough wrote at 2006-3-13 10:21 -0500:
... silly id restrictions ...
Here's my current monkeypatch to Zope to unrestrict a good number of
characters:
def patch_objectmanager_badid():
Causes Zope to be less restrictive in the set of characters it
Hi Geoff,
On Mon, 13 Mar 2006 18:04:14 -0500, Geoff Davis wrote:
bin/zopectl test --dir=/opt/Zope-2.8/lib/python/Products/SiteAccess/tests/
which yields the following:
Running tests via: /usr/local/bin/python /opt/Zope-2.8/bin/test.py -v
--config-file /home/zope/zopefix/etc/zope.conf
18 matches
Mail list logo
