[Zope-dev] uuid.UUID as a rock in zope.security
Hi,
We're using UUIDs a lot, and it's pretty painful that they are security
proxied. They're in the standard library from python 2.5
(http://docs.python.org/library/uuid.html) and are immutable according
to the documentation.
I think they meet all the all the requirements to be rocks. So unless
someone complains, I'll commit the attached patch in a few days.
--
Brian Sutherland
Index: CHANGES.txt
===
--- CHANGES.txt (revision 98805)
+++ CHANGES.txt (working copy)
@@ -5,7 +5,8 @@
3.6.4 (unreleased)
--
-- None so far.
+- Make uuid.UUID a rock, they are immutable and in the python standad library
+ from python 2.5.
3.6.3 (2009-03-23)
--
Index: src/zope/security/checker.py
===
--- src/zope/security/checker.py(revision 98805)
+++ src/zope/security/checker.py(working copy)
@@ -624,6 +624,13 @@
type(pytz.UTC): NoProxy,
})
+try:
+# NOTE: remove try/except when we depend on python2.5 and up. uuid in
standard library from python 2.5.
+from uuid import UUID
+BasicTypes[UUID] = NoProxy
+except ImportError:
+pass
+
# Available for tests. Located here so it can be kept in sync with BasicTypes.
BasicTypes_examples = {
object: object(),
Index: src/zope/security/tests/test_standard_checkers.py
===
--- src/zope/security/tests/test_standard_checkers.py (revision 98805)
+++ src/zope/security/tests/test_standard_checkers.py (working copy)
@@ -424,6 +424,14 @@
>>> from pytz import UTC
>>> int(type(ProxyFactory( UTC )) is type(UTC))
1
+
+>>> try:
+... # NOTE: remove try/except when we depend on python 2.5 and greater
(uuid in standard library)
+... from uuid import UUID
+... int(type(ProxyFactory( UUID('12345678123456781234567812345678')
)) is UUID)
+... except ImportError:
+... 1
+1
"""
def test_iter_of_sequences():
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing.runner: protecting against rogue threads
On Thu, 2009-04-02 at 21:17 +0200, Dieter Maurer wrote: > Christian Theune wrote at 2009-4-2 13:30 +0200: > >if tests spawn non-daemon threads, then the test runner can get stuck. > > > >The easiest way that I see is to always --exit-with-status and to make > >--exist-with-status also call sys.exit() when the tests passed. > > I do not understand the implication. > > Do you plan that any test runs in a separate process? > > Then, I would have an objection -- test suites would take far longer. No. What I meant was this: - if non-daemon threads remain after the test runner is done and the main thread exits, the Python interpreter will not exit - we already have the option "--exit-with-status" which will make the test runner always exit (even when non-daemon threads remain). However, --exit-with-status doesn't use sys.exit() in the case of a test success. I don't want to change the process structure: I only want to assure that the processes we start also quit. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] z3c.pt bug
Hi Malthe I just improved coverage in z3c.form and found a bug in z3c.pt. Can you run the group.txt tests in z3c.form and confirm the issue. A div tag get skipped after some nested repeat tags. (line 898, in group.txt) Is this a known issue? Can you fix this or give me some hints which let me do this? Regards Roger Ineichen _ END OF MESSAGE ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 22:53 Uhr, Tres Seaver wrote: > > *This* part needs some fixing, largely because Jim's role their is an > artifact of ZC's role, now lapsed, as custodians. At a minimum, there > should be a group (I suggest the zope-web regulars) who can take over > the maintenance of that application. A *different* group should have > the role of collecting / approving the committer access requests. I agree that this part definitely needs to be fixed. I updated the developer documentation in order to point to the foundations's about page as primary contact (suggested by Jens): http://docs.zope.org/developer/becoming-a-contributor.html (possibly not reflecting my changes made to the reST documents in SVN right now). Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVjFwACgkQCJIWIbr9KYwQRQCfRRVjxVylBA67tX+lhK3UG/ra ZHsAoKeaQGkNV/JUUKvfB00UFPpJ/D/6 =catZ -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: > I'd like to report back on the progress that Bzr/Launchpad has made > addressing concerns we heard since I last brought up Canonical's offer > to host the code and contribute commercial support for the transition. > > When I do that, I'll do it on zope-dev, assuming that Tres' statement > in this thread that we should discuss there is authoritative. (I > thought the people on Foundations were the superset of people who > commit to the repo, but I guess I was mistaken. Sorry for my > misunderstanding.) The foundation members are a *subset* of all committers, with sponsoring companies added on. There are under 50 "nominated members" (formerly "committer members", whereas there are something like 375 committers. Any decision to move the repository will need to be formally made by the foundation (via its board), but that would only happen if the consensus of the members and the wider community were clearly in favor of a move. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ1VnB+gerLs4ltQ4RAtvVAJ4kPghyM3nlJGRNQN5vsJazrhR+6wCfZRui WwEbnYYd59eXJ9FOHYD9ZuM= =gtgH -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 1:31 PM, Chris Withers wrote: > Hey All, ... > The other option would be to follow Python and move to Mercurial, but > that has the same problems for me as with Bzr (no decent gui tools, > less > mature, etc) although it's a toolset I'll have to learn at some point > anyway... I'd like to report back on the progress that Bzr/Launchpad has made addressing concerns we heard since I last brought up Canonical's offer to host the code and contribute commercial support for the transition. When I do that, I'll do it on zope-dev, assuming that Tres' statement in this thread that we should discuss there is authoritative. (I thought the people on Foundations were the superset of people who commit to the repo, but I guess I was mistaken. Sorry for my misunderstanding.) However, I just got back from a long trip, and I'm going to spend some time with my family. I'll write something up to zope-dev tomorrow. Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: zope.traversing/trunk/ zcml now only depends on zope.component meta, not zope.app.component
On Thu, Apr 02, 2009 at 01:08:51PM -0400, Tres Seaver wrote:
> Gary Poster wrote:
> > Log message for revision 98787:
> > zcml now only depends on zope.component meta, not zope.app.component
> >
> > Changed:
> > U zope.traversing/trunk/CHANGES.txt
> > U zope.traversing/trunk/src/zope/traversing/configure.zcml
> > A
> > zope.traversing/trunk/src/zope/traversing/tests/ftest_zcml_dependencies.zcml
> > A zope.traversing/trunk/src/zope/traversing/tests/test_dependencies.py
> >
> > -=-
> > Modified: zope.traversing/trunk/CHANGES.txt
> > ===
> > --- zope.traversing/trunk/CHANGES.txt 2009-04-02 02:22:07 UTC (rev
> > 98786)
> > +++ zope.traversing/trunk/CHANGES.txt 2009-04-02 06:46:52 UTC (rev
> > 98787)
> > @@ -5,7 +5,7 @@
> > 3.5.4 (unreleased)
> > --
> >
> > -- ...
> > +- Change configure.zcml to not depend on zope.app.component.
> >
> > 3.5.3 (2009-03-10)
> > --
> >
> > Modified: zope.traversing/trunk/src/zope/traversing/configure.zcml
> > ===
> > --- zope.traversing/trunk/src/zope/traversing/configure.zcml
> > 2009-04-02 02:22:07 UTC (rev 98786)
> > +++ zope.traversing/trunk/src/zope/traversing/configure.zcml
> > 2009-04-02 06:46:52 UTC (rev 98787)
> > @@ -16,10 +16,10 @@
> > provides="zope.traversing.interfaces.ITraversable" for="*"
> > factory="zope.traversing.namespace.etc"
> > />
> > - > + > name="etc"
> > -type="zope.interface.Interface"
> > -provides="zope.traversing.interfaces.ITraversable" for="*"
> > +for="* zope.publisher.interfaces.IRequest"
> > +provides="zope.traversing.interfaces.ITraversable"
> > factory="zope.traversing.namespace.etc"
> > />
> > ...
>
> Excellent fix.
*applause*
Incidentally, I've a long-standing wish to be able to register browser
views in ZCML using the adapter directive.
class MyFineView(BrowserPage):
adapts(IMyContentObject, IBrowserRequest)
template = ViewPageTemplateFile('my_fine_view.pt')
def __call__(self):
# update form or whatever
return self.template()
Maybe something to look for in Zope 4?
Marius Gedminas
--
http://pov.lt/ -- Zope 3 consulting and development
signature.asc
Description: Digital signature
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Thu, Apr 02, 2009 at 07:31:00PM +0100, Chris Withers wrote: > So, svn.zope.org causes me pain at the moment: > > - it uses the bizarre svn or svn+ssh protocols, which I find annoying > (ports blocked on routers, can't check with a browser, etc) +10 for continuing to support svn+ssh, it's the best thing ever! * secure (passphrase-protected key) * convenient (ssh-agent means you only type the passphrase once) * convenient to use remotely (ssh agent forwarding means I ssh into a remote server and can use svn without having to store a key or a password anywhere on that remote server) The story may be different for Windows users (as usual). +0.5 for alternatively accepting authenticated https access (I'm not the admin, so it doesn't cost me, but I'm also not going to use it) BTW I've yet to see a firewall that blocks SSH. Am I lucky? > - the web front end is ancient and not as good as other options (Trac, > WebSVN) +1 for having trac as a subversion browser. In fact, see http://zope3.pov.lt/trac The svn repository mirror used by that trac instance is updated with svnsync every 5 minutes. > - the process for adding keys is baroque and managed by one person who > is too busy to help with it (Jim) I would not mind spending some time in a sprint writing a Zope 3 svn key management web app, but that's only a small part of the solution. Authentication and deployment are the other---bigger--two parts. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing.runner: protecting against rogue threads
On Thu, Apr 02, 2009 at 01:30:38PM +0200, Christian Theune wrote: > if tests spawn non-daemon threads, then the test runner can get stuck. > > The easiest way that I see is to always --exit-with-status and to make > --exist-with-status also call sys.exit() when the tests passed. > > Any objections? +99 I would dearly love to have --exit-with-status on by default, for unrelated reasons. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.annotation/trunk/setup.py Whitespace fixes
On Wed, Apr 01, 2009 at 11:44:03PM +0200, Jacob Holm wrote: > If this whitespace fix is based on the current style guide, I think the > guide needs to be fixed. I find the fixed version much less readable. A > function that takes this many arguments should have an exception to the > PEP 8 rule of no whitespace around the equals sign used for keyword > arguments. I *think* a reasonable rule is that if you split the call > over multiple lines with one argument per line, you should add single > spaces before and after the equals sign. What does anyone else think? I don't want to argue about what's right for Zope, but you asked my (well, everone's) opinion about this, so: -1 I think PEP-8 is right, and keyword arguments should not have spaces around the equals sign *especially* if the argument list is long and is split into multiple lines. setup( foo = bar, ) looks like a mistaken assignment of a tuple to a name, while setup( foo=bar, ) looks like a function call. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
On Thu, 2009-04-02 at 20:43 +0200, Martijn Pieters wrote: > On Thu, Apr 2, 2009 at 20:39, Jim Fulton wrote: > > > On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: > >> For me, the ideal would be simply https for everything and using http > >> basic auth for access with more people having access to update the > >> passwd file and maybe Trac or WebSVN for a nice web interface. > > > > I absolutely *hate* using https to access subversion. This involves > > storing a key in plane text in my home directory, which is terrible. > > I far prefer using ssh-based infrastructure for this sort of thing. > > This is no longer the case for subversion 1.6 and up, the password is > now stored encrypted, and subversion now supports KWallet, GNOME > Keyring, Mac OS Keychain, and Windows CryptoAPI for storage. > > See: > http://subversion.tigris.org/svn_1.6_releasenotes.html#auth-related-improvements However, this only *allows* clients to manage their password reasonably, it doesn't force them to. SSH usually complains about bad permission settings on files etc and I guess is usually handled better. (Note: you can't force a passphrase onto the client either.) From my understanding, the interesting part is what the DVCSs do: let people sign their commits with e.g. their PGP key (strong auth) and allow them to share that data somewhere (different mechanism maybe not so strong auth). Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Apr 2, 2009, at 22:53 , Tres Seaver wrote: > +1 to making svn-over-http read-only checkouts work. This is now working. The repository can be reached under... http://svn.zope.org/repos/main/ jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAknVNjQACgkQRAx5nvEhZLLKzACfROrQxGjCo1x90az9/HCMGBk9 JjcAoLAbxTarJVv1+f3jikTGBK1MBlpm =jZ+o -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 22:52 Uhr, Chris Withers wrote: > Andreas Jung wrote: >> We might discuss this unhurriedly. To sleep and being in vacation mood >> in order to discuss this now :-) At least the term 'classic' is a NO-GO >> for me. > > Why? Would you prefer 'a' or maybe 'old'? ;-) > microsite or somewhere else. The point is that the release should remain available under their well-known URL >>> How does moving it all to old.zope.org fit with this requirement? >> >> That was actually my proposal if I wasn't clear enough. > > You were clear that you want both old.zope.org and releases to remain > available under their well-known urls. I don't see how those two > requirements are compatible? You heard of rewrite rules? :-) Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVJoEACgkQCJIWIbr9KYwZ/ACeIDqgsWtPkAUJILc1rMYaWYbr K+kAnjjjL54om11gdukeeb7UDml//XW2 =+lhX -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First, this cross-post was inappropriate: it is a matter for general discussion among Zope committers, which is not a matter for the Foundation to act on unless / until some consensus for changing the status quo emerges. This will be my last post to the 'foundat...@zope.org' list on this thres. Chris Withers wrote: > I got bitten by the current zope subversion setup at PyCon so thought > I'd mail the appropriate groups about it. If this has been covered > elsewhere and I've missed anything, please just point me in the right > direction... > > So, svn.zope.org causes me pain at the moment: > > - it uses the bizarre svn or svn+ssh protocols, which I find annoying > (ports blocked on routers, can't check with a browser, etc) /me shrugs. SSH is an essential part of my day-to-day work: not being able to use it means I'm effectively offline. > - the web front end is ancient and not as good as other options (Trac, > WebSVN) Fixing the web front-end should be a matter for the zope-web list. > - the process for adding keys is baroque and managed by one person who > is too busy to help with it (Jim) *This* part needs some fixing, largely because Jim's role their is an artifact of ZC's role, now lapsed, as custodians. At a minimum, there should be a group (I suggest the zope-web regulars) who can take over the maintenance of that application. A *different* group should have the role of collecting / approving the committer access requests. > So I thought I'd ask what the plans are now that the foundation owns all > the Zope IP (has this happened yet or am I imagining things?) The foundation now owns the copyrights. Trademarks are still in other hands. > Are we sticking with svn? Are we sticking with the current hosting? Are > we sticking with the current key-based login and upload mechanism? > > For me, the ideal would be simply https for everything and using http > basic auth for access with more people having access to update the > passwd file and maybe Trac or WebSVN for a nice web interface. > > I volunteer to help with any/all of the above. > > The other option would be to follow Python and move to Mercurial, but > that has the same problems for me as with Bzr (no decent gui tools, less > mature, etc) although it's a toolset I'll have to learn at some point > anyway... +1 to sticking with svn+ssh for write requests. - -1 to non-pubkey-based authentication for write requests. +1 to making svn-over-http read-only checkouts work. - -1 to switching away from svn, at least until the Python developers have some experience with the transition (I would wait at least 6 months). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ1SXm+gerLs4ltQ4RAt74AJ93TlHe0VZ4vbAI706kDQzT8IvrkACfdzNP HrZb19KJDG+En2Zx+nRjz5c= =kLgg -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
Andreas Jung wrote: > We might discuss this unhurriedly. To sleep and being in vacation mood > in order to discuss this now :-) At least the term 'classic' is a NO-GO > for me. Why? Would you prefer 'a' or maybe 'old'? ;-) >>> microsite or somewhere else. The point is that the release should >>> remain available under their well-known URL >> How does moving it all to old.zope.org fit with this requirement? > > That was actually my proposal if I wasn't clear enough. You were clear that you want both old.zope.org and releases to remain available under their well-known urls. I don't see how those two requirements are compatible? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 22:45 Uhr, Chris Withers wrote: > Andreas Jung wrote: >>> I'd imagine the full set of releases would appear on the respective >>> parts of classic.zope.org or advanced.zope.org... >> >> *shrug* I don't care if those releases on the new zope2.zope.org > > Please not zope2.zope.org, the insane version naming has *got* to stop... We might discuss this unhurriedly. To sleep and being in vacation mood in order to discuss this now :-) At least the term 'classic' is a NO-GO for me. > >> microsite or somewhere else. The point is that the release should >> remain available under their well-known URL > > How does moving it all to old.zope.org fit with this requirement? That was actually my proposal if I wasn't clear enough. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVJR0ACgkQCJIWIbr9KYwg3ACg3rrtvqlQ4lRCpuSa5tbU2Pkp yRYAnRXOfRhkkYwAHY9BNTbu8TnjXREX =UPOq -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
Andreas Jung wrote: >> I'd imagine the full set of releases would appear on the respective >> parts of classic.zope.org or advanced.zope.org... > > *shrug* I don't care if those releases on the new zope2.zope.org Please not zope2.zope.org, the insane version naming has *got* to stop... > microsite or somewhere else. The point is that the release should > remain available under their well-known URL How does moving it all to old.zope.org fit with this requirement? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 22:37 Uhr, Chris Withers wrote: > Andreas Jung wrote: >> >> Because we can't break existing download URL - neither to old Zope >> releases > > I'd imagine the full set of releases would appear on the respective > parts of classic.zope.org or advanced.zope.org... *shrug* I don't care if those releases on the new zope2.zope.org microsite or somewhere else. The point is that the release should remain available under their well-known URL - and I won't work on the migration of the old stuff to a new site in any way :-) > >> nor to old product releases. > > I wonder how many of these are actually safe to use nowadays? > (ie: run without patching and have an active maintainer) > This is not the point. We're playing nice and won't break those links - used or not used . - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVIwIACgkQCJIWIbr9KYzbkgCg4dLwS9jao+ay5E7w700iikMI ZlMAoKQpI4UqJBDF2BjR0Uj+LIStKh+8 =Z4yc -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: [Bug 343079] [NEW] Broken distribution (2009-03-15)]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: > Tres Seaver wrote: >> Chris Withers wrote: >>> Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- I mean an index which supplies the 'simple' PyPI interface, such that we could tell people to 'easy_install' from it, e.g.: $ /path/to/bin/easy_install -i http://kgs.zope.org/Zope2/2.1.2 >>> But how do you then set things up when you want to use other eggs that >>> are only available on PyPI? Surely as soon as you add PyPI as an egg >>> source, things go belly up? >> Personally, I evaluate such eggs in a sandbox, and then add them to the >> project-specific index once I'm sure that they work with the other >> software in the index: I don't use PyPI at all when building out >> production sites. > > That seems overly heavyweight for the average new user. > > "no, sorry, you can't use Zope 2.12 with anything other than what it > comes with unless you get your own egg repository running" Who is talking about an "average new user"? I'm talking about the "my revenue stream depends on this application working" professional (me), and the best practices I use. PyPI is *great* as a tool for discovering new stuff: it sucks as the basis for a repeatable build environment. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ1SLO+gerLs4ltQ4RAln1AJ9+8seP2utgjOS9/McNpGrMmuUPNwCfXyZD ROqI32MHvjjLfqZrVaotr1U= =SdaM -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
Andreas Jung wrote: > > Because we can't break existing download URL - neither to old Zope > releases I'd imagine the full set of releases would appear on the respective parts of classic.zope.org or advanced.zope.org... > nor to old product releases. I wonder how many of these are actually safe to use nowadays? (ie: run without patching and have an active maintainer) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 22:29 Uhr, Chris Withers wrote: > Andreas Jung wrote: >> Andrew & others have been working on this issue at the sprint. There is >> consensus that www.zope.org must be turned into landing page with some >> mission statement and then links to the related subprojects. The current >> zope.org site should be moved to old.zope.org (it must remain >> available for the time being (with URL redirections to the Products >> and Member area). > > Why does it need to keep living even at old.zope.org? > Because we can't break existing download URL - neither to old Zope releases nor to old product releases. - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVIY8ACgkQCJIWIbr9KYyzOwCdGarB1iSUzJeQJ1m1XJvx29yq 6p8An2pgzm1AXhEeBZd+LyBBpPCYtWE7 =aZgz -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope] Zope 4.0, maybe not such a bad idea...
Andrew Milton wrote: > | Indeed, but "classic" doesn't have any "bad" connotations as far as I'm > | concerned, and it'll need to keep living as long as Plone relies on it, > | which will be forever... > > Plenty of people use it without plone. You might want to crawl out of > the vacuum you live in. Yes, and I'm one of them, but I don't think it's fair to try and tempt new users into it... I'm happy to be proven wrong by you writing lots of decent docs, picking up maintenance of zope.org and LocalFS ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope] Zope 4.0, maybe not such a bad idea...
Andrew Milton wrote: > | Why does it need to keep living even at old.zope.org? > > Why do you care if it does? Because someone needs to look after the (rather large, ancient and crufty) zope instance in which it lives, and it keeps on tripping up innocent passers-by. I don't think many of these passers by will be put off by the old.zope.org url and we'll still end up with people wondering why LocalFS doesn't work in Zope Classic 4.0 ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope] Zope 4.0, maybe not such a bad idea...
Andrew Milton wrote: > | - mature > | - stable > | - maybe not the best choice for new development. > ^ for you Indeed, but "classic" doesn't have any "bad" connotations as far as I'm concerned, and it'll need to keep living as long as Plone relies on it, which will be forever... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
Andreas Jung wrote: > Andrew & others have been working on this issue at the sprint. There is > consensus that www.zope.org must be turned into landing page with some > mission statement and then links to the related subprojects. The current > zope.org site should be moved to old.zope.org (it must remain > available for the time being (with URL redirections to the Products > and Member area). Why does it need to keep living even at old.zope.org? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 22:17 Uhr, Chris Withers wrote: > I'd *really* like to see the majority of the current www.zope.org simply > eradicated from existence. It's out of date and a source of nothing but > confusion. > Andrew & others have been working on this issue at the sprint. There is consensus that www.zope.org must be turned into landing page with some mission statement and then links to the related subprojects. The current zope.org site should be moved to old.zope.org (it must remain available for the time being (with URL redirections to the Products and Member area). - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVH9AACgkQCJIWIbr9KYwZJQCgj1m4OH2KLVwxRej6zh2SaUen rMIAoNpVbCIFop0jLO8LFmhHCxeij9ov =O/6m -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
Jim Fulton wrote: > We and canonical use the Zope Framework. We don't use an > application. Zope (aka Zope 2) is an extensible application. We (ZC > and Canonical and others) assemble components from the Zope Framework > to build our own applications. Hmm, maybe I got this wrong, but Gary Poster expressed a strong concern that "zope 3 the app server" needed to keep living. I do think the name "Zope" should never be used on its own again. I think "Zope Classic" would certainly work for "Zope 2 the app server", it conveys the right things: - mature - stable - maybe not the best choice for new development. cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
On Apr 2, 2009, at 4:17 PM, Chris Withers wrote: > Jim Fulton wrote: >>> What Martijn has announced and is already being worked on >>> extensively. >>> >>> - Zope A 4.0 >>> >>> What was to be Zope 2.12 >>> >>> - Zope B 4.0 >>> >>> Whatever the next pending release of the Zope 3 appserver stuff >>> was to >>> be. (Need to keep the Canonical and ZC guys happy afterall ;-) ) >>> >>> www.zope.org could then just be a radically cut down link portal to >>> a.zope.org, b.zope.org and framework.zope.org, which I'd imagine >>> to be >>> brochurewear, download and/or KGS sites for each of the above. >>> >>> I'd suggesting splitting the svn access stuff out to dev.zope.org >>> because it transcends all three. >>> >>> docs.zope.org could hoover up the rest, with any remaining stuff >>> being >>> humanely dispatched. >>> >>> Seriously, how do people feel about this? >> I don't think we need A&B. Maybe just "Zope" and "Zope Framework". > > Unfortunately, as we discovered at the BOF, and what is currently a > significant cause of confusion, is that the "Zope" bit isn't just > one thing, we basically have two app-server projects named Zope > right now: > > - Zope 2 > > Used by Plone, and a few die-hard stragglers and unfortunate > passerby's who get sucked in by the rubbish on www.zope.org > > - Zope 3 > > Use by Canonical for Launchpad and (well, was suspected anyway) by > ZC. I'm sure there are more. We and canonical use the Zope Framework. We don't use an application. Zope (aka Zope 2) is an extensible application. We (ZC and Canonical and others) assemble components from the Zope Framework to build our own applications. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
Jim Fulton wrote: >> What Martijn has announced and is already being worked on extensively. >> >> - Zope A 4.0 >> >> What was to be Zope 2.12 >> >> - Zope B 4.0 >> >> Whatever the next pending release of the Zope 3 appserver stuff was to >> be. (Need to keep the Canonical and ZC guys happy afterall ;-) ) >> >> www.zope.org could then just be a radically cut down link portal to >> a.zope.org, b.zope.org and framework.zope.org, which I'd imagine to be >> brochurewear, download and/or KGS sites for each of the above. >> >> I'd suggesting splitting the svn access stuff out to dev.zope.org >> because it transcends all three. >> >> docs.zope.org could hoover up the rest, with any remaining stuff being >> humanely dispatched. >> >> Seriously, how do people feel about this? > > I don't think we need A&B. Maybe just "Zope" and "Zope Framework". Unfortunately, as we discovered at the BOF, and what is currently a significant cause of confusion, is that the "Zope" bit isn't just one thing, we basically have two app-server projects named Zope right now: - Zope 2 Used by Plone, and a few die-hard stragglers and unfortunate passerby's who get sucked in by the rubbish on www.zope.org - Zope 3 Use by Canonical for Launchpad and (well, was suspected anyway) by ZC. I'm sure there are more. The only sane solution I can think of is to give them both different names (I'm not wedded to A and B, maybe Classic and Advanced?) and let them evolve at their own pace from now on. I suspect their evolution will be glacial compared to things like Repoze.bfg and Grok, which should become the "new user" stories in the Zope world. I'd *really* like to see the majority of the current www.zope.org simply eradicated from existence. It's out of date and a source of nothing but confusion. cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4.0, maybe not such a bad idea...
On Apr 2, 2009, at 3:57 PM, Chris Withers wrote: > Remember this: > > http://www.perl.com/pub/a/2001/04/01/parrot.htm > > Well, that lead to this: > > http://www.parrot.org/ > > One of the reasons I got suckered into replying was that I thought > this > might be the result of some stuff a few of us had talked about at the > Zope BOF at PyCon. > > I actually think having a 4.0 release of Zope that unifies things > could > be used to make things a lot clearer... > > - Zope Framework 4.0 > > What Martijn has announced and is already being worked on extensively. > > - Zope A 4.0 > > What was to be Zope 2.12 > > - Zope B 4.0 > > Whatever the next pending release of the Zope 3 appserver stuff was to > be. (Need to keep the Canonical and ZC guys happy afterall ;-) ) > > www.zope.org could then just be a radically cut down link portal to > a.zope.org, b.zope.org and framework.zope.org, which I'd imagine to be > brochurewear, download and/or KGS sites for each of the above. > > I'd suggesting splitting the svn access stuff out to dev.zope.org > because it transcends all three. > > docs.zope.org could hoover up the rest, with any remaining stuff being > humanely dispatched. > > Seriously, how do people feel about this? I don't think we need A&B. Maybe just "Zope" and "Zope Framework". I like the idea of using a number larger than 3. (I've suggested 5 in the past.) Overall +1. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
Martijn Pieters schrieb: > On Thu, Apr 2, 2009 at 20:31, Chris Withers wrote: >> For me, the ideal would be simply https for everything and using http >> basic auth for access with more people having access to update the >> passwd file and maybe Trac or WebSVN for a nice web interface. >> >> I volunteer to help with any/all of the above. > > My offer to set up Trac as a buildout still stands too. > > Jens, have your concerns about dependencies been answered? > I also offer my help to install and maintain a trac and, if needed, the svn installation. ..Carsten ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope] Zope 4.0, maybe not such a bad idea...
Andrew Milton wrote: > +---[ Chris Withers ]-- > | Remember this: > > | Seriously, how do people feel about this? > > You can do anything you want with your time... who are we to judge? d8) Well, if there were no complaints I might do just that... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 21:58 Uhr, Chris Withers wrote: > Dieter Maurer wrote: >> I have been told that there are mirrors of the Zope SVN repository >> providing read access via "http". > > Shame none of them is advertised anywhere... http://svn.zope.de - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVGgYACgkQCJIWIbr9KYye6ACfXPCLs+nZPOKbupSZ3aJ0nWtT Pz0Ani9kEtzGwaxyoixsGFkdWOWbkhnB =fvsT -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Dieter Maurer wrote: > > I have been told that there are mirrors of the Zope SVN repository > providing read access via "http". Shame none of them is advertised anywhere... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope 4.0, maybe not such a bad idea...
Remember this: http://www.perl.com/pub/a/2001/04/01/parrot.htm Well, that lead to this: http://www.parrot.org/ One of the reasons I got suckered into replying was that I thought this might be the result of some stuff a few of us had talked about at the Zope BOF at PyCon. I actually think having a 4.0 release of Zope that unifies things could be used to make things a lot clearer... - Zope Framework 4.0 What Martijn has announced and is already being worked on extensively. - Zope A 4.0 What was to be Zope 2.12 - Zope B 4.0 Whatever the next pending release of the Zope 3 appserver stuff was to be. (Need to keep the Canonical and ZC guys happy afterall ;-) ) www.zope.org could then just be a radically cut down link portal to a.zope.org, b.zope.org and framework.zope.org, which I'd imagine to be brochurewear, download and/or KGS sites for each of the above. I'd suggesting splitting the svn access stuff out to dev.zope.org because it transcends all three. docs.zope.org could hoover up the rest, with any remaining stuff being humanely dispatched. Seriously, how do people feel about this? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Jacob Holm wrote at 2009-4-2 20:44 +0200: > ... >For write access I completely agree. For read-only unauthenticated >access it would be nice to be able to use http(s). It may be possible to >have it all at the same time. I have been told that there are mirrors of the Zope SVN repository providing read access via "http". -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Dieter Maurer wrote: > I would not like to enter my password every time I call "svn". > If this can be arranged, I am content. It can, and with svn 1.6 it's even secure :-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Chris Withers wrote at 2009-4-2 19:44 +0100: > ... >I prefer using password-protected (as opposed to key-protected) https. >What do other people prefer? I am fine with the "ssh" access. True, the initial setup was a bit difficult (the key program did not like the "." in "d.maurer" -- but forgot to tell so) but Jim spare enough time to help me overcome the problem. After I changed my username from "d.maurer" to "dmaurer", everything worked immediately. I would not like to enter my password every time I call "svn". If this can be arranged, I am content. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] setting missing minimum version in setup.py
Martijn Faassen wrote: > KGS is two things: > > * KGS the software > > * KGS the concept > > KGS the concept will have a life outside of the Zope world. I stand by my predication that even the KGS concept will never make it beyond Zope... > KGS the > concept is very easy to implement; you just make available on some URL a > buildout versions.cfg, or you run your own package index. OK, the former I can see happening on an end-user project, the latter is just too much work. > I'll note that buildout seems to be clawing to a life outside of the > Zope world; I know of several Django users that adopted it. It'd be much > more popular if we had a good bunch of beginner level tutorials for it. I promised to deliver this, and will do as soon as I get to that point in my work stack... > Anyway, we've already decided to use setup.py dependencies for API > compatibility. That's the best you're going to get out of us for a while. Good :-) Chris (although it's sad to note that Zope 2.12 can't be made to work without a KGS-like list :-/) -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] setting missing minimum version in setup.py
Roger Ineichen wrote: > Probably a way to go is to make both concept compatible with > each other. Which probably means we should be able to ignore > versions in packages if a KGS concept get used? > (not sure if this is possible) NO! This is INSANE! The version requirements in a package should be met by a KGS, it's just that they might be more rigid in a KGS... eg: KGS: foo.bar==1.7.1 In a package that depends on foo.bar: foo.bar >= 1.6 cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] setting missing minimum version in setup.py
Wichert Akkerman wrote: >> Are there other Python projects that have to deal with such a huge >> amount of packages and dependencies? I don't know any similar project. >> So the solution must come from the Zope world (which does not mean that >> we participate in the packaging toolchain development as Tarek does). > > I don't know. I just feel quite strongly that improving the packaging > tools would be a better use of manpower than working on the KGS in its > current form. Then dive in and help: - distutils-sig - catalog-sig - python-core :-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: [Bug 343079] [NEW] Broken distribution (2009-03-15)]
Tres Seaver wrote: > Chris Withers wrote: >> Tres Seaver wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> I mean an index which supplies the 'simple' PyPI interface, such that we >>> could tell people to 'easy_install' from it, e.g.: >>> >>> $ /path/to/bin/easy_install -i http://kgs.zope.org/Zope2/2.1.2 >> But how do you then set things up when you want to use other eggs that >> are only available on PyPI? Surely as soon as you add PyPI as an egg >> source, things go belly up? > > Personally, I evaluate such eggs in a sandbox, and then add them to the > project-specific index once I'm sure that they work with the other > software in the index: I don't use PyPI at all when building out > production sites. That seems overly heavyweight for the average new user. "no, sorry, you can't use Zope 2.12 with anything other than what it comes with unless you get your own egg repository running" :-S Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
Tres Seaver wrote: >> Possibly because I am using SVN 1.6. > > Then "never" means since 2009-03-20. Or else you have never done a > checkout from a password-protected SVN-over-HTTP(S) server. It's been encrypted on Windows for longer than that... (svn 1.4...) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing.runner: protecting against rogue threads
Christian Theune wrote at 2009-4-2 13:30 +0200: >if tests spawn non-daemon threads, then the test runner can get stuck. > >The easiest way that I see is to always --exit-with-status and to make >--exist-with-status also call sys.exit() when the tests passed. I do not understand the implication. Do you plan that any test runs in a separate process? Then, I would have an objection -- test suites would take far longer. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: > On 02.04.2009 20:44 Uhr, Andreas Jung wrote: >> On 02.04.2009 20:39 Uhr, Jim Fulton wrote: >>> On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. >>> I absolutely *hate* using https to access subversion. This involves >>> storing a key in plane text in my home directory, which is terrible. >>> I far prefer using ssh-based infrastructure for this sort of thing. > >> Really? I have never stored a plain text password for SVN over https >> within my home dir. I also can not find anything related within >> .subversion/ in my home dir. > > > Possibly because I am using SVN 1.6. Then "never" means since 2009-03-20. Or else you have never done a checkout from a password-protected SVN-over-HTTP(S) server. Tres, - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ1QqA+gerLs4ltQ4RAqp3AKCOse88Q5aHlgI3tZguCFveN+Uc7wCgqRB2 tbMxeMww1fYarBzC+1k01Eo= =cj6O -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Jim Fulton wrote: > > On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: >> For me, the ideal would be simply https for everything and using http >> basic auth for access with more people having access to update the >> passwd file and maybe Trac or WebSVN for a nice web interface. > > > I absolutely *hate* using https to access subversion. Well, I absolutely *hate* using ssh to access subversion. > This involves > storing a key in plane text in my home directory, which is terrible. How do you not have the same thing with ssh? Myself, I work from a variety of machines on a variety of different platforms, and trying to juggle multiple public keys with undocumented and unsupported upload facilities is painful. The alternative is to try and juggle one public key across multiple machines and ssh implementations which is just as painful, not to mention insecure. > I > far prefer using ssh-based infrastructure for this sort of thing. I prefer using password-protected (as opposed to key-protected) https. What do other people prefer? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 2:44 PM, Chris Withers wrote: >> This involves storing a key in plane text in my home directory, >> which is terrible. > > How do you not have the same thing with ssh? ssh keys are pass-phrase protected and ssh-agent allows me to enter the pass phrase once in a session. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 20:44 Uhr, Andreas Jung wrote: > On 02.04.2009 20:39 Uhr, Jim Fulton wrote: >> On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: >>> For me, the ideal would be simply https for everything and using http >>> basic auth for access with more people having access to update the >>> passwd file and maybe Trac or WebSVN for a nice web interface. > >> I absolutely *hate* using https to access subversion. This involves >> storing a key in plane text in my home directory, which is terrible. >> I far prefer using ssh-based infrastructure for this sort of thing. > > > Really? I have never stored a plain text password for SVN over https > within my home dir. I also can not find anything related within > .subversion/ in my home dir. > Possibly because I am using SVN 1.6. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVCFkACgkQCJIWIbr9KYzIFgCgnUMYfD6ed/Lrro1Kqa5lHyr7 47YAn1pkzCaXk4PrxjLmxAooav7JM0wl =N9xl -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 20:39 Uhr, Jim Fulton wrote: > On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: >> For me, the ideal would be simply https for everything and using http >> basic auth for access with more people having access to update the >> passwd file and maybe Trac or WebSVN for a nice web interface. > > > I absolutely *hate* using https to access subversion. This involves > storing a key in plane text in my home directory, which is terrible. > I far prefer using ssh-based infrastructure for this sort of thing. > > Really? I have never stored a plain text password for SVN over https within my home dir. I also can not find anything related within .subversion/ in my home dir. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVB6MACgkQCJIWIbr9KYy/OwCgvp2OPXzv/VFF2N09/fza6092 wiAAnRujl2mx2SRiviWclhWfnpDpiCqQ =xYXr -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Jim Fulton wrote: > On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: > >> For me, the ideal would be simply https for everything and using http >> basic auth for access with more people having access to update the >> passwd file and maybe Trac or WebSVN for a nice web interface. >> > > > I absolutely *hate* using https to access subversion. This involves > storing a key in plane text in my home directory, which is terrible. > I far prefer using ssh-based infrastructure for this sort of thing. > > For write access I completely agree. For read-only unauthenticated access it would be nice to be able to use http(s). It may be possible to have it all at the same time. - Jacob ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
On Thu, Apr 2, 2009 at 20:39, Jim Fulton wrote: > On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: >> For me, the ideal would be simply https for everything and using http >> basic auth for access with more people having access to update the >> passwd file and maybe Trac or WebSVN for a nice web interface. > > I absolutely *hate* using https to access subversion. This involves > storing a key in plane text in my home directory, which is terrible. > I far prefer using ssh-based infrastructure for this sort of thing. This is no longer the case for subversion 1.6 and up, the password is now stored encrypted, and subversion now supports KWallet, GNOME Keyring, Mac OS Keychain, and Windows CryptoAPI for storage. See: http://subversion.tigris.org/svn_1.6_releasenotes.html#auth-related-improvements -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: > For me, the ideal would be simply https for everything and using http > basic auth for access with more people having access to update the > passwd file and maybe Trac or WebSVN for a nice web interface. I absolutely *hate* using https to access subversion. This involves storing a key in plane text in my home directory, which is terrible. I far prefer using ssh-based infrastructure for this sort of thing. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ZF] Zope Source Code Repository
On Thu, Apr 2, 2009 at 20:31, Chris Withers wrote: > For me, the ideal would be simply https for everything and using http > basic auth for access with more people having access to update the > passwd file and maybe Trac or WebSVN for a nice web interface. > > I volunteer to help with any/all of the above. My offer to set up Trac as a buildout still stands too. Jens, have your concerns about dependencies been answered? -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Source Code Repository
Hey All, I got bitten by the current zope subversion setup at PyCon so thought I'd mail the appropriate groups about it. If this has been covered elsewhere and I've missed anything, please just point me in the right direction... So, svn.zope.org causes me pain at the moment: - it uses the bizarre svn or svn+ssh protocols, which I find annoying (ports blocked on routers, can't check with a browser, etc) - the web front end is ancient and not as good as other options (Trac, WebSVN) - the process for adding keys is baroque and managed by one person who is too busy to help with it (Jim) So I thought I'd ask what the plans are now that the foundation owns all the Zope IP (has this happened yet or am I imagining things?) Are we sticking with svn? Are we sticking with the current hosting? Are we sticking with the current key-based login and upload mechanism? For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. I volunteer to help with any/all of the above. The other option would be to follow Python and move to Mercurial, but that has the same problems for me as with Bzr (no decent gui tools, less mature, etc) although it's a toolset I'll have to learn at some point anyway... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: zope.traversing/trunk/ zcml now only depends on zope.component meta, not zope.app.component
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: > Log message for revision 98787: > zcml now only depends on zope.component meta, not zope.app.component > > Changed: > U zope.traversing/trunk/CHANGES.txt > U zope.traversing/trunk/src/zope/traversing/configure.zcml > A > zope.traversing/trunk/src/zope/traversing/tests/ftest_zcml_dependencies.zcml > A zope.traversing/trunk/src/zope/traversing/tests/test_dependencies.py > > -=- > Modified: zope.traversing/trunk/CHANGES.txt > === > --- zope.traversing/trunk/CHANGES.txt 2009-04-02 02:22:07 UTC (rev 98786) > +++ zope.traversing/trunk/CHANGES.txt 2009-04-02 06:46:52 UTC (rev 98787) > @@ -5,7 +5,7 @@ > 3.5.4 (unreleased) > -- > > -- ... > +- Change configure.zcml to not depend on zope.app.component. > > 3.5.3 (2009-03-10) > -- > > Modified: zope.traversing/trunk/src/zope/traversing/configure.zcml > === > --- zope.traversing/trunk/src/zope/traversing/configure.zcml 2009-04-02 > 02:22:07 UTC (rev 98786) > +++ zope.traversing/trunk/src/zope/traversing/configure.zcml 2009-04-02 > 06:46:52 UTC (rev 98787) > @@ -16,10 +16,10 @@ > provides="zope.traversing.interfaces.ITraversable" for="*" > factory="zope.traversing.namespace.etc" > /> > - + name="etc" > -type="zope.interface.Interface" > -provides="zope.traversing.interfaces.ITraversable" for="*" > +for="* zope.publisher.interfaces.IRequest" > +provides="zope.traversing.interfaces.ITraversable" > factory="zope.traversing.namespace.etc" > /> > ... Excellent fix. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ1PEi+gerLs4ltQ4RAo7yAKCG3khpLFSM3pB/4GhtgaCVow/63wCgsHKF QooMuQx3Htwl6K0hBFr12vU= =o9k5 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.annotation/trunk/setup.py Whitespace fixes
On Apr 1, 2009, at 5:44 PM, Jacob Holm wrote: > If this whitespace fix is based on the current style guide, I think so. > I think the > guide needs to be fixed. Me too, but I don't think it will happen. :( > I find the fixed version much less readable. A > function that takes this many arguments should have an exception to > the > PEP 8 rule of no whitespace around the equals sign used for keyword > arguments. I *think* a reasonable rule is that if you split the call > over multiple lines with one argument per line, you should add single > spaces before and after the equals sign. What does anyone else think? I agree, but the style guide says differently. In a previous thread, however, there seems to have been agreement that discussions of style were religious and meaningless, so I suggest ignoring the style guide. <0.32 wink> I would rather people not change things like this when making unrelated changes. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two small convenience suggestions for zope.interface and zope.component
On Wed, Apr 1, 2009 at 12:25, Chris Rossi wrote: > Additionally, if I was grokking Lennart correctly yesterday, > __metaclass__ is going away, so the current metaclass implementation > is going to need some rejiggering. What was unclear was whether a > single implementation could support both <=2.5 and >=2.6. 2.5 doesn't support class decorators, so no. But the plan is that both implements(IFoo) and @implementor(IFoo) will be available under 2.6. -- Lennart Regebro: Pythonista, Barista, Notsotrista. http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two small convenience suggestions for zope.interface and zope.component
2009/4/1 Marius Gedminas : > I now also wonder if adapter()/implementer() would work when called with > classes rather than functions...? Yes, in 2.6 and 3.0. Not with the current trunk of zope.interfaces, though, but in the future, sure. -- Lennart Regebro: Pythonista, Barista, Notsotrista. http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.annotation/trunk/setup.py Whitespace fixes
On Thu, Apr 2, 2009 at 9:37 AM, Zvezdan Petkovic wrote: > This would be more consistent, is sorted, and ensures easy addition/ > removal of each line including the first, and the last line in the > lists. > > install_requires=[ > 'setuptools', > 'zope.component', > 'zope.interface', > 'zope.location', > 'zope.proxy', > ], > extras_require=dict( > test=[ > 'ZODB3', > 'zope.testing', > ], > ), +1 -- Benji York Senior Software Engineer Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.annotation/trunk/setup.py Whitespace fixes
On Apr 1, 2009, at 5:44 PM, Jacob Holm wrote: > If this whitespace fix is based on the current style guide, I think > the guide needs to be fixed. I find the fixed version much less > readable. A function that takes this many arguments should have an > exception to the PEP 8 rule of no whitespace around the equals sign > used for keyword arguments. I *think* a reasonable rule is that if > you split the call over multiple lines with one argument per line, > you should add single spaces before and after the equals sign. What > does anyone else think? -1 The PEP-8 and Zope style for keyword arguments work here just fine. Readability is improved by putting arguments on separate lines, not by adding space around equal sign. Additionally, we could do without fancy spacing. For example, the lists don't have a consistent style in this patch. One avoids fancy spacing ... >> +classifiers=[ >> 'Development Status :: 5 - Production/Stable', >> 'Intended Audience :: Developers', >> 'License :: OSI Approved :: Zope Public License', >> @@ -40,23 +40,23 @@ >> 'Topic :: Internet :: WWW/HTTP', >> 'Topic :: Software Development', >> ], The other two use fancy spacing, are not alphabetically sorted, and do not have consistent rule on commas after the last element ... >> +install_requires=['setuptools', >> + 'zope.interface', >> + 'zope.component', >> + 'zope.location', >> + 'zope.proxy', >> + ], >> +extras_require=dict( >> +test=['zope.testing', >> + 'ZODB3'], >> ), This would be more consistent, is sorted, and ensures easy addition/ removal of each line including the first, and the last line in the lists. install_requires=[ 'setuptools', 'zope.component', 'zope.interface', 'zope.location', 'zope.proxy', ], extras_require=dict( test=[ 'ZODB3', 'zope.testing', ], ), ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing.runner: protecting against rogue threads
On Thu, 2009-04-02 at 13:30 +0200, Christian Theune wrote: > Hi, > > if tests spawn non-daemon threads, then the test runner can get stuck. > > The easiest way that I see is to always --exit-with-status and to make > --exist-with-status also call sys.exit() when the tests passed. > > Any objections? I forgot an alternative solution: Make the test runner patch the Thread class to turn all threads into daemons during testing. -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.testing.runner: protecting against rogue threads
Hi, if tests spawn non-daemon threads, then the test runner can get stuck. The easiest way that I see is to always --exit-with-status and to make --exist-with-status also call sys.exit() when the tests passed. Any objections? Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.annotation/trunk/setup.py Whitespace fixes
Michael Howitz wrote: > Am 01.04.2009 um 23:44 schrieb Jacob Holm: > >> Hi Baiju >> >> If this whitespace fix is based on the current style guide, I think the >> guide needs to be fixed. I find the fixed version much less readable. A >> function that takes this many arguments should have an exception to the >> PEP 8 rule of no whitespace around the equals sign used for keyword >> arguments. I *think* a reasonable rule is that if you split the call >> over multiple lines with one argument per line, you should add single >> spaces before and after the equals sign. What does anyone else think? > > What about defining the version number in front of the setup call as a > variable and using it in the call like: > > version = '3.5.0dev' > > setup( > name='zope.annotation', > version=version, > ... > ) > > This way no exception from the rule is necessary. I like the idea of putting the version string up front like that, but that was not what I meant. I was not complaining about the "version" keyword argument specifically, but about the removal of whitespace for *all* the keyword arguments to setup. Cheers - Jacob ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.annotation/trunk/setup.py Whitespace fixes
Am 01.04.2009 um 23:44 schrieb Jacob Holm: > Hi Baiju > > If this whitespace fix is based on the current style guide, I think > the > guide needs to be fixed. I find the fixed version much less > readable. A > function that takes this many arguments should have an exception to > the > PEP 8 rule of no whitespace around the equals sign used for keyword > arguments. I *think* a reasonable rule is that if you split the call > over multiple lines with one argument per line, you should add single > spaces before and after the equals sign. What does anyone else think? What about defining the version number in front of the setup call as a variable and using it in the call like: version = '3.5.0dev' setup( name='zope.annotation', version=version, ... ) This way no exception from the rule is necessary. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
