At 12:28 AM 8/19/2009 -0400, Glyph Lefkowitz wrote:
What goes in the ... is pretty important. For one thing, I don't
quite understand the implications of this approach.
Basically, anything required in the '...' will be downloaded (and
built if necessary) then dropped into the setup.py
Dear Tarek Ziadé and fellowship of the packaging:
Please pay attention to this issue. If we can extend our build
processes in a modular, re-usable, and testable way then this could
contribute to the success of distutils/setuptools/Distribute.
In particular, I want Nevow to be
At 05:20 PM 8/18/2009 -0600, Zooko Wilcox-O'Hearn wrote:
Dear Tarek Ziadé and fellowship of the packaging:
Please pay attention to this issue.
Did you read the email where I explained how you could solve the problem today?
On Tue, Aug 18, 2009 at 7:20 PM, Zooko Wilcox-O'Hearn zo...@zooko.comwrote:
... and Glyph refuses to accept my patch which fixes it because the fix
isn't testable ...
Hi, Zooko :).
Since this message officially makes me That Jerk Who Is Forcing The Issue,
I've finally joined distutils-sig.
On Sun, Aug 16, 2009 at 8:17 PM, P.J. Eby p...@telecommunity.com wrote:
At 02:16 PM 8/16/2009 -0600, Zooko Wilcox-O'Hearn wrote:
So it appears to me that none of these techniques are both modular/
testable and compatible with distutils/setuptools/Distribute. What
are we to do?
We could
On Sun, 16 Aug 2009 14:16:29 -0600
Zooko Wilcox-O'Hearn zo...@zooko.com wrote:
Folks:
I have a recurring problem with distutils/setuptools/Distribute,
which is that I don't know how to extend the functionality of
setup.py and make the new functionality be testable and modular.
...
At 02:16 PM 8/16/2009 -0600, Zooko Wilcox-O'Hearn wrote:
So it appears to me that none of these techniques are both modular/
testable and compatible with distutils/setuptools/Distribute. What
are we to do?
We could be modular if there was a way to specify pre-setup.py
dependencies.
