Re: [Zope3-dev] Re: [Zope Package Dependencies] This is just an experimental page

[Jim Fulton]

On Feb 20, 2007, at 10:48 PM, Baiju M wrote:


Jim Fulton wrote:

...


- I used a separate test extra to capture test dependencies.


Why we requires these two:

 tests_require = ['zope.testing'],
 extras_require = dict(

test = ['zope.testing'], ),


Let's use 'tests_require' for test requirements and  
'extras_require' for other requirements ?


tests_require doesn't really do anything.  It is used solely by  
setuptools at setup time.  It doesn't create any meta data that can  
be used by any other test runner, like ours.  IMO, it is useless.   
See the discussion of this a while back on the distutils sig mailing  
list.


- The zcml support currently causes a dependency on all of zope. :  
( This makes it impossible to run the tests for the zcml support   
without a zope checkout.  We need to fix this.


May be I can help, any pointer to start?


The easiest way to start is to try creating package buildouts that  
don't use a Zope checkout and seeing if you can make them work.  For  
example, check out the zope.component buildout, modify it so that it  
doesn't exclude the zcml tests, and see if you can get the tests to  
pass.  You'll notice that:


- zope.security should list zope.location as a depenency

- you'll end up with a depenency on zope.app.container, which doesn't  
exist as an egg or project.


When these are fixed, there are probably lots of other issues.






What do people think of using extras this way?  I think it makes  
a  lot os sense for tests.



As I said above, use 'extras_require' for other requirements and  
'tests_require' only for test requirements?


I think we're at the point now where we actually need to try and make  
things work.  If you do, you'll discover, as I did a few weeks ago,  
that tests_require doesn't do anything useful.


I would *greatly* appreciate it if you could work with Alex Heavner.  
He's now working on getting the zc.sharing buildout working without a  
zope3 checkout.  He's starting with the tests.  He could really use  
some help and I'll be at PyCon for the next few days. Note that  
Alex's initial goal is to get this working without getting the  
dependencies right. He's just listing all of the eggs you and he have  
made and trying to get the tests to pass.


Jim

--
Jim Fulton  mailto:[EMAIL PROTECTED]Python 
Powered!
CTO (540) 361-1714  
http://www.python.org
Zope Corporationhttp://www.zope.com http://www.zope.org



___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Re: [Zope3-dev] Re: [Zope Package Dependencies] This is just an experimental page

[Baiju M]

Jim Fulton wrote:



I don't know how to interpret this note.  Are you suggesting that  
these should be the dependencies?  I don't know what the relevence of  
the "flat is better than nested" quote or of the indentation in the  
list below. (Perhaps that was an accidental result of using tabs.



I was starting to think about reducing dependencies.  I used 
`src/utilities/finddeps.py` to find dependencies.
Later I will classify those dependencies as you said below 
(install_requires, tests_require and extras_require).
That quote is added as motivation for me :)  Now I have enough 
motivation, so I will remove it :)




In any case, look at what I did to zope.component.  In particular,  
see the use of extras to try to limit and segment the dependencies.


  http://svn.zope.org/zope.component/trunk/setup.py?rev=72722&view=auto


+1

I think we can follow this line.



Yes, I've commented some dependencies for the moment because they  
aren't currently realizable. :(


There are a few things to note:

- I need zope.component to be easily installable now. :)  In  
particular, for a course I'm teaching at PyCon on Tuesday.


This is a requirement for me also for 2nd March at FOSS.NITC : 
http://www.foss.nitc.ac.in

I will be talking about Zope Component Architecture, I have 2 hour time,
but the audience may not be Python programmers :(
Any advise ?



- I used a separate test extra to capture test dependencies.


Why we requires these two:

 tests_require = ['zope.testing'],
 extras_require = dict(

test = ['zope.testing'], ),


Let's use 'tests_require' for test requirements and 'extras_require' for 
other requirements ?




- The zcml support currently causes a dependency on all of zope. : ( 
This makes it impossible to run the tests for the zcml support  
without a zope checkout.  We need to fix this.


May be I can help, any pointer to start?



What do people think of using extras this way?  I think it makes a  
lot os sense for tests.



As I said above, use 'extras_require' for other requirements and 
'tests_require' only for test requirements?


Regards,
Baiju M

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com