From: Florent Guillaume [EMAIL PROTECTED]
As Jim said, If we want to get this into 2.6, we need to move quickly.
I want it in. It's so amazingly useful, that I want it. 2.6 is moving so
slow anyway, that I don't see it as a big problem.
Best Regards
Lennart Regebro, Torped
Once again I have the problem that all references to imported
modules/objects/whatever dissapear when refreshing.
It seems like sometimes some modules are not refreshed, even though they
really are. Could it be that not all modules are properly purged from
memory, and then when Zope core calls
Lennart Regebro wrote:
Once again I have the problem that all references to imported
modules/objects/whatever dissapear when refreshing.
It seems like sometimes some modules are not refreshed, even though they
really are. Could it be that not all modules are properly purged from
memory,
We had to wait this long, why not wait for a bit longer. I just hope it
doesn't give some the excuse to drag it on more. That was one of the things
I loved about Zope was Release Early/often mantra. Now with the 2.6 dabacle
lasting over 3 months. This better not happen again people :-) We
Shane Hathaway [EMAIL PROTECTED] wrote:
- Making one product depend on another using import statements
I'm doing that, and I observe the problem Lennart is describing (objects
turning into None). Any idea for a workaround?
Florent
--
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87
From: Shane Hathaway [EMAIL PROTECTED]
You're likely to run into this if your product does
anything more than simply define and register classes that derive from
SimpleItem.
Strangely enough we do this all the time, but we only get problems with the
core EasyPublisher products.
Which of the
From: James Johnson [EMAIL PROTECTED]
We had to wait this long, why not wait for a bit longer. I just hope it
doesn't give some the excuse to drag it on more. That was one of the
things
I loved about Zope was Release Early/often mantra. Now with the 2.6
dabacle
lasting over 3 months. This
Truth is that the Zope code has done anything but languish in the last few
months. Unfortunately most people are bound by our release cycle, which has
given that impression.
As for i18n in 2.6, The Zope Pope gave the nod, so I consider it a done deal,
assuming it gets checked in.
-Casey
On
Lennart Regebro wrote:
From: Shane Hathaway [EMAIL PROTECTED]
You're likely to run into this if your product does
anything more than simply define and register classes that derive from
SimpleItem.
Strangely enough we do this all the time, but we only get problems with the
core
On Wednesday 18 Sep 2002 4:23 pm, Lennart Regebro wrote:
Having to restart each time I make a change is slowing down my development
to a complete halt.
Something is wrong here. You should be able to restart Zope within a few
seconds.
Are you using FileStorage? I guess you are not shutting
From: Shane Hathaway [EMAIL PROTECTED]
The first thing you need to make sure you do is set up dependencies. If
FooProduct imports EasyPublisher, set FooProduct to be auto-refreshable,
then visit EasyPublisher and specify the dependency. Then, every time
EasyPublisher gets refreshed,
A new idea:
Could the problem appear when you have circular product imports, i.e.:
In Product.ProductA.ProductA.py:
from Product.ProductB.SupportModule import Supportmodule
In Product.ProductB.ProductB.py:
from Product.ProductB.AnotherModule import AnotherModule
Maybe the refresh gets
Lennart Regebro wrote:
A new idea:
Could the problem appear when you have circular product imports, i.e.:
In Product.ProductA.ProductA.py:
from Product.ProductB.SupportModule import Supportmodule
In Product.ProductB.ProductB.py:
from Product.ProductB.AnotherModule import
On Wed, 2002-09-18 at 13:09, Toby Dickenson wrote:
On Wednesday 18 Sep 2002 4:23 pm, Lennart Regebro wrote:
Having to restart each time I make a change is slowing down my development
to a complete halt.
Something is wrong here. You should be able to restart Zope within a few
seconds.
From: Shane Hathaway [EMAIL PROTECTED]
I assume you mean ProductA here.
Yes.
It might. In general, it's not a good thing to have circular imports in
your code anyway, since it's brittle.
They are not circular on a module-level, just on a product level, and
indeed, it seems to help to
Hello,
I´m working on a product which contains custom data in a list of multiple
dictionaries.
How can I save the list/dictionaries after changes? Persistence is enabled
(and works for other types), and _p_changed is set, also
get_transaction().commit() is called.
A second problem is that
Sounds like you are trying to persist a class attribute value. This is not
possible because instance are persistent, not classes. This is also the
reason that the values change over all the instances. You are changing a
mutable attribute of the class in place.
I would suggest setting the
From: Arndt Droullier [EMAIL PROTECTED]
How can I save the list/dictionaries after changes?
The easiest thing to do is to is to use PersistentMapping and
PersistentList.
Create them in __init__ with self.dictionary = PersistentMapping() instead
of setting them as a class attribute.
using chrism-install-branch and caring much less than
I have in my past life - I have run ab against Plone
in Zope2.6. It appears that Zope2.6 is significantly
slower than Zope2.5.1. I ran ab from my Windows
XP machine on a local network.
300Mhz Celeron w/ 256MB RAM
Zope2.5.1 Python 2.1.3
Hi,
I've seen you announcement. Too bad you quit. :)
But to me, the mission integrating PHP and Zope never seems to
finish. Especially when Zend 2's coming out. I would
expect to see someday a product like Script(PHP) to appear.
Anyway, I would like to take over PHParser under the
same name.
20 matches
Mail list logo
