Re: [Zope-dev] PyPI mirrors available
2008/11/13 Andreas Jung <[EMAIL PROTECTED]> > Hi there, > > I would like to point out that we have started the PyPI replication project > some months ago during the Blackforest sprint: > > http://www.openplans.org/projects/pypi-mirroring/project-home > > As an outcome we are now able to provide in phase one of the project some > mirrors of PyPI index. Currently we have three mirrors up and running and > some more mirrors will join the project soon. Right now we provide all > packages of PyPI that are directly hosted on PyPI (no packages with external > download URLs). This project should bring a lot of ease to buildout users > because PyPI is no longer a single-point-of-failure. Currently you have to > choose a PyPI mirror manually. For the next project phase we think about a > smarter mirror selection mechanism that is more transparent to setuptools > and zc.buildout. > > Suggestions and further support in terms of hardware resources and > bandwidth are highly appreciated. > > Credits go to Josip Delic and Gottfried Ganssauge of Haufe Mediengruppe for > their contributions to the original codebase of z3c.pypimirror and to > Daniel Kraft of D9T for being doing most of the coding of the package. Congrats to all! -- Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051 ___ 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] PyPI mirrors available
Hi there, I would like to point out that we have started the PyPI replication project some months ago during the Blackforest sprint: http://www.openplans.org/projects/pypi-mirroring/project-home As an outcome we are now able to provide in phase one of the project some mirrors of PyPI index. Currently we have three mirrors up and running and some more mirrors will join the project soon. Right now we provide all packages of PyPI that are directly hosted on PyPI (no packages with external download URLs). This project should bring a lot of ease to buildout users because PyPI is no longer a single-point-of-failure. Currently you have to choose a PyPI mirror manually. For the next project phase we think about a smarter mirror selection mechanism that is more transparent to setuptools and zc.buildout. Suggestions and further support in terms of hardware resources and bandwidth are highly appreciated. Credits go to Josip Delic and Gottfried Ganssauge of Haufe Mediengruppe for their contributions to the original codebase of z3c.pypimirror and to Daniel Kraft of D9T for being doing most of the coding of the package. Andreas -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope & Plone development, Consulting 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:[EMAIL PROTECTED] 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] Subversion merge tracking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: > On Thu, Nov 13, 2008 at 2:28 PM, Tres Seaver <[EMAIL PROTECTED]> wrote: >> +0, I guess: I would be more comfortable if we could measure the >> incidence of pre-1.5 client usage over time, and maybe even identify the >> committers who are using them, so that we can sent out a targeted >> warning message before breaking their checkouts. > > Checkouts are not a problem, only checkins. I'm talking about users who have *existing* checkouts on a pre-1.5 machine. If they are make a commits from there, during the deprecation period, we should collect that information, so that we can notify them before breaking their ability to make further commits. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] 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 iD8DBQFJHFoi+gerLs4ltQ4RAkWcAJ97an0p0FjwGG2SuMLjIxVNw0FMBwCgsgOM cQvNBSRv2YPTIlVIBSyIihk= =8+my -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] Subversion merge tracking
On Thu, Nov 13, 2008 at 2:28 PM, Tres Seaver <[EMAIL PROTECTED]> wrote: > +0, I guess: I would be more comfortable if we could measure the > incidence of pre-1.5 client usage over time, and maybe even identify the > committers who are using them, so that we can sent out a targeted > warning message before breaking their checkouts. Checkouts are not a problem, only checkins. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 Skype zopedc ___ 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] Subversion merge tracking
On 13.11.2008 14:42 Uhr, Benji York wrote: I'd like for us to disallow pre-1.5 Subversion clients from making commits starting one year from now (or sooner if there is consensus). +1 - six months should be enough for the transition. Andreas 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:[EMAIL PROTECTED] 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] Subversion merge tracking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benji York wrote: > I'd like for us to disallow pre-1.5 Subversion clients from making > commits starting one year from now (or sooner if there is consensus). > > The recent hardware problems for svn.zope.org had the positive outcome > of precipitating an upgrade to Subversion 1.5 which has merge tracking. > One of the requirements to use merge tracking is that no pre-1.5 client > merge to the branch that you want to use with merge tracking. > > That means that as of now, anyone can use merge tracking on their > projects as long as all merges are done with a mergeinfo-capable (1.5+) > client. > > Until we ban commits from pre-1.5 clients (using a pre-commit hook), > anyone who wants to use merge tracking will have to be careful with the > clients they use (and watch out for rouge merges from other contributors > which can be fixed-up after the fact). > > The Subversion book includes information about merge tracking: > http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html > http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html > > A description of the pre-1.5 client problem is at > http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.pre1.5clients +0, I guess: I would be more comfortable if we could measure the incidence of pre-1.5 client usage over time, and maybe even identify the committers who are using them, so that we can sent out a targeted warning message before breaking their checkouts. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] 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 iD8DBQFJHFWo+gerLs4ltQ4RAlDWAJ4mhFz6683K5eLs3T061ejSCaiIQACghWmn OQjtYqIrO3TXnn5SsrjhrL4= =Bncy -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] Subversion merge tracking
On Thu, Nov 13, 2008 at 1:09 PM, Jens Vagelpohl <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > On Nov 13, 2008, at 14:42 , Benji York wrote: > >> I'd like for us to disallow pre-1.5 Subversion clients from making >> commits starting one year from now (or sooner if there is consensus). > > +1 I vote for sooner, if that makes things easier. I'm already using 1.5 and I'm on Windows, so I guess the Linux users out there shouldn't have a problem getting an up-to-date package right? :) -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 Skype zopedc ___ 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] Request for comments: Devilstick persistence/storage
I would like to request comments on our idea how to use different storages for our new model-driven approch with the name Devilstick. You dont need to know devilstick or its ideas in depth to give valuable input. More it would helps us to get input from people knowing zopes persistency layer in depth. Devilstick is model driven framework to describe and manage data inside and outside ZODB. some more information at http://devilstickproject.net At Blackforest sprint in august we researched how the goal to support different storages than ZODB can be achieved. After first thinking about an own layer we got there the idea of using the usal persistence and transaction API of zope. IIRC it was a result of a conversation between Florian Friesdorf and Roger Ineichen and probably others. Today is the last day of Bolzano sprint. We researched a lot how it currently works with ZODB and discussed about how to use all this framework for devilstick. Our outcome is a document describing what we found and how we want to use all this. It follows here. for the devilstick-team Jens Klein = --- Introduction to Devilstick Storages --- This document describes the future. One of Devilsticks power is to support different storages than ZODB easily. The storage layer uses 100% zopes persistency implementation. At some entry point we enter the model driven world of devilstick: We hit 'Cage'. The Cage itself is not a data-access-object (DAO). But its the bridge to the otherstorage layer. Inside Devilstick DAOs are still persistent objects. They may still live in ZODB. But they can live complete outside if it is needed. They may live in SQL-databases, in LDAP, filesystem or fetched over a webservice. For more about DAOs and its API please read API.txt. Excursus: Zopes Persistence Framework - Classic zope objects are derived from 'persistence.Persistent'. Those objects are tracking themselfes for modifications. Once a modification is detected it joins it's data-manager to the current transaction-manager. All this happens in zope fully transparent. The data-manager is the key to the storage layer. Zope is designed to use different data-managers. Datamanagers are described well in 'transaction.interfaces.IDataManager'. They care about storing all data in a 2-phase commit. There is usally one data-manager for all modified object of one database. Transaction-manager collects all datamanagers (which are called resources inside the transaction-manager) with modifications. Once the transaction is committed the 2-phase commit is started: 1st 'tpc_begin' is called on each data-manager, 2nd the 'commit' is called for each, then 'tpc_vote' and finally 'tpc_finish'. After creation of a persistent object it has an attribute called '_p_jar' set to 'None'. _p_jar gets a datamanager set - almost magically - after it was added to a container. The datamanager taken there is copied over from the containers _p_jar attribute. Container and new object are marked as modifed and the datamanager joins the transaction. On commit both are written to the database. Devilstick persistency -- To provide other storages we alreay have a powerful framework: the persistent api and transaction api. Devilstick uses both. To use a different storage simply a new data-manager is needed. Anyway, for several uses-cases its fine to stay in the ZODB. Such a alternative datamanager might work different inside than the current ZODB one. Since we deal with SQL or LDAP we want to update a database with one query for several objects involved. So on commit we may need to look at the modified objects and build one sql-query from a bunch of modifications. Frameworks like SQLAlchemy may help us here for SQL and others are probably available for different use-cases. Entry-Points: Cages --- We need one point where the datamanager is switched to a different storage.A model is assigned and there the world of generic DAOs is entered. This entry point is called 'Cage'. A cage is still persistent in the ZODB and uses the zopes default data-manager. A cage has the root container DAO (which is a generic molecule DAO) set as an attribute. Here some example code how it looks like: >>> cage = Cage() >>> cage._p_jar None >>> somezodbcontainer._p_jar >>> somezodbcontainer['data'] = cage >>> cage._p_jar >>> cage._root None >>> cage.model = 'examplemodel' >>> cage._root >>> cage._root._p_jar The cage also bridges the container API of the root molecule. It simplifies the usage of the API and avoids to introduce a extra access step on the cage. This way its more intuitive. >>> cage._root.keys() ['m1', 'm2', 'm
Re: [Zope-dev] Subversion merge tracking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 13, 2008, at 14:42 , Benji York wrote: > I'd like for us to disallow pre-1.5 Subversion clients from making > commits starting one year from now (or sooner if there is consensus). +1 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkkcQx4ACgkQRAx5nvEhZLKugACfUMq7DHVTzRNdF61grqsIzFdd xqoAnRe5LpwZfh5JoD08z5Sj/SrOh0Ep =Zf2H -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] deprecate http://download.zope.org/distribution
On Wed, 2008-11-12 at 17:41 -0500, Jim Fulton wrote: > http://download.zope.org/distribution was set up as a place to publish > distributions while we were learning about setuptools, eggs, and > pypi. I think now, we're all using PyPI (or local repositories). I'd > like to deprecate this site, making it read-only for now, but > eventually removing it. +1 -- Christian Theune · [EMAIL PROTECTED] 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] Subversion merge tracking
I'd like for us to disallow pre-1.5 Subversion clients from making commits starting one year from now (or sooner if there is consensus). The recent hardware problems for svn.zope.org had the positive outcome of precipitating an upgrade to Subversion 1.5 which has merge tracking. One of the requirements to use merge tracking is that no pre-1.5 client merge to the branch that you want to use with merge tracking. That means that as of now, anyone can use merge tracking on their projects as long as all merges are done with a mergeinfo-capable (1.5+) client. Until we ban commits from pre-1.5 clients (using a pre-commit hook), anyone who wants to use merge tracking will have to be careful with the clients they use (and watch out for rouge merges from other contributors which can be fixed-up after the fact). The Subversion book includes information about merge tracking: http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html A description of the pre-1.5 client problem is at http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.pre1.5clients -- 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 )
[Zope-dev] Zope Tests: 4 OK, 2 Failed
Summary of messages to the zope-tests list. Period Wed Nov 12 12:00:00 2008 UTC to Thu Nov 13 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures - Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:39:40 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010476.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Wed Nov 12 20:41:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010477.html Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Nov 12 20:33:39 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010472.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:35:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010473.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:36:40 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010474.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:38:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010475.html ___ 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 )
