Hello!
My company wants me to upgrade the timeworn zope-2.7.4 to one of the
newest ones available.
I decided to take zope-2.11.1 but after installing and running it in
debug-mode i get the following error-messages:
2008-08-01T09:04:39 ERROR Zope.ZODBMountPoint Failed to mount database.
Wolfgang Lausenhammer wrote:
LockError: Couldn't lock
'D:\\workspace_zope\\xla-2008/var/Stdcontainer_o.fs.lock'
Can the user the zope process is running as write to this file?
(or create it, since it likely doesn't exist?)
TypeError: not all arguments converted during string formatting
Wolfgang Lausenhammer wrote:
LockError: Couldn't lock
'D:\\workspace_zope\\xla-2008/var/Stdcontainer_o.fs.lock'
Can the user the zope process is running as write to this file?
(or create it, since it likely doesn't exist?)
The file is existing. I tried to delete all the .index,
Hi all.
I need to implement an interaction with an external web service.
The external webservice basically can either provide or accept
messages from my zope application. The messages are either produced by
my application (and need to be sent to the external application via
web service) or
Hi all.
I have a zope application which uses a db (postgreSQL) to store and
retrieve data. I would like to cache it.
It is ok for me to cache them on thread-base. Up to now I've used a
simple _v_ attribute, with a dictionary.
The approach works, but:
- the _v_ attribute is not transactional
--On 1. August 2008 15:55:41 +0200 Marco Bizzarri
[EMAIL PROTECTED] wrote:
Hi all.
I have a zope application which uses a db (postgreSQL) to store and
retrieve data. I would like to cache it.
It is ok for me to cache them on thread-base. Up to now I've used a
simple _v_ attribute, with a
Thanks for your suggestions, Andreas.
Any chance these are going to work under Zope 2.8?
Regards
Marco
On Fri, Aug 1, 2008 at 4:04 PM, Andreas Jung [EMAIL PROTECTED] wrote:
--On 1. August 2008 15:55:41 +0200 Marco Bizzarri [EMAIL PROTECTED]
wrote:
Hi all.
I have a zope application which
My ZSQL product has a very simple feature for hooking up up to
memcache but with one caveat: that you can't invalidate the cache.
It only works for selects of course but it's really easy to work with. E.g.
SQLSelectAverageUserAge(min=10, max=20, memcache__=True)
(defaults to 5*60 seconds)
Thanks Martijn for your answer.
I tried fsdump but it did not work I got a FileStorageFormatError...
Is there any other way I can obtain the needed paramater (position) for the
truncate function where the CorruptedDataError occured?
Another question, is there a way of extracting all data or
On Fri, Aug 1, 2008 at 7:01 PM, Remy Pinsonnault
[EMAIL PROTECTED] wrote:
I tried fsdump but it did not work I got a FileStorageFormatError...
You only get that error if a) the first four bytes of the file are not
'FS21', or b) the file is smaller than 4 bytes. Are you sure you were
trying this
vyshakh,
vyshakh krishnan wrote:
Many of the the warnings in other modules are found similar to this warning.
Please enumerate them.
Please read and respond to all points raised in mails.
Unless I missed something, we're still waiting to see the full list of
the warnings in other modules.
Stephan Richter a écrit :
Log message for revision 89104:
* Added latest version of zope.app.security to avoid deprecation
warnings.
* Added history file for the KGS to hopefully create better release
notes.
Did you miss the CHANGES.txt in zope.release ? We have two histories
Summary of messages to the zope-tests list.
Period Thu Jul 31 11:00:00 2008 UTC to Fri Aug 1 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Thu Jul 31 20:56:10 EDT 2008
URL:
On Friday 01 August 2008, Christophe Combelles wrote:
Did you miss the CHANGES.txt in zope.release ? We have two histories now.
Nope, but that file tracks the package -- source code -- changes of
zope.release.
I wanted a separate file that tracks the changes to the
controlled-packages.cfg
Hey Stephan,
Thanks for doing all the work on KGS and the Zope 3.4.0 release.
There are unfortunately a few things in this process that have me
somewhat confused. I hope we can work out a way to clarify the process
for 3.4.x and helping to clarify the process for 3.5.x.
Firstly, could you
Stephan Richter a écrit :
On Friday 01 August 2008, Christophe Combelles wrote:
Did you miss the CHANGES.txt in zope.release ? We have two histories now.
Nope, but that file tracks the package -- source code -- changes of
zope.release.
I wanted a separate file that tracks the changes to
On Friday 01 August 2008, Martijn Faassen wrote:
Thanks for doing all the work on KGS and the Zope 3.4.0 release.
Thank Marius for getting into it and giving me some incentive to work on it
again too. :-)
There are unfortunately a few things in this process that have me
somewhat confused. I
On Friday 01 August 2008, Christophe Combelles wrote:
I wanted a separate file that tracks the changes to the
controlled-packages.cfg file.
In my understanding, there is almost no source code in 'zope.release',
since it has been moved into 'zope.kgs'. So there should be very few
entries in
On Fri, Aug 01, 2008 at 08:26:02AM -0700, Stephan Richter wrote:
We have been in release candidate space for Zope 3.4 for a very long
time; since january 31th. Do we really need 5 release candidates over a
period of half a year? Would we really have been harmed if we'd released
3.4.0 final
Stephan Richter a écrit :
On Friday 01 August 2008, Christophe Combelles wrote:
I wanted a separate file that tracks the changes to the
controlled-packages.cfg file.
In my understanding, there is almost no source code in 'zope.release',
since it has been moved into 'zope.kgs'. So there should
On Fri, Aug 1, 2008 at 2:06 PM, Marius Gedminas [EMAIL PROTECTED] wrote:
I also want to investigate the weird TALES iterator change where 'odd'
and 'even' swapped meanings between 3.2 and 3.4. If that swap happened
before 3.3, it's too late, but if it happened after 3.3, then I'm
tempted to
Hi,
could someone remove this package from the PyPI :
http://pypi.python.org/pypi/zope.size/3.4dev-r73090
This is an empty development version, considered more recent by PyPI than the
latest released version 3.4.0. (which is r78211)
Christophe
___
Christophe Combelles wrote:
could someone remove this package from the PyPI :
http://pypi.python.org/pypi/zope.size/3.4dev-r73090
This is an empty development version, considered more recent by PyPI
than the latest released version 3.4.0. (which is r78211)
Done.
In case anybody's wondering
Christophe Combelles wrote:
Stephan Richter a écrit :
On Friday 01 August 2008, Christophe Combelles wrote:
Did you miss the CHANGES.txt in zope.release ? We have two histories
now.
Nope, but that file tracks the package -- source code -- changes of
zope.release.
I wanted a separate file
24 matches
Mail list logo
