Hi!
Products.Five.browser.adding is basically a copy of
zope.app.container.browser.adding. Over time they became more out of
sync than necessary. I'd like to fix that, but have one question:
In the Five version
from zope.app import zapi
factory = zapi.getUtility(IFactory, type_name)
Hi yuppie
Betreff: [Zope-dev] coding style: using zapi recommended?
[...]
In the Five version
from zope.app import zapi
factory = zapi.getUtility(IFactory, type_name)
was replaced by
import zope.component
factory = zope.component.getUtility(IFactory, type_name)
Use
On Apr 14, 2008, at 7:29 AM, Roger Ineichen wrote:
Feel free to replace zapi everywhere in all packages
if you change something.
+1
Jim
--
Jim Fulton
Zope Corporation
___
Zope-Dev maillist - Zope-Dev@zope.org
On Sunday 13 April 2008, Jim Fulton wrote:
FWIW, I think using test extras is a necessary evil when testing
dependencies are significant. I wouldn't use it just to avoid a
dependency on zope.testing, but I would and have used test extras to
avoid more extensive dependencies.
+1
Hello,
Making a mistake in setup.py like this:
...
'foo.bar [test]'
'foo.lib',
...
(note the missing ,)
Makes buildout unhappy:
Develop: '...'
error in foo.other setup command: 'extras_require' must be a dictionary whose
values are strings or lists of strings
Has anyone already setup a more permanent log for buildouts. I am
wanting a more permanent record of what has happened when buildout is
run. I believe this likely ought to be part of zc.buildout so that you
identify a buildout.log location. Many thanks.
Regards,
David
Malthe Borch wrote:
On Z2, certain imports need to come from Products.Five, to play nicely
with ZPublisher and friends.
Not really. You can inherit from zope.publisher.browser.BrowserView and
Five's browser:page / directive will magically slap
Acquisition.Explicit into a newly-created
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Martijn Faassen wrote:
Technically, I think that this is going to be hard. You'd need to patch
in the magic acquisition base class. Acquisition is the main reason that
some of the code needed to be
Philipp von Weitershausen wrote:
*IF* you'd like to be pragmatic, I'd suggest we clean up those failing
Plone tests, merge the branch and be on our way.
+1
- C
___
Zope-Dev maillist - Zope-Dev@zope.org
On Apr 14, 2008, at 12:39 PM, David Pratt wrote:
Has anyone already setup a more permanent log for buildouts. I am
wanting a more permanent record of what has happened when buildout
is run. I believe this likely ought to be part of zc.buildout so
that you identify a buildout.log location.
On Apr 14, 2008, at 19:11 , Philipp von Weitershausen wrote:
*IF* you'd like to be pragmatic, I'd suggest we clean up those
failing Plone tests, merge the branch and be on our way.
+1
jens
___
Zope-Dev maillist - Zope-Dev@zope.org
Philipp von Weitershausen wrote:
*IF* you'd like to be pragmatic, I'd suggest we clean up those failing
Plone tests, merge the branch and be on our way. Yes, we *might* be
plastering over a potential problem in the patch, but the other
tests didn't seem to be affected and intensive alpha
Hi Jim. Yes, I definitely want a logging configuration also. I'm at
least hoping to look into the logging setup in the next couple of days
in between some other things. Many thanks.
Regards,
David
Jim Fulton wrote:
On Apr 14, 2008, at 12:39 PM, David Pratt wrote:
Has anyone already setup a
On Mon, 14 Apr 2008 10:11:11 -0700, Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
*IF* you'd like to be pragmatic, I'd suggest we clean up those failing
Plone tests, merge the branch and be on our way.
I'm also happy to make it visible on the Plone agenda, as long as it's
made clear
14 matches
Mail list logo
