Am Donnerstag, 19. Juni 2008 20:51 schrieb Martijn Faassen:
Hi there,
I'd like to announce my contribution for the expanding list of options
for SQLAlchemy integration for Zope 3.
I've just implemented a package called z3c.saconfig which implements a
utility-based way to set up SQLAlchemy's
Am Freitag, 20. Juni 2008 00:14 schrieb Martijn Faassen:
Hey,
Martijn Faassen wrote:
I intend to add support for a local utility soon,
inspired by some code sent to me by Hermann Himmelbauer.
This is now in there. It only looks faintly like Hermann's code, but it
was still very useful.
On Thu, Jun 19, 2008 at 08:51:17PM +0200, Martijn Faassen wrote:
Hi there,
I'd like to announce my contribution for the expanding list of options for
SQLAlchemy integration for Zope 3.
Looks good, I'd like to vote for moving some parts of it to
zope.sqlalchemy. Namely
Summary of messages to the zope-tests list.
Period Thu Jun 19 11:00:00 2008 UTC to Fri Jun 20 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 Jun 19 21:01:57 EDT 2008
URL:
Hermann Himmelbauer wrote:
Am Freitag, 20. Juni 2008 00:14 schrieb Martijn Faassen:
[snip]
This now works against the trunk of zope.sqlalchemy as well, as Laurence
merged my branch. I do think my code currently requires SQLAlchemy
0.5beta1 or higher.
Does it really? Because in the
Hey,
Hermann Himmelbauer wrote:
[snip]
1) Why do you need to specify what interface the factory provides, such as
here:
component.provideUtility(engine_factory, provides=IEngineFactory)
component.provideUtility(utility, provides=IScopedSession)
Why can't the utilities provide the interface
Hi there,
Brian Sutherland wrote:
[snip]
Also for this problem:
# XXX what happens if EngineFactory were to be evicted from the ZODB
# cache?
def getCached(self):
return getattr(self, '_v_engine', None)
I think you could use the same mechanism found in zope.app.cache.ram.
Hey,
Jim Fulton wrote:
[snip]
I suggest:
- decide on and advertise the new interface
- continue to do look ups the way we do now
- update relevant zcml directives (view, page, resource. etc.) to use
the new interface
+1
Update the relevant grokkers to use the new interface too. :)
Hey,
One question is what to do for persistent registrations in local sites.
I don't imagine they're used a lot, but it'd mean a content upgrade to
re-register them, right?
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
Martijn Faassen wrote:
One question is what to do for persistent registrations in local sites.
I don't imagine they're used a lot, but it'd mean a content upgrade to
re-register them, right?
The only piece of software that, to my knowledge, can actually *make*
local view registrations is
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer,
currently getting this:
creating zope.proxy
copying zope/proxy\proxy.h - zope.proxy
error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate compatible
binaries.
Chris Withers wrote:
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer,
currently getting this:
creating zope.proxy
copying zope/proxy\proxy.h - zope.proxy
error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate
Depending on how 'plone-ish' your buildout is, you can start from the
newly-created, experimental buildout-based Plone Installer for
Windows:
https://launchpad.net/plone/3.1/3.1.2/
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713
Chris Withers wrote:
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer,
currently getting this:
creating zope.proxy
copying zope/proxy\proxy.h - zope.proxy
error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate
14 matches
Mail list logo
