Re: [Zope-dev] Re: new zope.org, sphinx, and documentation management
On Wed, Apr 23, 2008 at 10:48 PM, Paul Carduner [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 12:01 PM, Martin Aspeli [EMAIL PROTECTED] wrote: I would start with the simple HTML approach, personally. It may be all we need. Hopefully there will be a first sample of this in the next hour or so. Ok, I setup a sample of what sphinx produces after a quite minimal setup for z3c.form. Check it out at: http://docs.carduner.net/z3c.form/. I made a few small modifications to the existing documentation, which I checked into a branch on svn.zope.org along with the sphinx setup generated for me by the sphinx-quickstart command. A few goody features include: Full text searching powered by javascript: http://docs.carduner.net/z3c.form/search.html Module index with quick synopses: http://docs.carduner.net/z3c.form/modindex.html (click on the plus symbol after the big Z) Cross links to other parts of the documentation: http://docs.carduner.net/z3c.form/src/z3c/form/README.html So far, I think this is pretty good for what took me maybe an hour. Think of what it would be with some extra documentation cleanup. -- Paul Carduner http://www.carduner.net ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Wed Apr 23 11:00:00 2008 UTC to Thu Apr 24 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed Apr 23 21:00:36 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009450.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 23 21:02:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009451.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 23 21:03:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009452.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 23 21:05:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009453.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 23 21:06:38 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009454.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 )
[Zope-dev] zc.authorizedotnet needs a new key
authorize.net has changed their CA for test.authorize.net and attempts to connect there with zc.authorizedotnet currently fail. The key that's needed is at the end of this message. Thanks! Kevin -BEGIN CERTIFICATE- MIIE2DCCBEGgAwIBAgIEN0rSQzANBgkqhkiG9w0BAQUFADCBwzELMAkGA1UEBhMC VVMxFDASBgNVBAoTC0VudHJ1c3QubmV0MTswOQYDVQQLEzJ3d3cuZW50cnVzdC5u ZXQvQ1BTIGluY29ycC4gYnkgcmVmLiAobGltaXRzIGxpYWIuKTElMCMGA1UECxMc KGMpIDE5OTkgRW50cnVzdC5uZXQgTGltaXRlZDE6MDgGA1UEAxMxRW50cnVzdC5u ZXQgU2VjdXJlIFNlcnZlciBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05OTA1 MjUxNjA5NDBaFw0xOTA1MjUxNjM5NDBaMIHDMQswCQYDVQQGEwJVUzEUMBIGA1UE ChMLRW50cnVzdC5uZXQxOzA5BgNVBAsTMnd3dy5lbnRydXN0Lm5ldC9DUFMgaW5j b3JwLiBieSByZWYuIChsaW1pdHMgbGlhYi4pMSUwIwYDVQQLExwoYykgMTk5OSBF bnRydXN0Lm5ldCBMaW1pdGVkMTowOAYDVQQDEzFFbnRydXN0Lm5ldCBTZWN1cmUg U2VydmVyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIGdMA0GCSqGSIb3DQEBAQUA A4GLADCBhwKBgQDNKIM0VBuJ8w+vN5Ex/68xYMmo6LIQaO2f55M28Qpku0f1BBc/ I0dNxScZgSYMVHINiC3ZH5oSn7yzcdOAGT9HZnuMNSjSuQrfJNqc1lB5gXpa0zf3 wkrYKZImZNHkmGw6AIr1NJtl+O3jEP/9uElY3KDegjlrgbEWGWG5VLbmQwIBA6OC AdcwggHTMBEGCWCGSAGG+EIBAQQEAwIABzCCARkGA1UdHwSCARAwggEMMIHeoIHb oIHYpIHVMIHSMQswCQYDVQQGEwJVUzEUMBIGA1UEChMLRW50cnVzdC5uZXQxOzA5 BgNVBAsTMnd3dy5lbnRydXN0Lm5ldC9DUFMgaW5jb3JwLiBieSByZWYuIChsaW1p dHMgbGlhYi4pMSUwIwYDVQQLExwoYykgMTk5OSBFbnRydXN0Lm5ldCBMaW1pdGVk MTowOAYDVQQDEzFFbnRydXN0Lm5ldCBTZWN1cmUgU2VydmVyIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MQ0wCwYDVQQDEwRDUkwxMCmgJ6AlhiNodHRwOi8vd3d3LmVu dHJ1c3QubmV0L0NSTC9uZXQxLmNybDArBgNVHRAEJDAigA8xOTk5MDUyNTE2MDk0 MFqBDzIwMTkwNTI1MTYwOTQwWjALBgNVHQ8EBAMCAQYwHwYDVR0jBBgwFoAU8Bdi E1U9s/8KAGv7UISX8+1i0BowHQYDVR0OBBYEFPAXYhNVPbP/CgBr+1CEl/PtYtAa MAwGA1UdEwQFMAMBAf8wGQYJKoZIhvZ9B0EABAwwChsEVjQuMAMCBJAwDQYJKoZI hvcNAQEFBQADgYEAkNwwAvpkdMKnCqV8IY00F6j7Rw7/JXyNEwr75Ji174z4xRAN 95K+8cPV1ZVqBLssziY2ZcgxxufuP+NXdYR6Ee9GTxj005i7qIcyunL2POI9n9cd 2cNgQ4xYDiKWL2KjLB+6rQXvqzJ4h6BUcxm1XAX5Uj5tLUUL9wqT6u0G+bI= -END CERTIFICATE- ___ 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] paver and buildout
Hi, So, I saw Martijn's paver: buildout is utterly doomed message on Tuesday, but I haven't had a chance to respond to it until now. As Kent points out immediately following, I plan to use zc.buildout's machinery. I actively use zc.buildout now, and I'm looking forward to getting my buildout merged into my pavement.py. I totally agree with Martijn that buildout needs a better website and I'm glad to see that Baiju is going forward with that. Ultimately, though, I think that people will choose to use buildout alone or paver+buildout (or maybe paver+virtualenv, depending on their tastes) completely based on what fits their brains better. I emailed a fair bit with Zed Shaw about his Vellum tool. He adamantly opposes having his builds defined in a full-blown language (ie Python), whereas for my needs I really want to define my builds in Python. But I want it to be easier to do than what you get with the Python standard library. People who prefer to keep there build information in a data format will no doubt stick with buildout. I have no problem with that. My goal is just to share the workload with other people who have similar build and deployment problems to the ones I have. Kevin ___ 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.4 available as packages based on setuptools tarballs
On Wednesday 23 April 2008, Marius Gedminas wrote: Okay, so I think we should use the KGS and declare the set of packages in there as Zope 3.4.0. The KGS changes from time to time, doesn't it? Do you mean the set of packages frozen at this moment in time? No, when we do a release, I provide frozen versions of the KGS. See: http://download.zope.org/zope3.4/intro.html Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ 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: new zope.org, sphinx, and documentation management
On Thu, Apr 24, 2008 at 2:09 AM, Paul Carduner [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 10:48 PM, Paul Carduner [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 12:01 PM, Martin Aspeli [EMAIL PROTECTED] wrote: I would start with the simple HTML approach, personally. It may be all we need. Hopefully there will be a first sample of this in the next hour or so. Ok, I setup a sample of what sphinx produces after a quite minimal setup for z3c.form. Check it out at: http://docs.carduner.net/z3c.form/. I made a few small modifications to the existing documentation, which I checked into a branch on svn.zope.org along with the sphinx setup generated for me by the sphinx-quickstart command. A few goody features include: Full text searching powered by javascript: http://docs.carduner.net/z3c.form/search.html Module index with quick synopses: http://docs.carduner.net/z3c.form/modindex.html (click on the plus symbol after the big Z) Cross links to other parts of the documentation: http://docs.carduner.net/z3c.form/src/z3c/form/README.html So far, I think this is pretty good for what took me maybe an hour. Think of what it would be with some extra documentation cleanup. Cool!. The Zope-3.3.1 tree contains 70 README.txt, 309 *.txt so, more than 70 files of correct, up to the minute examples of use. That's a lotta doc. If not adequate in themselves, invaluable as link destinations when explaining with prose. As they grow ..contents:: directives, and more section headings are added, glossary tags are added, they will increase in value. -- Paul Carduner http://www.carduner.net ___ 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 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.4 available as packages based on setuptools tarballs
Okay, so I think we should use the KGS and declare the set of packages in there as Zope 3.4.0. The KGS changes from time to time, doesn't it? Do you mean the set of packages frozen at this moment in time? No, when we do a release, I provide frozen versions of the KGS. See: http://download.zope.org/zope3.4/intro.html Regards, Stephan Hi, I'd just like to use the oportunity and point out a few small problems with packages in the current KGS... I understand that zope.app.traversing is deprecated, but still - i think it should depend on zope.traversing (it does not have any dependencies at the moment), because else just installing zope.app.traversing will give you import errors not deprecation warnings. z3c.breadcrumb-1.0.2 z3c.formjs-0.3.0 z3c.form-1.8.0 z3c.formui-1.4.1 have http://download.zope.org/distribution in their dependency links, which I think is not a very good idea. zope.server 3.4 does not have a proper entry point for wsgi server defined, so PPA has zope.server 3.5 Other than that everything seems to be working fine. Thanks for all the work you did on KGS, it really helped us to get our zope3 dependencies packaged in a usable state for ubuntu ... If someone will want to release a Zope3 based application on ubuntu - schooltool-common and schooltool-2008 are probably the packages that should be looked at to find out how to get a paste based server using an entry point defined in your egg. Ignas ___ 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: new zope.org, sphinx, and documentation management
Hi Paul. This is beautiful. A recipe is what we need now. Send me a mail off list if you want some help with this. Regards, David Kent Tenney wrote: On Thu, Apr 24, 2008 at 2:09 AM, Paul Carduner [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 10:48 PM, Paul Carduner [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 12:01 PM, Martin Aspeli [EMAIL PROTECTED] wrote: I would start with the simple HTML approach, personally. It may be all we need. Hopefully there will be a first sample of this in the next hour or so. Ok, I setup a sample of what sphinx produces after a quite minimal setup for z3c.form. Check it out at: http://docs.carduner.net/z3c.form/. I made a few small modifications to the existing documentation, which I checked into a branch on svn.zope.org along with the sphinx setup generated for me by the sphinx-quickstart command. A few goody features include: Full text searching powered by javascript: http://docs.carduner.net/z3c.form/search.html Module index with quick synopses: http://docs.carduner.net/z3c.form/modindex.html (click on the plus symbol after the big Z) Cross links to other parts of the documentation: http://docs.carduner.net/z3c.form/src/z3c/form/README.html So far, I think this is pretty good for what took me maybe an hour. Think of what it would be with some extra documentation cleanup. Cool!. The Zope-3.3.1 tree contains 70 README.txt, 309 *.txt so, more than 70 files of correct, up to the minute examples of use. That's a lotta doc. If not adequate in themselves, invaluable as link destinations when explaining with prose. As they grow ..contents:: directives, and more section headings are added, glossary tags are added, they will increase in value. -- Paul Carduner http://www.carduner.net ___ 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 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 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] paver: buildout is utterly doomed
Hey, On Thu, Apr 24, 2008 at 5:52 AM, Baiju M [EMAIL PROTECTED] wrote: [snip] We will be using Sphinx for the site. It will require: 1. Python 2.4 2. Sphinx 3. docutils 4. Pygments Strictly speaking only the person who generates the documentation would need Sphinx, as I think it generates HTML that can be uploaded to the server, correct? So I assume to generate the HTML, you'd get a buildout that installs sphinx and pulls in zc.buildout as an external for its documentation (which we'd also want to use), and then have something that points sphinx to all the documents that we want to publish. Other documentation would be in the checkout directly. The whole documentation package can be maintained on svn.zope.org itself. Regards, Martijn ___ 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
On Apr 24, 2008, at 1:12 AM, Christian Theune wrote: Hi, On Wed, Apr 23, 2008 at 04:47:59PM -0400, Jim Fulton wrote: On Apr 23, 2008, at 4:47 PM, Marius Gedminas wrote: ... The point of my message was not to whine about the state of zope.testing, but to present a new argument against the current fashion of using plain-text narrative doctests for everything. Except that that is not the current fashion, which has been pointed out many times in many places. For my own record (I must have missed this many times in many places), is the current fashion something along the lines: Use the various test styles as reasonable, text-file narrative doctests are preferred. No. WRT doc tests: - If a file is documentation and a test, make sure it is good documentation. In that case, documentation comes first. Don't add so many tests that it ruins the documentation. - Test edge cases in separate tests. These are typically short-ish strings in test modules. - A variation is to have a narrative that doesn't try hard to be documentation. The narrative can be convenient, up to a point, even in a test. These should be clearly marked as not being documentation. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZConfig 2.5.1 test failures
On Wed, 2008-04-23 at 22:38 +0300, Marius Gedminas wrote: By the way, the usual way to run tests in the Zope-3-land is to use bin/test rather than setup.py test. It uses a slightly different test runner that uses a slightly different method of getting the test description and therefore hides this incompatibility. Which probably explains why nobody saw it before. On the other hand, compatibility with setup.py test is desirable, and this bug should be fixed. I assume bin/test is part of zope.testing... If so (I'm going to be installing it soon) how would I go about running the tests then? The ultimate goal of what I'm working on is packaging ZODB3, and I've been working my way through the dependencies. Do all of the zope-ish packages use zope.testing? I'd like to be able to include tests in %check, as I don't usually get to test the built packages right-a-way and this would at least show that it passes basic scrutiny. Also, what was the rationale in making zope.testing instead of just using unittest. Does it extend unittest in a more zope-ish way (similarly for zope.buildout in regards to setuptool)? I'm just trying to understand the dynamics of the zope and python communities so I know areas to focus my attention. https://bugs.launchpad.net/zope.testing/+bug/221151 The next step would be to write a unit test to reproduce this in zope.testing's test suite. Thanks for submitting that bug. I'll look into writing a unit test based on the one that uses zope.testing, but while I understand the concepts of writing unit tests, I'm really just a n00b when it comes to all of this. I find that I learn the best by jumping straight in, feet first (not head first...broken legs are easier to deal with than a broken neck ;) --Tim If only I could be respected without having to be respectable. \ \ \ \ /\ ( ) .( o ). ___ 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: paver and buildout
Hey, Kevin Dangoor wrote: So, I saw Martijn's paver: buildout is utterly doomed message on Tuesday, but I haven't had a chance to respond to it until now. I knew you'd find out. :) As Kent points out immediately following, I plan to use zc.buildout's machinery. I actively use zc.buildout now, and I'm looking forward to getting my buildout merged into my pavement.py. Yes, I hadn't seen this until after I wrote that message. I'm glad to hear so! There are packaging and distribution problems that both projects share too, and I hope eventually some solutions to these problems can go into setuptools. If you're interested in hearing more about the problems we've been experiencing I'd be happy to talk about this more. I totally agree with Martijn that buildout needs a better website and I'm glad to see that Baiju is going forward with that. Ultimately, though, I think that people will choose to use buildout alone or paver+buildout (or maybe paver+virtualenv, depending on their tastes) completely based on what fits their brains better. While I fully agree that's an important factor, presentation counts too. Zope's attention to good presentation has been, let's say, lacking. I was rather empathic, deliberately. I emailed a fair bit with Zed Shaw about his Vellum tool. He adamantly opposes having his builds defined in a full-blown language (ie Python), whereas for my needs I really want to define my builds in Python. But I want it to be easier to do than what you get with the Python standard library. People who prefer to keep there build information in a data format will no doubt stick with buildout. I have no problem with that. My goal is just to share the workload with other people who have similar build and deployment problems to the ones I have. I can certainly see benefits to both approaches, and I think there's enough room to support both. But I think better presentation and speaking to Python programmers matters so much I think zc.buildout stands rather weakly in competition with Paver right now. This needs to be improved. What I like about buildout's recipe approach is that it creates an ecosystem of reusable recipes, and gets people to think about declarative ways to get things done. If you could've gotten your problem solved by writing 5 lines of python, the recipe might not be around. On the other hand, the benefit is that you'd be done after 5 lines of Python. :) I believe I read somewhere about Paver having a goal to have projects install directly from PyPI (with a single command), is that correct? That would be interesting. Regards, Martijn ___ 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] Buildout Builder: Call for Ideas.
All, My name is Kenneth Miller and I am a student of Electronics Engineering Technology at the University of Houston. My proposal for the buildout builder has been selected for the Google Summer of Code program. You can read my proposal, a list of general deliverables and a development schedule at xkenneth.blogspot.com. I feel that from my experience with buildout and Plone, that I have a good but general idea of what the Buildout Builder should be. I know what I expect of it, but as I begin the in depth planning of this project I'd like to know what the community expects of it. Any and all feedback is appreciated and I will carefully consider every idea. My goal is to prepare a detailed list of key features and development goals in order to ensure that my time is spent as efficiently as possible and that the community gets the quality project they deserve. Regards, Kenneth Miller ___ 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 )
