Hi Paul,
I experimented a litle bit.
I removed zope.publisher-3.4.1-py2.4.egg/ and zope.traversing-3.4.0-py2.4.egg/
Then I transfered zope.traversing-3.5.0a1.dev_r78730-py2.4.egg/ and
zope.publisher-3.5.0a1.dev_r78838-py2.4.egg/ from another box where the update
of zcontact was
Dieter Maurer wrote:
Chris Withers wrote at 2007-11-14 09:14 +:
Tres Seaver wrote:
I've never known of transactions in anything to do with setuptools...
I wasn't literally referring to a transaction, in the ZODB sense -- I
meant, install using a separate run of easy_install'.
Unless I'm
On Thursday 15 November 2007, Chris Withers wrote:
Have all the things that have lead to buildout/kgs/etc been brought to
the attention of the distutils sig? This *must* be a problem that all
decent sized python frameworks are facing.
We are still experimenting. I think once we tried our
Summary of messages to the zope-tests list.
Period Wed Nov 14 13:00:00 2007 UTC to Thu Nov 15 13:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Wed Nov 14 20:55:01 EST 2007
Hi All,
Kindof related to the packaging discussion...
How do I get/install the minimum needed to have:
- http/ftp/webdav servers
- url publishing
- security
- component architecture
cheers,
Chris
--
Simplistix - Content Management, Zope Python Consulting
-
On Nov 15, 2007, at 9:35 AM, Tres Seaver wrote:
...
Chris is not advocating switching away from zc.buildout for the
*development* of the packages; he is arguing that we can't force
people
who *use* the packages to stop using the facilities supplied
setuptools.
Agreed,
If we want people
On Nov 15, 2007, at 10:52 AM, Tres Seaver wrote:
...
Gr. I find setup.py test to be really annoying as it requires
meta data that is available only to that command.
Not after running 'egg_info', or any other setuptools-aware command;
the tests_require dependencies then become
Hi All,
How do you go about mapping from old collector issue numbers to new
launchpad ticket numbers?
cheers,
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist -
On Nov 15, 2007 9:35 AM, Tres Seaver [EMAIL PROTECTED] wrote:
- Making sure that the tests can psss for somebody who is not a
core Zope developer, (and therefore who doesn't know about
zc.buildout, or want to). E.g.:
$ /path/to/python setup.py develop
$ /path/to/python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Hi All,
How do you go about mapping from old collector issue numbers to new
launchpad ticket numbers?
You let the www.zope.org redirect you.
Tres.
- --
===
On Nov 15, 2007, at 12:44 PM, Dieter Maurer wrote:
Jim Fulton wrote at 2007-11-15 10:28 -0500:
...
Agreed. I'll note that there is a school of thought that I proposed
but am somewhat ambivalent about that anything required by tests
should also be required by install. This is in accordance
Jim Fulton wrote at 2007-11-15 10:28 -0500:
...
Agreed. I'll note that there is a school of thought that I proposed
but am somewhat ambivalent about that anything required by tests
should also be required by install. This is in accordance with fly
what you test, test what you fly. To the
Previously Fred Drake wrote:
On Nov 15, 2007 9:35 AM, Tres Seaver [EMAIL PROTECTED] wrote:
- Making sure that the tests can psss for somebody who is not a
core Zope developer, (and therefore who doesn't know about
zc.buildout, or want to). E.g.:
$ /path/to/python setup.py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Nov 15, 2007, at 10:52 AM, Tres Seaver wrote:
...
Gr. I find setup.py test to be really annoying as it requires
meta data that is available only to that command.
Not after running 'egg_info', or any other setuptools-aware
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Nov 15, 2007, at 9:35 AM, Tres Seaver wrote:
...
Chris is not advocating switching away from zc.buildout for the
*development* of the packages; he is arguing that we can't force
people
who *use* the packages to stop using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
You are correct: I was misled by the presence of the section for the
'tests' extra. Attached find a patch against the setuptools-0.6 branch
which addes a 'tests_require.txt' file entry point. I will propose that
the patch be
Le Wed, 14 Nov 2007 15:07:33 +0530, Baiju M a écrit :
Hi all,
I started writing a book about Zope Component Architecture.
http://www.muthukadan.net/docs/zca.html
http://www.muthukadan.net/docs/zca.pdf
If you have any suggestions/comments please send it to me.
Great stuff !
Hi there,
I just wrote an article about the ages of Zope and the age I think we
find ourselves in now on my blog. Enjoy, and I'd be happy to hear
comments on it:
http://faassen.n--tree.net/blog/view/weblog/2007/11/15/0
Regards,
Martijn
___
Hi all,
For fun, I just tried to make use of adapters and utilities, registered
with ZCML, in a Pylons application.
I installed Pylons in a virtualenv, and easy_installed zope.component
and zope.interface using the KGS index for 3.4. I used
zope.configuration (also installed) to load a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
Chris McDonough wrote:
Is there an equivalent for tests_require in
buildout.cfg/zc.recipe.testrunner?
The reason I ask is this... currently the zope.18n distribution has
an install_requires that looks something like this:
20 matches
Mail list logo
