Hey,
These sound good to me, as long as they're off by default, have tests, and
don't break existing behavior.
> package="."
> recursive="True"
> ignore="zope.app.zcmlfiles ice.control"
> />
>
> This not include packages `zope.app.zcmlfiles` and `ice.control`, but
> include their dependencies.
On Wed, Jan 6, 2010 at 10:44 AM, Hermann Himmelbauer wrote:
>> +1 on just "bream" from an interested bystander. Somehow the "blue" makes
>> me think of microsoft.
>
> Microsoft, really?
I guess it's some blurred combination of the blue color schemes I
always associate with Windows, and the blue
On Tue, Jan 5, 2010 at 9:29 AM, Stephan Richter <
srich...@cosmos.phy.tufts.edu> wrote:
> On Monday 04 January 2010, Baiju M wrote:
> > I am proposing to call "Zope 3 - the web frame work"
> > as "BlueBream". The main use for name is documentation.
> > But the package named "bluebream" w
Hi,
On Fri, Dec 18, 2009 at 9:47 AM, Lennart Regebro wrote:
> On Fri, Dec 18, 2009 at 08:51, Brian Sutherland
> wrote:
>> I like things to fail noisily and loudly unconfigured and give good
>> information about what's wrong.
>
> +1
[snip]
> we make zope.interface aware that such a thing as util
Hi,
On Thu, Dec 17, 2009 at 10:15 AM, Martijn Faassen
wrote:
> * It'd be nice if __call__ came back with a LookupError instead of a
> TypeError, but how to get from A to B without breakage?
Maybe I've misunderstanding, but what's the advantage of making
IFoo(x) raise a LookupError instead of a T
On Tue, May 5, 2009 at 8:07 AM, Martin Aspeli
> wrote:
> Lennart Regebro wrote:
> > Can you expand on this argument, because I don't understand it. Zope
> > 2.10 doesn't stop working because Zope 2.12 no longer supports Python
> > 2.4. And you are not expected to use Zope Toolkit with Zope 2.10,
ceLanguage interface, and mark the current request with
IForceLanguage before rendering the template.
egj
On Fri, Apr 17, 2009 at 3:35 PM, Ethan Jucovy wrote:
> How about just monkeypatching the active negotiator?
>
> {{{
> negotiator = getUtility(zope.i18n.interfac
ceLanguage interface, and mark the current request with
IForceLanguage before rendering the template.
egj
On Fri, Apr 17, 2009 at 3:35 PM, Ethan Jucovy wrote:
> How about just monkeypatching the active negotiator?
>
> {{{
> negotiator = getUtility(zope.i18n.interfac
How about just monkeypatching the active negotiator?
{{{
negotiator = getUtility(zope.i18n.interfaces.INegotiator)
orig = negotiator.getLanguage
negotiator.getLanguage = lambda foo, bar: 'fr'
text = my_page_template()
negotiator.getLanguage = orig
}}}
Haven't tested it, but in my (limited) unders
On Mon, Mar 2, 2009 at 9:59 AM, Martijn Faassen wrote:
>> Also, is there any caching for already processed packages in the
>> include finder code? If no, I'd probably like to contribute some, if
>> I'll use z3c.autoinclude. :)
>
> Ah, you're thinking in the same direction. I don't think there's an
On Fri, Feb 27, 2009 at 10:35 AM, Martijn Faassen
wrote:
> Hey,
>
> On Thu, Feb 26, 2009 at 5:32 PM, Ethan Jucovy wrote:
>> That's true on paper, but in practice z3c.autoinclude's *indirection*
>> does make a difference when you're just trying to debug what&
On Thu, Feb 26, 2009 at 7:07 AM, Martijn Faassen wrote:
> Hey,
>
> On Thu, Feb 26, 2009 at 12:43 PM, Dan Korostelev wrote:
>> Yep, I know about z3c.autoinclude, but I don't like it, as it makes
>> things more implicit and it also
>
> Yes, automation makes things more implicit. This is *not* an ar
Hey Christian,
I finally had a bit of time to sort out my Zope.org SVN credentials
and try to look into this ... but I'm actually not getting very far.
What I'm stumped on: is there any way to find out which "extras" have
been installed with a package?
The details:
The bad line is src/z3c/autoi
On Thu, Jul 17, 2008 at 2:17 PM, Martijn Faassen <[EMAIL PROTECTED]> wrote:
>> Just FYI, the final resting place for this information will likely be
>> inside a more general documentation website, the address buildout.zope.org
>> is just a temporary resting place.
>
> Just to make a discussion Jens
14 matches
Mail list logo
