Thaddeus H. Black wrote:
This question regards the code in Zope's
zpasswd.py. If you know zpasswd.py or are
involved in Debian, please reply.
I've attempted to add this to the Zope issue tracker and used the
Debiuan bug's email address so it can be tracked there too.
Please let me know if it doe
This question regards the code in Zope's
zpasswd.py. If you know zpasswd.py or are
involved in Debian, please reply.
Debian GNU/Linux 3.1 releases soon. The Debian
Zope package (actually the Debian `zopectl'
package) has what Debian calls a Release
Critical Bug open against it
[http://bugs.debia
Em Qua, 2004-08-18 às 12:22, Ames Andreas (MPA/DF) escreveu:
> [...]
> Questions:
>
> - Is this the right forum/place to send patches to?
This is the right forum to discuss the patches, and to send them for
evaluation if it's a small one, like yours. The best place to actually
send patches to i
Hi,
I had a thinko in my previous patch
(http://mail.zope.org/pipermail/zope-dev/2004-August/023630.html)
which is corrected in the attached version of the patch. Sorry for
any inconvenience, I might have caused.
As I'm sort of protocol challenged (thanks to corporate firewall), svn
unfortunatel
On 12/07/2004, at 12:29 PM, Chris McDonough wrote:
FWIW, as far as I understand the "prevent commit on conflict" behavior
*is* currently the behavior for caught ReadConflictErrors. The only
time ZODB doesn't exhibit this behavior is *during the commit of a
transaction*. If a commit is attempted a
