On 7 Sep, 2009, at 14:15, Chris Withers wrote:
I'd prefer setup.cfg to be totally static. If there are complicated
if/then/else's needed, they should be in setup.py.
I have a number of packages where the only logic on setup.py is set
flags based on the python version or OS. Examples:
*
Ronald Oussoren wrote:
I have a number of packages where the only logic on setup.py is set
flags based on the python version or OS. Examples:
* depend on pysqlite in old versions of python where sqlite wasn't in
the stdlib
mini rant
If Python had a packaging system *and* used it for the
2009/9/8 Chris Withers ch...@simplistix.co.uk:
I agree that the file shouldn't be too dynamic, we don't need a full
programming language in setup.cfg because we already have setup.py files.
It's an extremely slippery slope, as soon as there's any possibility for
weirdness some inexperienced
Tarek Ziadé wrote:
- an extra function called long_description, to be able to point a
file for the long description field
I can't comment on the others, but this is unnecessary. Why do you need
more than:
long_decription=some lump of text
or
long_description_path
On 2009-09-05, Zooko Wilcox-O'Hearn zo...@zooko.com wrote:
On Wednesday,2009-09-02, at 7:07 , Reinout van Rees wrote:
First things first: what I want to accomplish is to install
pyflakes and docutils in a buildout. That is, I want to have a bin/
pyflakes and bin/rst2* scripts.
See also
On 8 Sep, 2009, at 10:18, Chris Withers wrote:
Ronald Oussoren wrote:
I have a number of packages where the only logic on setup.py is set
flags based on the python version or OS. Examples:
* depend on pysqlite in old versions of python where sqlite wasn't
in the stdlib
mini rant
If
On Mon, Sep 07, 2009 at 05:41:40PM +0200, Tarek Ziadé wrote:
The template engine will be restricted to if, and the expression
will be able to ^may only 3 values:
- the python version
- sys.platform
- os.name
The members of the structure/named-tuple returned os.uname() too
please, otherwise
Hi Tarek,
Tarek Ziadé wrote:
I am pleased to announce the release of Distribute 0.6.
Distribute is a friendly fork of the Setuptools project.
You can get more info, download it and install it using the
instructions from its PyPI page :
http://pypi.python.org/pypi/distribute
I've been
On Tue, Sep 8, 2009 at 12:04 PM, Chris Withersch...@simplistix.co.uk wrote:
Hi Tarek,
Hi Chris,
I've been working on a branch of zc.buildout that uses distribute instead of
setuptools:
http://svn.zope.org/zc.buildout/branches/use_distribute/
...and I've hit a problem at the first
David Lyon wrote:
On Tue, 08 Sep 2009 09:18:50 +0100, Chris Withers ch...@simplistix.co.uk
wrote:
mini rant
If Python had a packaging system *and* used it for the standard library,
then things like this wouldn't be a problem...
The setup.cfg could just say requires sqlite greater than version
On Tue, Sep 8, 2009 at 10:29 AM, Chris Withersch...@simplistix.co.uk wrote:
Tarek Ziadé wrote:
- an extra function called long_description, to be able to point a
file for the long description field
I can't comment on the others, but this is unnecessary. Why do you need more
than:
Tarek Ziadé wrote:
On Tue, Sep 8, 2009 at 10:29 AM, Chris Withersch...@simplistix.co.uk wrote:
Tarek Ziadé wrote:
- an extra function called long_description, to be able to point a
file for the long description field
I can't comment on the others, but this is unnecessary. Why do you need more
On Tue, Sep 8, 2009 at 2:32 PM, Eric Smithe...@trueblade.com wrote:
Tarek Ziadé wrote:
On Tue, Sep 8, 2009 at 10:29 AM, Chris Withersch...@simplistix.co.uk
wrote:
Tarek Ziadé wrote:
- an extra function called long_description, to be able to point a
file for the long description field
I
Chris Withers wrote:
David Lyon wrote:
On Tue, 08 Sep 2009 09:18:50 +0100, Chris Withers
ch...@simplistix.co.uk
wrote:
mini rant
If Python had a packaging system *and* used it for the standard
library, then things like this wouldn't be a problem...
The setup.cfg could just say requires
On Tue, Sep 8, 2009 at 3:49 PM, Chris Withersch...@simplistix.co.uk wrote:
Tarek Ziadé wrote:
I've been working on a branch of zc.buildout that uses distribute instead
of
setuptools:
http://svn.zope.org/zc.buildout/branches/use_distribute/
Okay, I now have all but a couple of tests
Tarek Ziadé wrote:
This is probably zc.buildout setup.py script because it contains
install_requires = 'setuptools',
Not on my branch it doesn't...
That's why you need to install Distribute using distribute_setup.py
for instance,
Which my branch does...
My be worth taking a look at the
Hi All,
Thought I'd try and help Reinout van Rees out by running the tests on
his branch on Windows, but found problems even when trying to run the
tests on trunk:
- running dev.py failed on Windows, I've fixed this in r103647
- Even so, running dev.py with Python 2.6 on Windows pops up a
Hi All,
Sphinx, among others, provides command in this entry point.
With this buildout:
[buildout]
parts = sphinx
[sphinx]
recipe = zc.recipe.egg
eggs = sphinx
And based on the entry points listed here:
http://bitbucket.org/birkenfeld/sphinx/src/447109cf9b01/setup.py#cl-182
I'd expect to
On 2009-09-08, Chris Withers ch...@simplistix.co.uk wrote:
Reinout van Rees wrote:
Chris, you could try out the zc.buildout/branches/reinout-scripts branch.
I've fixed it there.
How do I actually go about doing that?
If I just put that checkout in the develop line of my buildout will get
On 2009-09-08, Chris Withers ch...@simplistix.co.uk wrote:
Thought I'd try and help Reinout van Rees out by running the tests on
his branch on Windows
:-) Thanks
- There are test failures with Python 2.6 on Windows, I've attached the
full run in windows.txt.
I noticed two things:
-
On Tue, Sep 08, 2009 at 02:53:49PM +0200, Tarek Ziadé wrote:
On Tue, Sep 8, 2009 at 2:32 PM, Eric Smithe...@trueblade.com wrote:
Tarek Ziadé wrote:
On Tue, Sep 8, 2009 at 10:29 AM, Chris Withersch...@simplistix.co.uk
wrote:
Tarek Ziadé wrote:
- an extra function called
Hi!
I'm happy to announce the release of virtualenv-distribute 1.3.4dev-1,
which is a fork of virtualenv which uses distribute 0.6.1 instead of
setuptools.
Any feedback welcome.
Regards,
Florian Schulze
___
Distutils-SIG maillist -
On 2009-09-08, Chris Withers ch...@simplistix.co.uk wrote:
Hi All,
Sphinx, among others, provides command in this entry point.
With this buildout:
[buildout]
parts = sphinx
[sphinx]
recipe = zc.recipe.egg
eggs = sphinx
And based on the entry points listed here:
On Tue, Sep 8, 2009 at 11:20 PM, Tarek Ziadéziade.ta...@gmail.com wrote:
Hello
I am happy to announce the release of Distribute 0.6.1.
Changes:
* zip_ok is now True by default.
I mean False of course ;)
___
Distutils-SIG maillist -
Florian Schulze wrote:
I'm happy to announce the release of virtualenv-distribute 1.3.4dev-1,
which is a fork of virtualenv which uses distribute 0.6.1 instead of
setuptools.
Wow, it's a shame this is needed. Did Ian just flat-out refuse to switch
to distribute?
Chris
--
Simplistix -
On Tue, 8 Sep 2009 14:20:30 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
The practice in the community is to create the long_description field
using a separate reStructuredText file
and reaching it in setup.py like this for example:
long_description = open('README.txt').read()
Having a
On Wed, Sep 9, 2009 at 1:31 AM, Tarek Ziadéziade.ta...@gmail.com wrote:
On Wed, Sep 9, 2009 at 1:25 AM, Philip Jenveypjen...@underboss.org wrote:
On Sep 8, 2009, at 2:20 PM, Tarek Ziadé wrote:
Hello
I am happy to announce the release of Distribute 0.6.1.
Excellent!
I've found one
Eric Smith e...@trueblade.com writes:
setup.cfg should be entirely static except for some simple
if-then-else logic involving versions, as Tarek has described earlier.
That is, it should only contain logic that needs to be decided on the
platform where the installation is taking place. This
On Wed, Sep 9, 2009 at 1:25 AM, Philip Jenveypjen...@underboss.org wrote:
On Sep 8, 2009, at 2:20 PM, Tarek Ziadé wrote:
Hello
I am happy to announce the release of Distribute 0.6.1.
Excellent!
I've found one issue: distribute_setup.py uses 2.6's site.USER_SITE.
Right, I'll fix it
On Tue, 8 Sep 2009 10:26:19 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
I am restricting the template language to two expressions: if and
else
The values you can work with in the if and else section will be
restricted to :
- the python version (string)
- the os.name (string)
- the
Ben Finney wrote:
The metadata being discussed is static. What's at issue is how that
metadata should be encoded: in an imperative language (like a Python
program file) or a declarative language (like a ConfigParser file).
I'm not sure that exactly expresses the distinction either.
Depending
Tarek Ziadé wrote:
In that case, if we want to keep a configparser-compatible file, we
need to find another
way to express these if/else parts, which will probably lead to a
complex, non natural
syntax.
Maybe the conditions could be expressed in the
section headers?
[requires platform=linux]
On Wed, 09 Sep 2009 11:31:42 +1200, Greg Ewing
greg.ew...@canterbury.ac.nz
wrote:
Maybe the conditions could be expressed in the
section headers?
[requires platform=linux]
...
[requires platform=win32]:
...
Then it's not so much if-then-else logic as just
tagging parts of the file
33 matches
Mail list logo
