-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21.02.2009 5:14 Uhr, Martin Aspeli wrote:
>
> We already have all the infrastructure and code we need. If you can
> accept that a 'microsite' is a folder (zope.org/projects/zope2 or /zodb
> or /whatever), then we already have skeletal microsites
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21.02.2009 8:16 Uhr, Lennart Regebro wrote:
> About wiki/vs microsite, I also would hope for a microsite. Wikis are
> good for community generated docs/howtos and stuff, which we already
> have for Zope2. And a pretty good one at that:
> http://wik
On Sat, Feb 21, 2009 at 05:14, Martin Aspeli wrote:
> The new.zope.org initiative died because no-one could write any content.
> Even then 5-10 pages of content requires for a very basic microsite was
> too much, and several separate calls for volunteers produced almost no
> actual content, even i
On Thu, Feb 19, 2009 at 18:49, Andreas Jung wrote:
> because of the failure of the new.zope.org project I would like to put
> the hat on for reorganizing the Zope 2 presentation on zope.org. The
> goal is having up some pages with the downloads, basic pointers and
> links with the final release of
Andreas Jung wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 20.02.2009 15:23 Uhr, Martijn Faassen wrote:
>> I really hope someone provides the resources to create a microsite
>> instead of "the Zope 3 approach on wiki.zope.org". Grok is doing two
>> things: a Plone-based site wh
Chris Withers wrote:
> Andreas Jung wrote:
>> because of the failure of the new.zope.org project I would like to put
>> the hat on for reorganizing the Zope 2 presentation on zope.org.
>
> Is this failure official or is there just no action on this?
Let's say both.
I basically gave up trying to
Simon Michael wrote:
> Martijn Faassen wrote:
>> and a Sphinx-based website for official documentation maintained in SVN.
>
> +1 of course,
>
>> Anyway, overall I'm a big supporter of the "microsite" approach. It's
>> the only approach that actually got us to new web sites over the last years.
>
Christian Theune wrote:
> On Fri, 2009-02-20 at 18:18 +0100, Martijn Faassen wrote:
>> We discovered this when Christian Theune said he wanted his package
>> __init__.py empty as otherwise he runs into circular import issues. Some
>> of the others including myself were puzzled as we put APIs in
On Fri, 2009-02-20 at 18:18 +0100, Martijn Faassen wrote:
> We discovered this when Christian Theune said he wanted his package
> __init__.py empty as otherwise he runs into circular import issues. Some
> of the others including myself were puzzled as we put APIs in
> __init__.py quite frequentl
Hi there,
Jim Fulton wrote:
[snip]
>> I suspect there are two possibilities:
>>
>> * no API defined in __init__.py and absolute imports
>>
>> * API defined in __init__.py and dotted.package.name.references
>> don't work.
>
> In what way don't they work?
> I don't see how this has anything to d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20.02.2009 17:48 Uhr, Tres Seaver wrote:
> Andreas Jung wrote:
>> Log message for revision 96831:
>> moved HISTORY
>
>
>> Changed:
>> D Zope/trunk/doc/HISTORY.txt
>> A Zope/trunk/doc/obsolete/HISTORY.txt
>
> -1. I would rather keep tha
Martijn Faassen wrote:
> and a Sphinx-based website for official documentation maintained in SVN.
+1 of course,
> Anyway, overall I'm a big supporter of the "microsite" approach. It's
> the only approach that actually got us to new web sites over the last years.
I must quibble: I agree with you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
> Log message for revision 96831:
> moved HISTORY
>
>
> Changed:
> D Zope/trunk/doc/HISTORY.txt
> A Zope/trunk/doc/obsolete/HISTORY.txt
- -1. I would rather keep that in the main doc directory.
Tres.
- --
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> On Feb 20, 2009, at 10:15 AM, Martijn Faassen wrote:
>> This looks like a religious debate though.
>
>
> Maybe. The most important reason for a style guide is to make code
> more readable. In my experience, from imports make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20.02.2009 15:23 Uhr, Martijn Faassen wrote:
>
> I really hope someone provides the resources to create a microsite
> instead of "the Zope 3 approach on wiki.zope.org". Grok is doing two
> things: a Plone-based site where people can contribute do
Hey,
On Fri, Feb 20, 2009 at 5:05 PM, Jim Fulton wrote:
[snip]
> You will still likely have other problems unless you use deferred imports
> which will generally solve this problem in a robust way.
I've created quite a few packages that have this structure without any
problems in my experience.
On Feb 20, 2009, at 11:00 AM, Martijn Faassen wrote:
...
> The main take-home message was that the import mechanics of Python are
> rather surprising in operation here and it's very hard to reason about
> it. It has something to do with 'foo'" having to be more initialized
> during importing than
Hi there,
> Names exported to a containing package cause circular import problems
> whether or not from imports are used. I've seen from imports make this
> worse. I believe you've seen cases where they make it better. I think the
> only way to avoid this is to use a deferred import mechanism su
Hey,
Andreas Jung wrote:
> I followed the whole thread with some amusement. There are too many
> personal coding styles on the market which makes it impossible to
> regulate all all and everything. At least this discussion about
> about how to write imports properly appears esoteric to me.
Yeah,
On Feb 20, 2009, at 10:22 AM, Martijn Faassen wrote:
> Jim Fulton wrote:
>> On Feb 19, 2009, at 2:07 PM, Marius Gedminas wrote:
>> ...
>>> -1 for repeating
>>> english.adjective.fully english.adverb.qualified
>>> english.noun.package
>>> english.noun.names all over the place in the code
>>
>> I
Hey Christian,
You do realize you started a bikeshed discussion right?
Suddenly people wake up and spout opinions because everybody has an
opinion about this. :)
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailm
On Feb 20, 2009, at 10:15 AM, Martijn Faassen wrote:
> Jim Fulton wrote:
>
>> BTW, I strongly discourage from imports. (I didn't always have this
>> opinion, but have seen the error of my ways. Thanks to Fred Drake for
>> nudging me in this direction.) IMO, this is wildly more important
>> than
Jim Fulton wrote:
> On Feb 19, 2009, at 2:07 PM, Marius Gedminas wrote:
> ...
>> -1 for repeating
>> english.adjective.fully english.adverb.qualified english.noun.package
>> english.noun.names all over the place in the code
>
> If you have package hierarchies remotely that deep, you have bigger
Hey,
Joachim König wrote:
>
> import zope.interface as interface
Surprisingly enough this actually has a subtly different behavior than:
from zope import interface
the former can create circular import situations where the latter doesn't.
Regards,
Martijn
___
Jim Fulton wrote:
> BTW, I strongly discourage from imports. (I didn't always have this
> opinion, but have seen the error of my ways. Thanks to Fred Drake for
> nudging me in this direction.) IMO, this is wildly more important than
> any of the issues raised in this thread.
I like from imp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20.02.2009 15:39 Uhr, Jim Fulton wrote:
> On Feb 20, 2009, at 7:48 AM, Joachim König wrote:
> ...
>>> 2. Depending on what code you might unearth, Interface could be
>>> either zope.interface.Interface, or the older version
>>> Interface.Interf
On Feb 20, 2009, at 7:48 AM, Joachim König wrote:
...
>> 2. Depending on what code you might unearth, Interface could be
>> either zope.interface.Interface, or the older version
>> Interface.Interface. Package qualification makes this unambiguous.
>>
> if module qualification is enough and
Hey Andreas,
Andreas Jung wrote:
> There are basically two options: create a dedicated microsite (similar
> to grok.zope.org) or follow the Zope 3 approach on wiki.zope.org. Unless
> someone provides enough resources in helping, I would like to go with
> the wiki approach since it is much easier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.02.2009 22:14 Uhr, Chris Withers wrote:
> Andreas Jung wrote:
>> See this thread:
>>
>> http://mail.zope.org/pipermail/zope-web/2009-January/thread.html
>
> Shame, oh well, I think dictatorship is the way to go and I think you'd
> make a pretty
On Fri, Feb 20, 2009 at 2:41 AM, Michael Howitz wrote:
> Am 19.02.2009 um 18:48 schrieb Malthe Borch:
>> Log message for revision 96790:
>> Reformatted changelog dates.
>>
>> Changed:
>> U z3c.pt/trunk/CHANGES.txt
>>
>> -=-
>> Modified: z3c.pt/trunk/CHANGES.txt
>> =
Jim Fulton wrote:
> On Feb 19, 2009, at 4:07 PM, Shane Hathaway wrote:
>
>
>> You're saying that:
>>
>> import zope.interface.Interface
>>
>> class IFoo(zope.interface.Interface):
>> ...
>>
>> is better than:
>>
>> from zope.interface import Interface
>>
>> class IFoo(Int
Summary of messages to the zope-tests list.
Period Thu Feb 19 12:00:00 2009 UTC to Fri Feb 20 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-trunk Python-2.4.6 : Linux
From: Zope Tests
Date: Thu Feb 19 20:50:04 EST 2009
URL: http://mail.zope.
On Feb 19, 2009, at 4:07 PM, Shane Hathaway wrote:
> Fred Drake wrote:
>> On Thu, Feb 19, 2009 at 11:03 AM, Jim Fulton wrote:
>>> BTW, I strongly discourage from imports. (I didn't always have this
>>> opinion, but have seen the error of my ways. Thanks to Fred Drake
>>> for
>>> nudging me in
On Feb 19, 2009, at 2:07 PM, Marius Gedminas wrote:
...
> -1 for repeating
> english.adjective.fully english.adverb.qualified english.noun.package
> english.noun.names all over the place in the code
If you have package hierarchies remotely that deep, you have bigger
problems.
If dotted names
34 matches
Mail list logo
