Re: [Zope-dev] ohloh listings
From that same page: """ Please do not simply delete and re-add the enlistment. In most cases this does not have any effect (our system will recognize the URL and simply re-add the existing broken download), and it will complicate our debugging efforts. """ On Sat, Sep 10, 2011 at 6:32 PM, Chris McDonough wrote: > Hanno, > > Could you delete and readd the failed repository enlistments at > https://www.ohloh.net/p/zope/enlistments?page=13 > > I think these are them: > > svn://svn.zope.org/repos/main/zope.schema/trunk > svn://svn.zope.org/repos/main/zope.security/trunk > > They're preventing Zope stats on ohloh from getting updated regularly, I > think. > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] ztk on pypy?
There's a pypy sprint going on in Switzerland next week: http://codespeak.net/svn/pypy/extradoc/sprintinfo/leysin-winter-2011/announcement.txt Just wondering if anyone has plans to attend it and push some ztk on pypy goodness. I would gladly go, but personal issues prevent me from doing so. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] lxml dependency in Zope 2.12.10 KGS
On Fri, Sep 10, 2010 at 8:45 AM, Martin Aspeli wrote: > Hi, > > The Zope 2.12.10 KGS at > http://download.zope.org/Zope2/index/2.12.10/versions.cfg specifies > > lxml = 2.2.6 > > There is no Python 2.6 Windows build for this egg, which means that this > version cannot be installed on Windows under Python 2.6. Version 2.2.4 is > the latest version with safe binary eggs for all platforms. > > What in Zope depends on lxml? Why did we pin to 2.2.6? Eggs for lxml 2.2.8 have been uploaded for Python 2.6, 2.7 and 3.1, for 32 and 64 bits Windows. Enjoy. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] .lock files on Windows
On Fri, Sep 3, 2010 at 1:16 PM, Jim Pharis wrote: > https://bugs.launchpad.net/collective.buildout/+bug/596839 > > Killing a fg instance with ctrl-c isn't the only scenario where the lock and > pid files don't get cleaned up. I thought the problem was only the .pid file, not the .lock. Can you confirm? The .lock file should go away if the process dies in any way, but the .pid file seems to only be deleted on clean shutdown. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] RFC: ETag support for zope.browserresource
On Tue, Aug 10, 2010 at 12:42 PM, Marius Gedminas wrote: > How would you like that to be configured? > > Option #1: > > ? > > Option #2: > > getMultiAdapter((resource, request), IETag).computeETag() ? > > This is maybe a bit problematic, because the actual File object that > contains all the data--such as filename--doesn't implement any > interfaces. And neither does FileResource. > So maybe Option #1? >> I see that your implementation uses last-modified + size, which should >> generally be fine. However if you're load-balancing across two >> different servers and the timestamps don't match then the ETag is >> useless. > > Would you prefer a sha1 checksum? As a default? I'd say last-modified + size is OK. >> On a completely different note, I see that the File object reads the >> whole file into memory. > > And it does that twice for every request that results in a 200 response: > once to auto-detect the content-type, the second time to return the > actual data. Ouch. That sounds pretty bad. I thought it kept the data in-memory (didn't look close enough at the source). -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] RFC: ETag support for zope.browserresource
On Mon, Aug 9, 2010 at 3:25 PM, Marius Gedminas wrote: > I've added ETag support for zope.browserresource in a branch: > http://zope3.pov.lt/trac/changeset/115596 > > Does anybody have any comments/objections? If not, I'd like to merge > this to trunk and release zope.browserresource 3.11.0. +1 as long as there's a way to disable or configure how it's computed. There's some information about issues with ETags here: http://developer.yahoo.com/performance/rules.html#etags I see that your implementation uses last-modified + size, which should generally be fine. However if you're load-balancing across two different servers and the timestamps don't match then the ETag is useless. On a completely different note, I see that the File object reads the whole file into memory. Hum. Maybe RAM is cheaper than Disk these days and it doesn't matter, but reading whole files into memory generally raises a red flag for me. hoping-no-one-is-serving-iso-files-through-zope.browserresource-ly yours, -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope summit topics
On Mon, Jul 5, 2010 at 3:52 PM, Martijn Faassen wrote: > (But hurry.resource is not perfect; I think it'd be better to step out > of Python land and create a Javascript packaging system somewhat modeled > on Python's, with easy integration into Python projects. A sprint task?) YUI 3's loader comes to mind (as its the one I have most experience with). -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] All sponsored MSDN licenses received?
Has not arrived here. But then again Brazil is far away. Em 15/06/2010 12:06, "Christian Theune" escreveu: Hi, at the meeting Adam said he has his copy of MSDN received. Did everybody else who subscribed? Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Summary (Was: Developer meeting today 15:30 UTC, Agenda attached)
On Wed, May 26, 2010 at 10:46 AM, Christian Theune wrote: > Ok. That's cool. As you read we're currently looking into Rackspace as an > alternative to Amazon. Do you have an idea whether there is a way to > leverage your work on the AMI for that, too? You'd basically have to reinstall everything. :) The only extra thing I have is a bat file that sets the right environment variables. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Summary (Was: Developer meeting today 15:30 UTC, Agenda attached)
FWIW, YES. It is possible to install the toolchains for 32-bit alongside 64-bit. That's how it is setup in the AMI I provided. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [PATCH] zope.testing/zope.testrunner doesn't tearDown layers when running in parallel
I have a patch for the issue in the subject, which seems like mostly an oversight than being by design. Bug at: https://bugs.edge.launchpad.net/zope.testrunner/+bug/579019 There are two branches linked to the bug, one against zope.testrunner and another against zope.testing. Would be nice to get some reviews. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] bug tracker gardening for bugday
On Wed, Apr 21, 2010 at 2:14 PM, Tres Seaver wrote: > I have also tagged a bunch of other bugs (mostly those with patches) > with the tag -- it would be good to adopt a culture where bugs with > patches (or branches) never languish. "There's a view for that!": https://bugs.edge.launchpad.net/zopetoolkit/+patches -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 9:40 PM, Tres Seaver wrote: > Turns out not to be too tough, given the git and mercurial examples to > stare at: > > lp:~tseaver/mr.developer/bzr_sources > > I have only tested it lightly so far, but it does seem at least to get > the initial checkouts done using bzr (even against svn+ssh:// URLs!). I tried to get this branch, but it depends on lp:~tseaver/mr.developer/trunk, which hasn't been pushed to. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 2:27 PM, Tres Seaver wrote: > - using externals to stitch together omnibus buildouts, e.g. > CMF.buildout. We could probably use something like > 'infrae.subversion' instead, maybe with a hook that allowed > local customization of the command used to fetch the sub-checkout. I'd recommend mr.developer then, if you haven't looked at it yet. http://pypi.python.org/pypi/mr.developer I believe it *might* be using infrae.subversion under the covers, though I'm not 100% confident. The nice thing it adds on top of that is switching between a release version and a checkout in a single command, IIRC. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 12:41 PM, Leonardo Rochael Almeida wrote: > Thanks Tres and Sidnei, > > My questions were intended to go to the list anyway. > > Can we take a branch from the launchpad mirror and bind it back > directly at svn+ssh://svn.zope.org/ to commit? > > For instance, say I'm reviewing a bugfix proposed by someone that > doesn't currently have access to svn.zope.org but added a > merge-proposal to lp, can I branch it, bind it to > svn+ssh://svn.zope.org and then commit? > > Wouldn't it be nice if it was possible? Not sure if it would. What you really want to do is to merge the bzr branch you got from Launchpad into the 'trunk' you got from svn.zope.org, which behaves exactly as Tres described on his previous email. Pushing the branch directly without merging first would overwrite the contents of the target branch with the contents of the pushed branch. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
> There's a dashboard for keeping track of pending and approved Merge > Proposals, eg: > > https://launchpad.net/zopetoolkit/+activereviews Not very useful since it's empty. Look at the pending proposals from zc.buildout for a better example: https://edge.launchpad.net/zc.buildout/+activereviews -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 12:17 PM, Tres Seaver wrote: > Finally, I push my branch up to Launchpad:: > > $ bzr push lp:~tseaver/zope.interface/lp_12345 Once the branch is submitted to Launchpad, it is also possible to create a Merge Proposal, which is a step up from a patch. Reviewers can see a live diff on the Merge Proposal that gets updated every time you do a new 'push'. Merge Proposals also have their own state. There's a dashboard for keeping track of pending and approved Merge Proposals, eg: https://launchpad.net/zopetoolkit/+activereviews (the same exists for users: https://launchpad.net/~sidnei/+activereviews) If you have bzrtools installed, you can use the 'bzr lp-submit' command to create a Merge Proposal from the command line, IIRC. It might seem like extra work at first, but once you get used to using Merge Proposals to track work that's pending a merge it pays off very quickly. > A branch made using 'bzr checkout' is "bound" to the SVN repository: > commits are automatically pushed back to the master. When working in > bzr, I really like the ability to "batch up" local commits, so I often > create a local branch of the "bound" one, hack on it with multiple > commits, and then push back to the "bound" branch. That's how I work too, even with branches stored in bzr, by having a 'trunk' branch that is bound it saves you a few steps when merging work back into the main tree. For people that prefer to be really explicit, you can use 'bzr branch svn+ssh://...' instead of 'bzr checkout' to create an unbound branch by default. You can also use 'bzr bind' and 'bzr unbind' to switch between bound and unbound. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [PATCH] subunit output for zope.testing
On Fri, Mar 12, 2010 at 11:09 AM, Marius Gedminas wrote: >> > On Thu, Mar 11, 2010 at 08:52:11PM +, Jonathan Lange wrote: >> >> === modified file 'src/zope/testing/testrunner/testrunner-leaks.txt' >> >> --- src/zope/testing/testrunner/testrunner-leaks.txt 2008-05-05 18:50:48 >> >> + >> >> +++ src/zope/testing/testrunner/testrunner-leaks.txt 2010-02-20 22:23:32 >> >> + >> >> @@ -16,7 +16,7 @@ >> >> >>> from zope.testing import testrunner >> >> >> >> >>> sys.argv = 'test --layer Layer11$ --layer Layer12$ -N4 >> >> -r'.split() >> >> - >>> _ = testrunner.run(defaults) >> >> + >>> _ = testrunner.run_internal(defaults) >> > >> > I'm curious about this change. >> >> Sidnei explained it correctly. This particular file is only tested if >> you're running a Python with --with-pydebug set, so it's easy to miss >> when you make a change. > > Ah! That explains why it wasn't fixed on trunk. > > (This bit should probably be committed separately. And zope.testing > could use a bit more continuous integration with various Python > versions/build flags...) I committed this change as a separate revision, and merged the rest of the patch after that. I guess I should make a 3.9.0 release now. Any objections? -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [PATCH] subunit output for zope.testing
Hi Jonathan, On Thu, Mar 11, 2010 at 5:52 PM, Jonathan Lange wrote: > Hello, > > For a long time, I've wanted to have a subunit output formatter for > zope.testing. Subunit is a language-generic streaming protocol for > test results. Once a test runner can display subunit output, it > becomes much easier to write tools to process output programmatically. > We want to use it in the Launchpad project for analyzing test results > and for distributing our test runs across multiple machines. Other > projects use it to get Hudson integration, or to glue their > multi-language test suite into one result. More information on subunit > can be found at http://launchpad.net/subunit. > > I've written a patch that adds subunit support to zope.testing by > adding a new formatter object. The patch comes complete with tests and > a willingness to jump through whatever legal hoops might be required > to get it to land. The patch is attached, and can also be found as a > merge proposal on Launchpad at > https://code.edge.launchpad.net/~jml/zope.testing/subunit-output-formatter/+merge/19825 > > I look forward to your replies. The patch looks great to me, specially the testing coverage and the fact it is completely optional to use subunit. Big +1 from me. @Marius: re: run() vs run_internal(), the former would cause a sys.exit() at some point, so run_internal() was added. I didn't spot this change, but it looks fine to me. I volunteer for commiting this patch and making a new major release, if no one else volunteers. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Moving Zope 2 downloads to LP
On Mon, Sep 21, 2009 at 5:41 PM, Chris Withers wrote: > Andreas Jung wrote: >> https://edge.launchpad.net/zope2 > > My only concern is that the above url is veeeyy slloww. If this URL timed out, it would be a problem. > https://edge.launchpad.net/zope2/+download even timed out for me fully :-( This URL shouldn't really be used, unless you're really curious and want to see all releases all the way back to 2.0.0. Rather, the URL for a series (https://launchpad.net/zope2/2.11) or for a specific release (https://launchpad.net/zope2/+milestone/2.11.4-final) should be used. > What is edge? Will we always have these speed problems? Edge runs the in-development, aka what is it going to look like in one month from now, aka the next version of Launchpad and you shouldn't generally use it, unless you're part of the "Launchpad Beta Testers" team, in which case you get automatically redirected to it, or if you want to try out in-development features, or someone cut-and-pasted the URL and forgot to remove 'edge' from it. *wink*. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: rip twisted integration out of Zope2
On Fri, Sep 18, 2009 at 1:23 PM, Andreas Jung wrote: >> IIRC, the twisted integration code was added because Jim wanted us to >> "get out of the server business." At this point, I think that folks >> wanting an alternative to ZServer should focus on using WSGI to >> integrate with the server of their choice; we should make that as easy >> / smooth as possible, and ditch the (undermaintained / icky / old) >> twisted integration. >> > I totally agree with your observation and consider the Twisted integration > as mission-failed. Nothing objections from my side. If you don't see > objections by others, just go ahead. IIRC, the twisted integration actually runs a WSGI server. But then again, my memory fooled me more than once this week alone. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZTK test failures - zope.testing
Hi Hanno, On Tue, Sep 15, 2009 at 6:42 PM, Hanno Schlichting wrote: > We are down to zero-build problems for the ZTK and just one test > failure. This is in zope.testing in testrunner-layers-buff.txt. That smells like something Gary has touched recently. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] chameleon.core removes the meta http-equiv="content-type" tag
On Wed, Sep 9, 2009 at 9:13 AM, Malthe Borch wrote: > Fabio Tranchitella wrote: >> I hope this is the right mailing list for such a question. Why does >> chameleon.core removes the meta tag http-equiv="content-type" from the >> output? > > I have no idea why; I've asked Sidnei to clarify that particular > changeset in Chameleon (although I suspect it was just carried over > as-is from ``zope.pagetemplate``). As far as I remember, it was just carried over as-is. Some (local) tests that expected it to be gone were failing with chameleon. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Wed, Sep 9, 2009 at 10:35 AM, Jens Vagelpohl wrote: > SVN 1.4 clients will work with SVN 1.5 repositories in general. However, > that's not the real issue here. The issue is the new-style externals > definitions that allow you to use "relative" paths. Those relative paths > will not work for SVN 1.4 clients. Is that based on an assumption or someone tried and verified that it doesnt work? -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] UnicodeDecodeError problems with Zope 2.12.0b4
Hi Charlie, > I only know about it because I keep on it hitting it in Windows installs > as there isn't a binary of 2.11 with the fix. You mean the latest binary doesn't have the fix? Or you haven't seen that a binary was released recently? http://www.zope.org/Products/Zope/2.11.4/ -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Looking for volunteer: windows installer builder for zc.sourcerelease-based releases
On Fri, Aug 14, 2009 at 3:48 PM, Jim Fulton wrote: > I know there are people on this list who have experience building > windows installers. > > It would be really great if someone who had some expertise building > windows installers would work with me on a tool to build windows > installers from source releases built with zc.sourcerelease. I don't > have the windows installer foo to do this by myself and am not willing > to spend the time to get the foo. > > Such a tool would be very very handy. For example, it could be used > to build a windows installer for Zope 2.12 and for ZODB. I'm interested in this, but relatively swamped at the moment attending a sprint. I will add it to my TODO to ping you about it. -- Sidnei ___ 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 3.8 fails in mysterious ways
On Thu, Jul 30, 2009 at 9:33 PM, Martin Aspeli wrote: > Unfortunately, I've got other packages that depend on a newer > zope.testing (specifically, collective.testcaselayer). But I thought > zope.testing aimed to be able to run any "valid" tests, so it sounds > like a bug in zope.testing regardless, at least since every other test > I've run in the same instance work fine. The traceback you pasted shows an UnboundLocalError. What about looking at the source and figuring out why that local variable is not defined? -- Sidnei ___ 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] Hg mirror available
Hi Wolfgang, On Fri, Jun 19, 2009 at 2:43 AM, Wolfgang Schnerring wrote: > Hi there, > > * Sidnei da Silva [2009-06-18 14:28]: >> > I'm asking because I noticed that basically all SVN->DVCS conversion >> > tools (hg convert, git-svn, bzr svn-import, svn2bzr, svn-fast-export.py, >> > svn-all-fast-export.cpp) do not convert the history properly, more >> > precisely, history that happened on branches is lost: >> >> Here's some context about this from one of the Bazaar developers, John >> Arbash Meinel. Hopefully that will solve some of your questions? > > Thanks for relaying! > >> I'm not really sure what he means by "edit" and then "merge" without a >> commit inbetween. So I'm assuming there is one. > > Sorry for being overly brief in my description; please find below a > sample shell script to set up a Subversion repository with a project > containing a trunk and a branch. To reproduce the problem I'm > concerned about, do this: > > $ create-repos.sh repos > $ svn log repos/project/trunk/feature.txt > > r9 | wosc | 2009-06-18 17:11:46 +0200 (Thu, 18 Jun 2009) | 1 line > > merged feature1 > > r8 | wosc | 2009-06-18 17:11:43 +0200 (Thu, 18 Jun 2009) | 1 line > > implemented feature1 > > > As you can see, Subversion reports the history of the file that > happenened on the branch (in r8). Can you show us your 'svn --version'? I suspect what you're seeing is a result of svn 1.5 merge tracking. > After converting the repository, however... > > $ bzr init-repo repos-bzr > $ cd repos-bzr > $ bzr svn-import file://$PWD/../repos > $ bzr log repos/project/trunk/feature.txt > > revno: 3 > svn revno: 9 (on /project/trunk) > committer: wosc > timestamp: Thu 2009-06-18 14:11:46 + > message: > merged feature1 > > ... this history is lost. Not only does it not appear in the log > output, also when looking at bzr visualize it seems like that branch > never existed at all in bzr. (I'm new to bzr, am I missing something > here?) Like John said, it *should* be possible to bring that information over if the svn repository is in 1.5 format and contains informations about merge, but at the moment that (apparently) hasn't been implemented. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Hg mirror available
Hi Wolfgang, On Thu, Jun 18, 2009 at 7:31 AM, Wolfgang Schnerring wrote: > * Sebastien Douche [2009-06-18 01:34]: >> This is a first attempt to build an Mercurial mirror : >> http://hg.zope.mirrors.securactive.org/ > > How did you convert the repository? > > I'm asking because I noticed that basically all SVN->DVCS conversion > tools (hg convert, git-svn, bzr svn-import, svn2bzr, svn-fast-export.py, > svn-all-fast-export.cpp) do not convert the history properly, more > precisely, history that happened on branches is lost: > > 1. import /trunk/foo.txt > 2. branch /trunk to /branches/mybranch > 3. edit /mybranch/foo.txt > 4. merge /mybranch to /trunk > > If you now ask svn for the history of /trunk/foo.txt (say with 'svn > log'), you see both steps 3 and 4. After conversion to a DVCS with one > of the above mentioned tools, you only see step 4, while step 3 never > happened in the DVCS repository. I think that's unacceptable, most > importantly because all commit messages that happened on branches are > lost that way. > > Does somebody here know something about this phenomenon, by any chance? > Am I missing something? Here's some context about this from one of the Bazaar developers, John Arbash Meinel. Hopefully that will solve some of your questions? """ In pretty much all dvcs merging a content exactly back to trunk does not generate a change message when doing "bzr log foo.txt". I'm not really sure what he means by "edit" and then "merge" without a commit inbetween. So I'm assuming there is one. Now, what really matters is whether or not *Subversion* recorded 4 correctly, such that it can actually see that it was a merge from 3. My understanding is that before svn 1.5 that isn't possible. So you are left with trying to infer that sort of thing from the history. Which would be possible, but probably expensive. I'm pretty sure SVN represents (4) as not a *merge* but as an indentical commit. I don't have a great answer there. Though the fact that Wolfgang says svn shows both... I suppose because "svn log" shows everything across all branches? """ -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Mailinglist for Zope 2 bugs!?
On Sun, May 17, 2009 at 3:15 AM, Jens Vagelpohl wrote: > Same here. There is no reason for yet another mailing list. I see it > as needlessly duplicating what Launchpad already does. So should we backtrack and undo the change to the zope-dev team which made it send messages to the publicly-open zope2-tracker mailing list? -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Mailinglist for Zope 2 bugs!?
Now for another question: how do people feel about moving Zope 3 and CMF bugs to a similar setup. That is, bug mail goes to a separate mailing list instead of directly to everyone that's a member of the teams in Launchpad. On Thu, May 14, 2009 at 1:13 PM, Andreas Jung wrote: > > All Zope 2 tracker notifications go now all to a new > mailinglist: > > http://mail.zope.org/mailman/listinfo/zope2-tracker > > Notification mails will no longer be send to the individual > members of the Zope 2 team @ Launchpad. > > People interested in bugtracker notifications must subscribe > to the list above > > Thanks to Sidnei and Jens for helping. > > Andreas > > On 13.05.09 16:51, Andreas Jung wrote: >> On 12.05.09 16:49, Sidnei da Silva wrote: >> >> >>>> That's not needed. Since the zope2-dev team is automatically >>>> subscribed to issues, we only need to set it's contact address. If we >>>> set that address to zope-...@lists.zope.org, then issues will >>>> automatically be delivered to it. >>>> >>>> >>> >>> >> Based on yesterdays discussion, I propose to setup a new mailman >> list 'zope2-trac...@zope.org' (or propose a better name) that will be >> added as primary contact address of the Zope 2 team @ Launchpad. >> >> So anyone can subscribe to Zope 2 ticket changes without having >> to be a member of the Zope 2 team. >> >> >> Objections? >> >> Andreas >> >> >> >> >> >> ___ >> Zope-Dev maillist - zope-...@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 ) >> > > > -- > ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany > Web: www.zopyx.com - Email: i...@zopyx.com - 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 > > > > ___ > Zope-Dev maillist - zope-...@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 ) > > -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Mailinglist for Zope 2 bug!?
On Wed, May 13, 2009 at 11:46 AM, Andreas Jung wrote: > So anyone can subscribe to Zope 2 ticket changes without having > to be a member of the Zope 2 team. Works for me. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 12:38 PM, Chris Withers wrote: > Sidnei da Silva wrote: >> >> And the original message said: >> >> """ >> That page was changed recently >> to show more information. You can see from the screenshot on this page >> that there used to be a Big Green Button in the page for joining the >> team: >> >> https://help.launchpad.net/Teams/Joining >> """ > > Yes, I read this, but since, as you say, launchpad has changed, this > information is no longer relevant so I didn't reply to it. /me shrugs. I was pointing out that there *used* to be a Big Green Button, and it doesn't exist anymore. You said "I don't see a Big Green Button". Of course the information is relevant. I was telling you *NOT* to look for a Big Green Button because it doesn't exist anymore, and, still, you looked for one. >>> Are zope2-dev or zope3-dev similarly restricted teams? >>> If so, how do people find out how to join a restricted team? >> >> See Andreas' reply. > > I have and was waiting for you to reply, I was hoping you could explain > where you'd find a join link for a moderated team... The screenshot I've sent is for a moderated team, gnome-terminator. The link is visible there and would be in the same location for someone joining zope-dev. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 12:25 PM, Chris Withers wrote: > I'm reading everything you're writing. What do you think I missed? You said: >>> Huh? I can't tell for zope2-dev as I'm a member, but I see no "big green >>> button" here: And the original message said: """ That page was changed recently to show more information. You can see from the screenshot on this page that there used to be a Big Green Button in the page for joining the team: https://help.launchpad.net/Teams/Joining """ That means you didn't read the whole message, and no matter how much effort I spend in explaining this to you, if you don't read the whole message then it's worthless. > Are zope2-dev or zope3-dev similarly restricted teams? > If so, how do people find out how to join a restricted team? See Andreas' reply. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 12:12 PM, Chris Withers wrote: > Huh? I can't tell for zope2-dev as I'm a member, but I see no "big green > button" here: > > https://edge.launchpad.net/~launchpad-dev Chris, please slow down and read the *whole* message and also my other replies. I can't keep up with your speed, and you you're just causing a lot of extra communication overhead by not reading what I'm writing and quickly replying with short messages. This is not IRC/IM. Thanks! -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 12:08 PM, Chris Withers wrote: > Sidnei da Silva wrote: >> >> On Tue, May 12, 2009 at 12:06 PM, Andreas Jung wrote: >>> >>> Will do - after having the URL for the "Join" link. >> >> https://launchpad.net/~zope2-dev/+join > > And where, exactly, are you supposed to find that?! Obviously it's not visible anymore once you *are* a member of a team. For an example of what it looks like when you're not a member of a team, see this screenshot: http://www.ubuntu-pics.de/bild/14102/screenshot_027_8l3CD1.png To me the link is perfectly clear there, with a green '+' icon and all. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 11:58 AM, Chris Withers wrote: > It took me ages to figure out how to do this, and I still couldn't tell > you how to do it now. Launchpad has an *extremely* poor UI here, what > would be so hard about having a "request to join this team" link > somewhere prominently on the team page? It's visible enough to me right there were it is? I can understand your complaint though. That page was changed recently to show more information. You can see from the screenshot on this page that there used to be a Big Green Button in the page for joining the team: https://help.launchpad.net/Teams/Joining -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 12:06 PM, Andreas Jung wrote: > Will do - after having the URL for the "Join" link. https://launchpad.net/~zope2-dev/+join -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 11:37 AM, Andreas Jung wrote: > I *think* there was such a list. LP provides mailinglist support for > for each group > > https://launchpad.net/~zope2-dev That's an option, creating a mailing list for the team. However it's not required. See below. > but I see no option for using such a list for tracker notifications. > > I suggest to add a pseudo member to the Zope 2 dev team and configure its > mail address to some new mailman list on lists.zope.org That's not needed. Since the zope2-dev team is automatically subscribed to issues, we only need to set it's contact address. If we set that address to zope-...@lists.zope.org, then issues will automatically be delivered to it. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
On Tue, May 12, 2009 at 10:25 AM, Chris Withers wrote: > The problem is that the visibility of issues in Launchpad is very poor. > You can't even get notifications of bugs unless you're part of the > development team. Using it for features means that no-one in the wider > community is likely to even know what's going on. That's bad as it means > that no-one gets the opportunity to make suggestions or comments. This > could be improved by getting issue emails sent to this list too, is that > possible? Yes, that is possible. But I fear this list might not be the most appropriate place. Maybe we should revive the 'zope-collector' mailing list (or am I dreaming that such a list ever existed?) -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Using views for exceptions in Zope 2.12?
On Sat, May 9, 2009 at 12:52 PM, Chris Withers wrote: > Hmm, so I would I register different views for a KeyError versus an > AttributeError? I believe you need to make KeyError implement an interface to be able to register a view for it. What use would be a view for KeyError anyway. *wink* -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Publishing our company internal Zope extensions and fixes
On Fri, May 8, 2009 at 6:39 AM, Andreas Jung wrote: > Hi there, > > we are currently combing through our company internal Zope (2.11) version > and trying to identify the stuff that is of interest for the public and the > Zope 2 core (including some ZODB extensions/changes). I will create a ticket > on Launchpad (containing a detailed description + patch) > for the interesting items (we have roughly 50 of them) over the next > days. All items are prefixed with "[DM]". > Everyone is invited to look at the stuff and > comment on it. I also reserve the right merging some of the changes into > the current > trunk until the next Zope 2.12 beta2 release (intentionally breaking the > rule > that no new features should be added within the beta phase). I've found the [DM] prefix to be very annoying. You could have used tags instead. Regardless of that, thanks for putting those improvements out there. I've looked at the list and at least a couple of them are very interesting to me. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Please use launchpad bugtracking/blueprints more
On Wed, Mar 25, 2009 at 1:49 PM, Baiju M wrote: > If possible, I think it is better to rename current 'zope3' as > 'zope-framework', > then create another 'zope3' project. So that we will get all bugs > and blueprints as part of 'zope-framework'. If 'zope-framework' is a project group containing 'zope3', you would already get that. See: https://bugs.launchpad.net/chameleon-template-engine https://bugs.launchpad.net/lazr -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Please use launchpad bugtracking/blueprints more
Hi Martijn, On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen wrote: > One question is what launchpad project we should use. > > The current launchpad is for "Zope 3". The steering group isn't about > Zope 3. It's about a whole bunch of libraries. Creating a separate > launchpad project for each library in the framework seems like a bit of > overkill at this stage, though it would please those people who come at > us at the perspective from libraries the most. It smells like 'Zope Framework' (zope-framework) should be a Project Group then, and there should be a 'Zope Steering Group Project' (zope-steering-group-project) as part of it, and sibling of Zope 3 and any other libraries that are part of Zope Framework. For an example of what this looks like, look at: https://launchpad.net/chameleon-template-engine I can help setting up this structure, if needed. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] setup.py "extra" dependencies
On Thu, Mar 5, 2009 at 5:20 PM, Wichert Akkerman wrote: > I would like to see a move away from zope testing frameworks to a more > standard testing infrastructure: setup.py test, possibly combined with > using nose. > > Wichert. Be aware of nose issue #102: http://code.google.com/p/python-nose/issues/detail?id=102 -- Sidnei da Silva ___ 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] Differing case for Buildout on Windows
I've been constantly bitten by a very annoying bug: depending on how you call buildout on Windows, a full rebuild might be triggered, if only the case differs. For example, all the following calls cause buildout to think settings have changed and that things need to be rebuilt. Note only the drive letter changes: c:\Python24\python.exe bin\buildout-script.py -c c:\src\some-project\buildout.cfg c:\Python24\python.exe bin\buildout-script.py -c C:\src\some-project\buildout.cfg C:\Python24\python.exe bin\buildout-script.py -c c:\src\some-project\buildout.cfg C:\Python24\python.exe bin\buildout-script.py -c C:\src\some-project\buildout.cfg Now, I'm wondering what is the best way to fix it. I originally thought of fixing the data as it comes into buildout, but that would cause existing buildouts to all possibly trigger a rebuild. I'm now thinking of fixing the place where buildout detects that the path has been changed as to normalize the path. Thoughts? -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] CSRF/XSS: zope.formlib
Hello all, I've been looking at the way CSRF protection is done in Plone (plone.protect, using a @protect decorator), and also at the XSS protection added to Zope (@postonly decorator) and was wondering if something more generic could possibly be done for zope.formlib-based forms, instead of requiring the use of a decorator. A quick look though the code, makes seem like an Action could be added to the Actions object such that the validator would do one (or both) of those checks, and something similar to the render_submit_button() which is registered as a @namedtemplate.implementation() would then be used to render the hidden form field holding the CSRF token for that specific action. Does that sound like a reasonable implementation, or is it abusing the framework? -- Sidnei da Silva ___ 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: Zope Tests: 4 OK, 2 Failed]
It is certainly in my plans to look at this. With December right
ahead, I'm sure I will make time for this before the end of this year.
On Sat, Nov 29, 2008 at 1:41 PM, Tres Seaver <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Any chance you can get these worked out? I looked at the Products.Five
> tests today, with the following observations:
>
> - Not as many tests fail if I run '-s Products.Five' as when I run the
> whole set: in particular, the first two in 'aqlegacy_ftest.txt'
> ('HTTPError', 'falcon.pt' not called) don't occur.
>
> - The next 'aqlegacy_ftest.txt' failure is because the content provider
> is not being acquisition wrapped. The remaining failure is likely
> due to the same cause (it is on the following line).
>
> - All the failing tests in Products.Five come from code which relies
> on zope.testbrowser, via the Products.Five.testbrowser shim.
>
> - The first failing zope.testbrowser test (README.txt line 1162) seems
> to be due to a change somewhere which contradicts the comment just
> below the example: "Here, the body is left in place because it isn't
> form data."
>
> - The testing requirements for zope.testbrowser itself are really
> snarled up: it pulls in basically all of Zope3.
>
>
>
> - Original Message
> Subject: Zope Tests: 4 OK, 2 Failed
> Date: Sat, 29 Nov 2008 13:00:03 +0100
> From: Zope Tests Summarizer <[EMAIL PROTECTED]>
> To: Zope-dev
> Newsgroups: gmane.comp.web.zope.devel
>
> Summary of messages to the zope-tests list.
> Period Fri Nov 28 12:00:00 2008 UTC to Sat Nov 29 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: Fri Nov 28 20:38:21 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010572.html
>
> Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux
> From: Zope Tests
> Date: Fri Nov 28 20:39:51 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010573.html
>
>
> Tests passed OK
> - ---
>
> Subject: OK : Zope-2.8 Python-2.3.7 : Linux
> From: Zope Tests
> Date: Fri Nov 28 20:32:16 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010568.html
>
> Subject: OK : Zope-2.9 Python-2.4.5 : Linux
> From: Zope Tests
> Date: Fri Nov 28 20:33:51 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010569.html
>
> Subject: OK : Zope-2.10 Python-2.4.5 : Linux
> From: Zope Tests
> Date: Fri Nov 28 20:35:21 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010570.html
>
> Subject: OK : Zope-2.11 Python-2.4.5 : Linux
> From: Zope Tests
> Date: Fri Nov 28 20:36:51 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010571.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 )
>
>
> - --
> ===
> 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
>
> iD8DBQFJMWKt+gerLs4ltQ4RAh0MAJ4gBJZOdsRw+Q8ZqhOU+VlajxuC6wCgw0BP
> oCiVHZ0ig6wiItTk9clcBJU=
> =KihL
> -END PGP SIGNATURE-
>
--
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 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 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 )
Re: [Zope-dev] [Zope-tests] FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
212/lib/python/zope/
>> testbrowser/fixed-bugs.txt", line 87, in fixed-bugs.txt
>> Failed example:
>> browser.open('http://localhost/@@/testbrowser/fragment.html#asdf')
>> Exception raised:
>> Traceback (most recent call last):
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> zope/testing/doctest.py", line 1356, in __run
>> compileflags, 1) in test.globs
>> File "", line 1, in ?
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> zope/testbrowser/browser.py", line 231, in open
>> self.mech_browser.open(url, data)
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> mechanize/_mechanize.py", line 177, in open
>> return self._mech_open(url, data)
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> mechanize/_mechanize.py", line 219, in _mech_open
>> raise error
>> HTTPError: HTTP Error 404: Not Found
>> --
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/
>> testbrowser/fixed-bugs.txt", line 90, in fixed-bugs.txt
>> Failed example:
>> browser.getLink('Follow me')
>> Exception raised:
>> Traceback (most recent call last):
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> zope/testing/doctest.py", line 1356, in __run
>> compileflags, 1) in test.globs
>> File "", line 1, in ?
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> zope/testbrowser/browser.py", line 313, in getLink
>> return Link(self.mech_browser.find_link(**args), self)
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> mechanize/_mechanize.py", line 499, in find_link
>> raise LinkNotFoundError()
>> LinkNotFoundError
>> --
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/
>> testbrowser/fixed-bugs.txt", line 92, in fixed-bugs.txt
>> Failed example:
>> browser.getLink('Follow me').click()
>> Exception raised:
>> Traceback (most recent call last):
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> zope/testing/doctest.py", line 1356, in __run
>> compileflags, 1) in test.globs
>> File "", line 1, in ?
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> zope/testbrowser/browser.py", line 313, in getLink
>> return Link(self.mech_browser.find_link(**args), self)
>> File "/home/stefan/autotest/temp/python24-zope212/lib/python/
>> mechanize/_mechanize.py", line 499, in find_link
>> raise LinkNotFoundError()
>> LinkNotFoundError
>>
>> Ran 114 tests with 2 failures and 0 errors in 3.044 seconds.
>> Running zope.traversing.tests.layer.TraversingLayer tests:
>> Tear down zope.testbrowser.tests.TestBrowserLayer in 0.008 seconds.
>> Set up zope.traversing.tests.layer.TraversingLayer/home/stefan/
>> autotest/temp/python24-zope212/lib/python/zope/configuration/
>> config.py:197: DeprecationWarning: ZopeSecurityPolicy is
>> deprecated. It has moved to zope.securitypolicy.zopepolicy This
>> reference will be removed somedays
>> obj = getattr(mod, oname)
>> in 1.218 seconds.
>> Ran 7 tests with 0 failures and 0 errors in 0.449 seconds.
>> Tearing down left over layers:
>> Tear down zope.traversing.tests.layer.TraversingLayer in 0.008
>> seconds.
>> Total: 6465 tests, 2 failures, 0 errors in 3 minutes 59.117 seconds.
>>
>> FAILED (failures=2)
>> ___
>> Zope-tests mailing list
>> [EMAIL PROTECTED]
>> http://mail.zope.org/mailman/listinfo/zope-tests
>
> --
> Anything that, in happening, causes something else to happen,
> causes something else to happen. --Douglas Adams
>
>
> ___
> 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 )
>
--
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] Zope 2.12 features
On Fri, Oct 31, 2008 at 4:28 AM, Andreas Jung <[EMAIL PROTECTED]> wrote: > If Sidnei should be successful with making Plone 2.11 compatible with Python > 2.5 then we might add "inofficial" support for Python 2.5 to the current > Zope 2.11 release...but as stated earlier I would like to see some arguments > why Python 2.5 compatiblity is necessary now and why Python 2.6 support at > some time next year would not be good enough. That's a great suggestion, and I believe we can achieve a middle ground solution here if there are more people interested in a short-term release that only adds Python 2.5 support. The idea there would be to branch a 2.12 off the 2.11 branch and only add Python 2.5 fixes on top of it, and maybe possibly a new ZODB. -- 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] Zope 2.12 features
>> - Official Python 2.5 and 2.6 support (almost done, requires a community >> decision on when we call RestricedPython supported and reviewed) > > +1 for 2.5; I'm pretty sure 2.6 is not there yet, and may be too hard > to aim for in one release. What makes you think so? -- 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] problem with using webDAV between MS Word and Zope
Please make sure you read the information contained here:
http://awkly.org/2007/06/23/google-soc-status-report-1/
On Wed, Oct 29, 2008 at 2:15 AM, Wayne Glover
<[EMAIL PROTECTED]> wrote:
> hi all,
>
> i am using plone 3+ with zope ope-2.10.5-final
>
> I am trying to use webDAV between Word and Zope. This works fine for OO
> (yes i know - don't use Word! Not an option)
>
> I have searched far and wide and have found the 'solution' at
> (https://bugs.launchpad.net/zope2/+bug/143725) however, i can't get it to
> work for me with this installation
>
> _
>
> The changes suggested by the bug fix at the link are as follows:
>
> *** /usr/local/zope-2.8.4/lib/python/webdav/Resource.py 2006-06-13
> 16:35:29.0 -0500
> --- /usr/local/zope-2.8.4/lib/python/webdav/Resource.py.orig2006-06-13
> 16:20:17.0 -0500
> ***
> *** 197,203
> self.dav__init(REQUEST, RESPONSE)
> RESPONSE.setHeader('Allow', ', '.join(self.__http_methods__))
> RESPONSE.setHeader('Content-Length', 0)
> - RESPONSE.setHeader('MS-Author-Via', 'DAV')
> RESPONSE.setHeader('DAV', '1,2', 1)
> RESPONSE.setStatus(200)
> return RESPONSE
> --- 197,202
> ***
> *** 594,606
> def manage_DAVget(self):
> """Gets the document source"""
> # The default implementation calls manage_FTPget
> ! # some things have manage_FTPget's that take REQUEST and RESPONSE
> ! # -- mengel 2006-06-13
> ! try:
> ! res = self.manage_FTPget()
> ! except:
> ! self.manage_FTPget({},{})
> ! return res
>
> def listDAVObjects(self):
> return []
> --- 593,599
> def manage_DAVget(self):
> """Gets the document source"""
> # The default implementation calls manage_FTPget
> ! return self.manage_FTPget()
>
> def listDAVObjects(self):
> return []
> ___
>
> Note that what it is doing is forcing a response of 'MS-Author-Via', 'DAV')
>
> what this is supposed to do is force Word to accept webDAV vs. it's only
> silly thing. good in theory, but i couldn't get it to work
>
> After revising the file on the zope server, i then tried Word webDAV. I
> monitored the network traffic to look for the OPTIONS response telling Word
> to use webDAV. see attached txt file which has tcp stream while i tried to
> save .doc file.Note that, in the above change, the "RESPONSE.setHeader
> ('MS-Author-Via', 'DAV') is supposed to be returned by Zope to force Word to
> work with webDAV, but this does not happen.
>
> This has been driving me crazy and any help would be greatly appreciated.
>
> Note: i have attached the zope 'resource.py' as i have modified it based on
> the above link. plz let me know if you can see what is wrong.
>
>
> Thanks,
>
> Wayne Glover
> TechnicalMedia, Inc.
> ___
> 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 )
>
>
--
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] Proposal: Backporting some Python 2.5/2.6 fixes
On Mon, Oct 27, 2008 at 4:06 PM, Andreas Jung <[EMAIL PROTECTED]> wrote: > Please create branches first and then lets review the changes. Great. > What is the > state of the compatability of Z3 modules with Python 2.5/2.6 as used in Zope > 2.10/2.11? Hard to tell at this point. -- 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] Proposal: Backporting some Python 2.5/2.6 fixes
On Mon, Oct 27, 2008 at 3:42 PM, Andreas Jung <[EMAIL PROTECTED]> wrote: > Why do we need these backports on the current maintenance branches? They are small cleanups that could potentially allow someone to run Python 2.5 or 2.6 if they really really really wanted to, but note should be made that it would be completely and utterly unsupported. -- 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] Proposal: Backporting some Python 2.5/2.6 fixes
Hi all, I would like to propose backporting some of the fixes needed for Python 2.5 and 2.6 all the way down to Zope 2.10. The fixes that would be backported would only be those that deal with syntax changes (eg: 'with' and 'as' keyword being used as variables, relative imports) and some C-level changes, to Acquisition and zope.app.container if I recall. I would *not* backport changes to RestrictedPython because those are actually features (support for newer versions of Python) as opposed to the other changes, which are just 'bugfixes' IMHO. Would anyone be against this? -- 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] Zope 2.12 - supported Python versions
On Wed, Oct 15, 2008 at 11:28 AM, Hanno Schlichting <[EMAIL PROTECTED]> wrote: > Stephan Richter wrote: >> On Wednesday 15 October 2008, Sidnei da Silva wrote: >>> I don't want to rain on your parade, but I already did a first pass at >>> reviewing the changes in Python 2.5 and Python 2.6. There are no >>> significant changes that I could spot so far. Apparently the major >>> changes are: >> >> I also did a review for Python 2.5 a while ago... > > So does this mean RestrictedPython just had a bad emotional status in > the community, but it is actually well proven and reviewed now? > > I always was under the impression that Jim feared the code and the > required security audit was perceived as a major painful undertaking. That was my perception too. But after looking at the code it is really not bad at all. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 2.12 - supported Python versions
Folks,
I don't want to rain on your parade, but I already did a first pass at
reviewing the changes in Python 2.5 and Python 2.6. There are no
significant changes that I could spot so far. Apparently the major
changes are:
- Ternary 'if'
- Context Managers ('with' keyword)
Both of those are just syntactic sugar for already existing idioms and
they are pretty much covered by already existing transformation of the
ast tree.
Also, the only new bytecode seems to be 'WITH_CLEANUP' which is part
of the handling of the 'with' keyword.
In general, RestrictedPython seems to be well-structured and the tests
are easy to extend and understand for someone that played with ast
(like the folks playing with z3c.pt).
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
___
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] Relative Imports: PEP-328
FWIW, I've done that now. On Wed, Oct 8, 2008 at 9:43 AM, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: > > El 8 Oct 2008, a las 14:23 , Sidnei da Silva escribió: > >> On Wed, Oct 8, 2008 at 8:53 AM, Philipp von Weitershausen >> <[EMAIL PROTECTED]> wrote: >>> >>> Sidnei da Silva wrote: >>>> >>>> I'm trying to fix some import errors, which seem to be related to >>>> PEP-328. >>>> >>>> I'm fixing those errors this way, though I don't know if that's the >>>> recommended way of fixing it. Thoughts? >>>> >>>> """ >>>> try: >>>> from DT_Util import parse_params, name_param >>>> except ImportError: >>>> # See PEP-328 >>>> from .DT_Util import parse_params, name_param >>>> """ >>> >>> This will generate a SyntaxError in Python 2.4. So unless we *require* >>> Python >= 2.5, this won't work. >> >> Yuck. I hadn't thought of that. Any other suggestions? Like, using >> zope.documenttemplate? :) > > zope.documenttemplate is a crippled version of DocumentTemplate. It doesn't > have all features (e.g. it lacks the C extension module) and hasn't been > kept up-to-date with respect to bugfixes. So it seems like a good idea to > put this clone out of its misery and retire it. > > I ultimately suggest going to absolute imports everywhere (at least as long > as we have to maintain Python 2.4 compatibility). I realize that > DocumentTemplate/DocumentTemplate.py creates a problem. So here's what I > suggest: > > 1. Rename DocumentTemplate/DocumentTemplate.py to, say, > DocumentTemplate/DocTemplate.py (feel free to come up with > a better name) > > 2. Introduce absolute imports to DocumentTemplate.DocTemplate > everywhere > > 3. Ensure backwards compatibility by adding the following lines > to DocumentTemplate/__init__.py:: > >import DocumentTemplate.DocTemplate >import sys >sys.modules['DocumentTemplate.DocumentTemplate'] = > DocumentTemplate.DocTemplate > > I *think* this should work. > > -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 2.12 - supported Python versions
On Tue, Oct 14, 2008 at 2:16 PM, Andreas Jung <[EMAIL PROTECTED]> wrote: > Thanks for starting the discussion. Going for Python 2.6 also requires that > we get the ZCA running on top of Python 2.6 until some time next year. FWIW, that's what I've been working on. There's enough of the the ZCA working on Python 2.6 to run Zope 2. Would anything else be needed? I would say we are pretty much done as far as Zope 2 is concerned. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] ZServer/medusa doesn't work with Python 2.6
This one is for someone that has some asyncore knowledge: Python 2.6 has cleaned up and integrated many patches to asyncore, some of which seem to have broken the medusa version shipped with Zope. https://bugs.edge.launchpad.net/zope2/+bug/280020 My question is, is this something we should fix in Zope or is it a bug in Python 2.6 that asyncore is not backwards compatible? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Relative Imports: PEP-328
On Wed, Oct 8, 2008 at 8:53 AM, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: > Sidnei da Silva wrote: >> >> I'm trying to fix some import errors, which seem to be related to PEP-328. >> >> I'm fixing those errors this way, though I don't know if that's the >> recommended way of fixing it. Thoughts? >> >> """ >> try: >>from DT_Util import parse_params, name_param >> except ImportError: >># See PEP-328 >>from .DT_Util import parse_params, name_param >> """ > > This will generate a SyntaxError in Python 2.4. So unless we *require* > Python >= 2.5, this won't work. Yuck. I hadn't thought of that. Any other suggestions? Like, using zope.documenttemplate? :) -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 279981] Re: zope.app.testing use of 'with' keyword breaks with Python 2.6]
I'm sorry Andreas but where did you find mention of code incompatible with Python 2.4? On Wed, Oct 8, 2008 at 3:15 AM, Andreas Jung <[EMAIL PROTECTED]> wrote: > > Who is committing code that is incompatible with Python 2.4? > I think it is not acceptable - even for code on the trunk of a package. > > Andreas > Original-Nachricht > Betreff: [Bug 279981] Re: zope.app.testing use of 'with' keyword breaks with > Python 2.6 > Datum: Wed, 08 Oct 2008 04:13:52 - > Von: Sidnei da Silva <[EMAIL PROTECTED]> > Antwort an: Bug 279981 <[EMAIL PROTECTED]> > An: [EMAIL PROTECTED] > Referenzen: <[EMAIL PROTECTED]> > > ** Also affects: zope.app.testing > Importance: Undecided > Status: New > > ** Also affects: zope2 > Importance: Undecided > Status: New > > -- > zope.app.testing use of 'with' keyword breaks with Python 2.6 > https://bugs.launchpad.net/bugs/279981 > You received this bug notification because you are a member of Zope 3 > Developers, which is subscribed to Zope 3. > > -- > 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 > > > ___ > 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 ) > > -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Relative Imports: PEP-328
On Wed, Oct 8, 2008 at 2:40 AM, Marius Gedminas <[EMAIL PROTECTED]> wrote: > I'd suggest converting it to an absolute import > > from zope.documenttemplate.dt_util import parse_params, name_param So I thought at first. Except there is a problem: Inside 'DocumentTemplate' there's another 'DocumentTemplate' module. So doing: 'from DocumentTemplate.DT_Util import parse_params' ... tries to import DT_Util from the relative module. Then the fix is to do: 'from __future__ import absolute_import' ... except that doesn't work on Python 2.4. So the try: except seems to be the only way around here, unfortunately. > or whatever the equivalent for Zope 2 is (I'm assuming it's Zope 2, > since DT_Util is capitalized). Another option might be to switch this to use zope.documenttemplate. :) -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Python 2.6: 'with' in Interfaces
Trying to run some tests with Python 2.6 I stumbled on a problem that
I need help with: an interface that has an attribute named 'with'.
The interface in question is defined in zope.app.component.back35:
class IAdapterRegistration(IComponentRegistration):
...
with = schema.Tuple(
title = _("With interfaces"),
...
Any suggestions on how to fix this one?
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
___
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] Relative Imports: PEP-328
I'm trying to fix some import errors, which seem to be related to PEP-328. I'm fixing those errors this way, though I don't know if that's the recommended way of fixing it. Thoughts? """ try: from DT_Util import parse_params, name_param except ImportError: # See PEP-328 from .DT_Util import parse_params, name_param """ -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] z3c.form and lxml
On Tue, Sep 16, 2008 at 12:48 AM, Roger Ineichen <[EMAIL PROTECTED]> wrote: > Sidnei, > we or at least I as the second last windows user need > your help;-) > > We like to use lxml everywhere in z3c packages > because Malthe implemented a nice and fast PageTemplate > relacement in z3c.pt based on lxml. > > The problem right now is, that nobody compiles the > lxml binary eggs for windows. > > What do you think, can you do that important part? > And more important can you keep doing that in the future? Yes, I do compile the binary eggs. And yes, you can expect me to keep doing it in the future. It might take 2-3 weeks sometimes, but eventually I get around to it. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] lxml and z3c.form strategy?
What's the actual issue with lxml? It's not that hard to compile it (I'm the person that compiles the official releases), just a little bit under-documented. On Tue, Sep 16, 2008 at 12:29 AM, Roger Ineichen <[EMAIL PROTECTED]> wrote: > Malthe, Stephan > > I decided after along night, trying to compile > lxml on a windows box, that we will not use > lxml and lxml based packages like z3c.form, > z3c.template, z3c.macro etc at some of our > windows servers. > > We have to find a strategy to keep this packages > free of lxml and implement the z3c.pt support in > this packages in a different way. > > I really like your lxml based z3c.pt work. It's > nice and incredible fast. > > What do you think about that? > > I know it's a hugh amount of work, but I'm willing > to help with the refactoring if you like. > > > 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 ) > -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Increasing the Zope Security [EMAIL PROTECTED]
It's not possible to join the team: """ Restricted Team: New members can only be added by one of the team's administrators. """ On Mon, Sep 1, 2008 at 2:06 PM, Andreas Jung <[EMAIL PROTECTED]> wrote: > Hi there, > > I just submitted a possible security related Zope issue on Launchpad and > noticed that the bug has been assigned to the Zope Security Team which > consists only of Jim. I suggest that a number of competent developers > of the Zope 2 and Zope 3 world volunteer to join the team in order to make > sense to the Zope Security team. > > 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 > > ___ > 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 ) > > -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 3 on Python 2.5, Zope 3 releases
On Fri, Jul 18, 2008 at 1:23 PM, Chris Withers <[EMAIL PROTECTED]> wrote: > Would be rgeat to have a bullet point list for how to get a suitable > environment set up given that I don't have mingw32 and have never used it > before in my life :-S Like this? http://plone.org/documentation/how-to/using-ploneout-on-windows -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 3 on Python 2.5, Zope 3 releases
On Thu, Jul 17, 2008 at 12:54 PM, Stephan Richter <[EMAIL PROTECTED]> wrote: > On Thursday 17 July 2008, Martijn Faassen wrote: >> Yeah, I share this worry. I wonder what Jim is using. If Jim is using >> a mingw setup too, then there seems to be no real problem, after all. >> >> :) > > He does. :-) And I do too. I released several Windows binary eggs based on > that setup as well. Mingw compiled extensions are binary-compatible yes. Mark Hammond has confirmed that at least once to me. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: [Plone-developers] PAULA: bringing Zope 3's authentication to Plone and beyond
"may or may become a part of Zope and/or Plone in the future". Well put Martin. ;) -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: Deprecation warnings from 2.11.0
On Fri, Jul 4, 2008 at 3:12 PM, Chris Withers <[EMAIL PROTECTED]> wrote: > Did we as a community really release a stable version that emits deprecation > warnings?! :-( We did (/me hides). -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: buildout on Windows
On 6/23/08, Chris Withers <[EMAIL PROTECTED]> wrote: > Sidnei da Silva wrote: > > > This one is used to pre-build everything, and then we run Inno Setup > > to build the installer: > > > > > https://svn.plone.org/svn/plone/Installers/Windows/trunk/buildout/installer.cfg > > > > Which buildout.cfg is this extending? The one in the same directory. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: buildout on Windows
On 6/23/08, Chris Withers <[EMAIL PROTECTED]> wrote: > Surely that'd do it, right? I have vague memories of someone working on > this... who is it? That'd be Phillip I believe. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: buildout on Windows
On Sun, Jun 22, 2008 at 1:10 PM, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: > b) or extend the plone.recipe.zope2install recipe to get the binary Zope > installer and execute it (if that's even possible) on Windows, rather than > trying to get the source tarball and compile it (this would still be the > default for Unixy platforms). Why would it not be possible? Another option would be to use some sort of 'Inno Unpacker', which I believe exists but I have not looked at. Yet another option would be to just tar up the results of running 'setup.py build-ext -i' on a extracted tarball and put it in some common location, alongside with the installer. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: buildout on Windows
On Sat, Jun 21, 2008 at 3:16 PM, Chris Withers <[EMAIL PROTECTED]> wrote: > Hey Sidnei, > > Sidnei da Silva wrote: >> >> Depending on how 'plone-ish' your buildout is, you can start from the >> newly-created, experimental buildout-based Plone Installer for >> Windows: >> >> https://launchpad.net/plone/3.1/3.1.2/ > > So how does this work? There are some notes here: https://svn.plone.org/svn/plone/Installers/Windows/trunk/NOTES.txt > Where's the buildout.cfg that gets used and what recipes have you > created/tweaked to make this happen? This one is used to pre-build everything, and then we run Inno Setup to build the installer: https://svn.plone.org/svn/plone/Installers/Windows/trunk/buildout/installer.cfg After install, we run bootstrap and buildout with this config file. All eggs will be in buildout-cache at that point: https://svn.plone.org/svn/plone/Installers/Windows/trunk/buildout/buildout.cfg > Also, related, would you be up for building binary windows eggs for the zope > 3 components for both python 2.4 and python 2.5? No. :) But I believe Jim volunteered. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: buildout on Windows
Depending on how 'plone-ish' your buildout is, you can start from the newly-created, experimental buildout-based Plone Installer for Windows: https://launchpad.net/plone/3.1/3.1.2/ -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Why I dislike narrative doctests
Can't you start a plain-old unittests module and stick your test in
there? Is there any rule that says you cannot create a plain-old test
module if the project you are fixing the bug in uses doctests?
On Wed, Apr 23, 2008 at 5:19 PM, Marius Gedminas <[EMAIL PROTECTED]> wrote:
> Suppose I find a bug (say, zope.testing.testrunner.StartUpFailure
> objects make unittest.TextTestRunner cry). Being a good developer I
> want to start the bug fix with a unit test.
>
> Now if zope.testing used old-style isolated unit tests, I could open the
> tests.py (or tests/test_testrunner.py) in a text editor and start
> writing:
>
> class OptionsStub(object):
> post_mortem = False
>
> def doctest_StartUpFailure():
> """Test that StartUpFailure is a proper unittest.TestCase
>
> StartUpFailure is a TestCase-lookalike that is inserted into the
> test suite to indicate that a failed import of a test module
> won't be unnoticed.
>
> >>> from zope.testing.testrunner import StartUpFailure
> >>> options = OptionsStub()
> >>> module_name = 'test_me'
> >>> exc_info = (ImportError, ImportError('zonkulator'), None)
> >>> test = StartUpFailure(options, module_name, exc_info)
> >>> unittest.TextTestRunner(verbosity=2).run(test)
>
> This is a regression test for http://launchpad.net/bugs/221151
> """
>
> There, I'm almost done. Now I can fix the bug and paste the correct
> output into the doctest.
>
> But zope.testing uses narrative doctests instead of isolated unit tests.
> There are 22 plain-text files that together comprise over 4500 lines of
> text. Now instead of mechanically opening the appropriate test module
> and grepping for the class/function name I have to figure out which of
> the txt files is the appropriate place for the new test. After that I
> have to figure out how to insert it into the narrative seamlessly. Or
> decide to create a new file---but a hundred of .txt files each 20-lines
> long is not a good idea, in my opinion.
>
> Suddenly I almost don't want to fix the bug any more.
>
> While I was writing this, I suddenly realised that almost all
> zope.testing's txt files are actually functional tests. There are
> nearly no unit tests there. Perhaps that's what causing me pain.
>
> I still maintain that:
>
> * adding a new unit test should be a trivial task
>
> * extending a narrative doctest is not a trivial task
>
> * the only way to solve this conflict is to explicitly separate unit
> tests (test_*.py) from doctest-enhanced API documentation (*.txt).
>
> Marius Gedminas
> --
> UNIX is user friendly. It's just selective about who its friends are.
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFID5m0kVdEXeem148RAqs5AJ4qUo9IiqMSsuFOIrZBTq+xyWv/FQCePM/Q
> eTvxFfGfDPuGA1YzlM8CTks=
> =J91E
> -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 )
>
>
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
___
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 2.11] Stepping forward and going beta
On Dec 9, 2007 5:30 AM, Andreas Jung <[EMAIL PROTECTED]> wrote: > Objections? Thoughts? That branch didn't look like it was far off being finished. Is there a TODO of what is pending to finish it? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: Splitting 'Signals' into an egg?
On Oct 4, 2007 11:02 AM, Sidnei da Silva <[EMAIL PROTECTED]> wrote: > Not sure what Zope 3 is using these days (haven't checked), but Zope 2 > had a 'Signals' package that handled signaling events on both Windows > and *nix in a somewhat transparent way. Has anyone thought of > packaging that as an egg? Toc toc, is there anybody out there? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: Hivurt code hosting
I believe you can host code on launchpad.net too, but using 'bzr' instead of Subversion. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: Zope on Python 2.5?
On 11/1/07, Fred Drake <[EMAIL PROTECTED]> wrote: > This seems to be a common misconception; I'm not sure why. > > Python 2.4 has *already* hit EOL. There will only be security fixes > released in source form. > > When a new Python 2.X is released, a final 2.X-1 bugfix release is > made and 2.X becomes the maintenance release. 2.X-1 gets critical > security fixes only. The unreleased trunk becomes the development > version. Ouch. I guess we should skip 2.5 and target 2.6 then to save some time :) -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: Zope on Python 2.5?
I would like to point out that on this thread people are getting too tied up with restrictions about *installing* stuff on the system Python and forgetting that for example, buildout will not install stuff on the system Python, but people might want to run a Zope (2) buildout on Python 2.5 just because it's the Python they have installed. Now, putting Limi's proven incapability to start a discussion without causing major commotion from our fellow developers, let's rephrase the question: Will Zope 2 be supported on Python 2.5, regardless of whether it's a system-installed Python or not? I think we are closely approaching the EOL for Python 2.4. Supposedly when Python 2.6 comes out next year Python 2.4 will be officially discouraged and will not receive any more fixes other than security fixes. I believe this is a critical issue and the interested parts need to work together on it. Maybe the Plone Foundation and the Zope Foundation can work together and setup a bounty to fund some developer to do this work? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] zc.recipe.egg and 'install' instead of 'develop'?
On 10/31/07, Jim Fulton <[EMAIL PROTECTED]> wrote: > > On Oct 31, 2007, at 12:45 PM, Sidnei da Silva wrote: > > > Is there a recipe that will 'install' a distutils package from source > > instead of doing 'develop'? Couldn't find it. :( > > build Erm, can you be more specific? The only two options in zc.recipe.egg seem to be 'develop' and 'custom', none of which will run a 'setup.py install' from a checkout. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] zc.recipe.egg and 'install' instead of 'develop'?
Is there a recipe that will 'install' a distutils package from source instead of doing 'develop'? Couldn't find it. :( -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Splitting 'Signals' into an egg?
Not sure what Zope 3 is using these days (haven't checked), but Zope 2 had a 'Signals' package that handled signaling events on both Windows and *nix in a somewhat transparent way. Has anyone thought of packaging that as an egg? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: Mixing recipes (zc.recipe.cmmi reuse)
On 9/24/07, Jim Fulton <[EMAIL PROTECTED]> wrote:
> > Or would it require the recipe
> > writer to explicitly 'subclass' (?) cmmi to get patch functionality?
>
> I prefer composition. A number of recipes reuse the egg recipe
> through composition.
>
> Generally, an egg will need to explicitly provide a Python API for
> other eggs. See, for example, http://pypi.python.org/pypi/
> zc.recipe.egg/1.0.0b6#egg-recipe-api-for-other-recipes
Gotcha, that makes sense.
> > Or even, would a 'post-fetch'/'pre-build' generalization be desired,
> > 'patch' being one such application?
>
> I have no idea what that is. :)
My intent is:
"Given any recipe, no matter where data is coming from (be it an egg
in PyPI, a Subversion checkout or a tarball), I would like to be able
to perform an operation in the 'local copy' of the data, without
depending on the person that wrote the recipe to have allowed me to do
so"
An example being, after a recipe that does a Subversion checkout runs,
my custom operation kicks in and applies a patch to the local copy
before the buildout processing continues.
I believe that this might be doable today by writing custom
configuration, but maybe it's such a common case that could be
simplified.
Maybe something along the lines of (note: this is all pseudo-config):
"""
[Step1]
recipe = some.recipe.checkout
url = svn://url-to-repo/package
[Step2]
recipe = zc.recipe.cmmi
source = {Step1:location}
patch = /path/to/my/patch
[zope2]
products = {Step2:location}
"""
I believe that something like this might already work today, if not it
might be easy to make it work that way. But what I'm after is to avoid
Step2 above by listing the patch to be applied in Step1 even if
'some.recipe.checkout' does not support the 'patch' option directly.
All in all, if you tell me that the hypotetical Step2 above really
can't be avoided and that the best option is to make
'some.recipe.checkout' and any other recipes out support the 'patch'
option directly, I would be fine with that too.
Does it make more sense now?
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
___
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] Mixing recipes (zc.recipe.cmmi reuse)
Hi there, Not sure this is the right list, but let's give it a try. I would like to use the 'patches' functionality from zc.recipe.cmmi together with other recipes. I believe this is useful functionality and is interesting to all sorts of recipes, not only to cmmi-based ones. So the question is, does the zc.buildout architecture support reusing options from a recipe on other recipes? Or would it require the recipe writer to explicitly 'subclass' (?) cmmi to get patch functionality? Or even, would a 'post-fetch'/'pre-build' generalization be desired, 'patch' being one such application? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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: Fwd: [Zope-dev] Options replacing DateTime with datetime!?
(Sending reply to the list, since Gustavo doesn't seem to be subscribed.)
On 9/17/07, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote:
>
> Hey Lennart,
>
> > 1. Giving the timezone string 'GMT+3' meant that you got the timezone
> > GMT-3 back. This was done intentionally and I had some discussion with
> > Gustavo about that.
>
> True.. after these discussions I'm sure that the current implementation
> isn't ideal. I'll try to fix that in the next dateutil release.
>
>
> > 2. "Timezones in the form of EST5EDT or US/Eastern doesn't work.
> >
> > Both these can be avoided by keeping the old time and timezone
> > interpretation around.
>
> I'm not aware about that. In fact, I'm curious about what the problem
> is. EST5EDT may be seen in the test suite several times, using different
> sources of information even.
>
> >>> tz.gettz("EST5EDT")
> tzfile('/usr/share/zoneinfo/EST5EDT')
>
> >>> tz.tzstr("EST5EDT")
> tzstr('EST5EDT')
>
>
> > The third one is the the modules concept of local timezone is set when
> > the module is imported, and there was no way to change it afterwards,
>
> dateutil can get timezones from several different sources and formats.
> tzlocal is based on what libc exposes, and I don't advice it to be used
> if any better source of information is available. If the fact that
> some of its data is initialized as module import time is bothering you,
> I can definitely change it, but please keep in mind that there are other
> gotchas (variables in the time module won't change unless you call tzset,
> for instance)
>
> I recomment using tz.gettz() instead, which doesn't suffer from any of
> the problems you described, and provides much better information
> about the local timezone.
>
>
> > in effect making any testing impossible, as any tests in converting
> > timezones will only work in the timezone of the one who wrote the
> > tests. That's a huge problem when you need to test that timezones work
> > properly, and IMO opinion makes the module pretty much useless for any
>
> Making testing impossible is a bit overstated, IMO. I use TDD in a
> daily basis, and testing that environment seems far from challenging.
> Time-related logic is tricky to test sometimes, of course, but saying
> that dateutil is useless because tzlocal is initialized at import time
> is funny, at least.
>
> Here is a hot-fix for tzlocal, if that's the problem you're blocked on.
>
> class tzlocal(dateutil.tz.tzlocal):
>
> @property
> def _std_offset(self):
> return datetime.timedelta(seconds=-time.timezone)
>
> @property
> def _dst_offset(self):
> if time.daylight:
> return datetime.timedelta(seconds=-time.altzone)
> else:
> return self._std_offset
>
> dateutil.tz.tzlocal = tzlocal
>
>
> --
> Gustavo Niemeyer
> http://niemeyer.net
>
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
___
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] Options replacing DateTime with datetime!?
-- On 8/25/07, Andreas Jung <[EMAIL PROTECTED]> wrote: Before digging deeper I would like to hear some opinions if this seems a reasonable approach? Unlikely that we can achieve 100% backward compatibility but possibly 99%thoughts...comments? Yeah, I had that idea as well, and also tried it and also got stuck on timezones. :-) I used dateutil, though, and one of the main problems with that is that it calculates what timezone you are in when you load the module, which basically makes timezone testing impossible. pytz may be a better choice. Uhm, I am not quite sure that is the case. What exactly is the problem? Creating a 'datetime' without timezone information? Why the timezone you are in matters for testing? If you could explain what the problem is, we could ask Gustavo to take a look at the issue. He's very receptive with patches and bugfixes. -- Sidnei da Silva Enfold Systems, Inc. ___ 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] Merging #1441 fix to 2.10 branch?
On 6/25/07, Andreas Jung <[EMAIL PROTECTED]> wrote: --On 25. Juni 2007 14:38:59 -0300 Sidnei da Silva <[EMAIL PROTECTED]> wrote: > Hi there, > > I would like to merge the fix for issue #1441 into the 2.10 branch. It > restores a 'feature' that was removed almost 35 months ago, Any idea why it was removed? The issue title should say it all, but here it goes: Zope used to send a "MS-Author-Via: DAV" header, which in old versions of Microsoft Office would cause Word to be fired and try to lock the file and then open it, which if the user was an anonymous user would prevent the file download. Recently (Jan 2005 and May 2007) Microsoft fixed this issue by updating the "WebFolders" implementation. Also recent versions of Microsoft Office don't have this issue either. The patch adds back the "MS-Author-Via: DAV" header for compatibility with old versions of WebFolders, but with a toggle on zope.conf, default to off. It also adds a "Public: ..." header, for compatibility with *new* versions of WebFolders, which now require it, with another separate toggle in zope.conf, also default to off. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Merging #1441 fix to 2.10 branch?
Hi there, I would like to merge the fix for issue #1441 into the 2.10 branch. It restores a 'feature' that was removed almost 35 months ago, but the feature will be disabled by default, so should not affect anything unless you enable it in zope.conf. I've added good test coverage for it, and it has been applied to trunk. http://svn.zope.org/?rev=76767&view=rev Any objections against applying it to the 2.10 branch? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: Zope Installers for Windows: ready for testing
Cursory testing suggests they're both fine. If no-one's found any problems, I'll put them up some time tomorrow... Thank you Chris! -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 Installers for Windows: ready for testing
It's that time again... fire up your VMs and do some testing. Let's get those up on the website ASAP! http://files.enfoldsystems.com/Zope-2.10.3-Final-7151.exe http://files.enfoldsystems.com/Zope-2.9.7-Final-7151.exe -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Early processing of request body (was: Proposal for optimized Blob handling)
On 3/8/07, Christian Theune <[EMAIL PROTECTED]> wrote: I really wonder whether that's necessary. Yeah, after re-reading Dieter's reply, I sort of wonder how big of a deal that is. Actually. I'll take a look around the other web frameworks and check how they do their REQUEST processing. Maybe I can learn something from that. I suspect you will find that they don't do anything special. You could look at how Apache or Squid does it though. > Hopefully something similar could be done for files being sent *out* > of the application when they don't need any application processing > anymore (ie, Blobs!). We already have that. The FileStreamIterator allows you to hand out an iterable that will be used outside the application thread to stream data from. Right, I had something else in mind which is serving large data from the ZODB when you're done with the application logic. But that's another story. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Early processing of request body (was: Proposal for optimized Blob handling)
On 3/7/07, Christian Theune <[EMAIL PROTECTED]> wrote: Right. This optimization is about leveraging the fact that in many situations the upstream bandwith is *much* lower than the IO bandwith to the disk. Another condition that I have (and I think this is the general pattern) is that application threads should be given back to the pool as quickly as possible. If 5 seconds are spend in the application thread to untangle mime data which has nothing application-specific about it and then only 100ms or so in the application itself, I'd say there is a major overhead problem. I had came to the same conclusion a couple weeks ago, somehow *wink*. Maybe we've been influenced by the same person. :) So if the uploaded file shouldn't be handled by the application thread, neither by the IO layer, then I guess we need a 'upload handling thread pool' of some sorts, whose sole purpose is to handle incoming requests that are large before it gets to the application thread while still outside the async IO layer. Hopefully something similar could be done for files being sent *out* of the application when they don't need any application processing anymore (ie, Blobs!). -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Proposal for optimized Blob handling
On 3/7/07, Christian Theune <[EMAIL PROTECTED]> wrote: > Does this work on Windows? Link does not work on Windows using the link() function from the os module. I don't know whether Windows has any API for doing this kind of operation. Yes [1] it [2] does [3]. The omission on os.link() is just the lack of a good soul to contribute it apparently [4]. A good task for a friday evening. [1] http://msdn2.microsoft.com/en-us/library/aa363860.aspx [2] http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil_hardlink.mspx?mfr=true [3] http://www.flexhex.com/docs/articles/hard-links.phtml [4] http://www.thescripts.com/forum/thread537011.html -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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] Re: [Zope3-dev] Re: Proposal for optimized Blob handling
On 3/7/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: Am I the only person here who immediately associated "link" with the POSIX? Also, am I the only one who read "when possible" as "when on a POSIX system where link is available", in other words, "when not on Windows"? One starts to wonder... NTFS does support hard links since version 5, which means Windows 2000+. It does not support hard links to directories though, only soft links (which are called junctions or junction points). The version of NTFS shipped with Vista supports hard links for directories I believe. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 )
