Tarek Ziadé wrote:
Last, as I said in a previous mail, I tend to agree with the people
who said that we should stick with only one way to write the version
scheme for the sake of clarity. e.g. dropping aliases and picking
*one* way to write the markers after major.minor.micro.
I would tend
On Thu, Dec 03, 2009 at 01:55:53PM +0100, M.-A. Lemburg wrote:
Tarek Ziadé wrote:
Last, as I said in a previous mail, I tend to agree with the people
who said that we should stick with only one way to write the version
scheme for the sake of clarity. e.g. dropping aliases and picking
On Thu, Dec 3, 2009 at 1:55 PM, M.-A. Lemburg m...@egenix.com wrote:
Tarek Ziadé wrote:
Last, as I said in a previous mail, I tend to agree with the people
who said that we should stick with only one way to write the version
scheme for the sake of clarity. e.g. dropping aliases and picking
Tarek Ziadé wrote:
On Thu, Dec 3, 2009 at 1:55 PM, M.-A. Lemburg m...@egenix.com wrote:
Tarek Ziadé wrote:
Last, as I said in a previous mail, I tend to agree with the people
who said that we should stick with only one way to write the version
scheme for the sake of clarity. e.g. dropping
Toshio Kuratomi wrote:
On Thu, Dec 03, 2009 at 01:55:53PM +0100, M.-A. Lemburg wrote:
Tarek Ziadé wrote:
Last, as I said in a previous mail, I tend to agree with the people
who said that we should stick with only one way to write the version
scheme for the sake of clarity. e.g. dropping
[..]
1. whether it's release quality code
1.0.0
2. whether it's a development snapshot
1.0.0a0.20091202
3. whether it's working code, but still under development
1.0.0a1
4. whether it fixes some bug that was found after a release
1.0.1
How do you
Tarek Ziadé wrote:
[..]
1. whether it's release quality code
1.0.0
2. whether it's a development snapshot
1.0.0a0.20091202
3. whether it's working code, but still under development
1.0.0a1
4. whether it fixes some bug that was found after a release
1.0.1
On Dec 3, 2009, at 4:46 AM, David Cournapeau wrote:
The way I
would do it is by having akara distutils extensions, which define in
particular a setup function and associated classes.
...
If you think this is insane, you are not alone :)
Wow. That's just crazy, I say - crazy.
I
On Thu, Dec 03, 2009 at 04:50:50PM +0100, M.-A. Lemburg wrote:
The dev markers introduce an extra level of confusion, which
IMHO is not necessary.
Let's take 1.0a0.dev123 as example, reading it from the left:
1.0 - ok, so this is part of a 1.0 release
1.0a0- oops, no,
I thought this list might be of interest to the people here.
Surprisingly not many packages rely on (not declare) setuptools'
extras feature [bit.ly/setuptools-extras].
http://paste.pocoo.org/raw/154703/
-srid
___
Distutils-SIG maillist -
I know at least one package not in your list: zope.component [1].
[1] - http://svn.zope.org/zope.component/trunk/setup.py?rev=105736view=markup
Sridhar Ratnakumar a écrit :
I thought this list might be of interest to the people here.
Surprisingly not many packages rely on (not declare)
On Thu, Dec 3, 2009 at 1:05 PM, kiorky kio...@cryptelium.net wrote:
I know at least one package not in your list: zope.component [1].
Indeed. Many z3c.* and zope.* packages provide extras that aren't
referenced by other packages directly, but are referenced from
buildout configurations or
Hi,
On Thu, Dec 3, 2009 at 19:05, kiorky kio...@cryptelium.net wrote:
I know at least one package not in your list: zope.component [1].
It does have a few extras (zcml being the most notable one probably),
but I don't think it depends on any extras. Other packages may,
however, depend on
Attila Oláh a écrit :
It does have a few extras (zcml being the most notable one probably),
but I don't think it depends on any extras. Other packages may,
however, depend on zope.component [zcml].
There are many, and as i say, and i know many others packages using extras which
are not yet in
On 12/3/2009 10:16 AM, kiorky wrote:
Attila Oláh a écrit :
It does have a few extras (zcml being the most notable one probably),
but I don't think it depends on any extras. Other packages may,
however, depend on zope.component [zcml].
There are many, and as i say, and i know many others
At 01:06 AM 12/3/2009 +0100, Andrew Dalke wrote:
Hi all,
I'm working with the Akara project. It contains a web server. The
server loads extensions from a special directory (let's say
$AKARA for now). An extension can register handlers for URLs. An
example extension might look like:
At 10:21 AM 12/3/2009 -0800, Sridhar Ratnakumar wrote:
Do you have anything particular in mind? What I did was a ``grep
^.*[a-zA-Z]\[`` in the requires.txt of (almost) all the packages in PyPI.
Do note that this won't tell you about end users' use of extras.
The main use case described in
On Thu, Dec 3, 2009 at 1:06 AM, Andrew Dalke da...@dalkescientific.com wrote:
Hi all,
I'm working with the Akara project. It contains a web server. The server
loads extensions from a special directory (let's say $AKARA for now). An
extension can register handlers for URLs. An example
On Thu, Dec 3, 2009 at 20:05, P.J. Eby p...@telecommunity.com wrote:
At 10:21 AM 12/3/2009 -0800, Sridhar Ratnakumar wrote:
Do you have anything particular in mind? What I did was a ``grep
^.*[a-zA-Z]\[`` in the requires.txt of (almost) all the packages in PyPI.
Do note that this won't tell
Hi All,
Say I have a package, mortar, that offers multiple extras options for
different data storage mechanisms, eg: sqlalchemy, zodb, simpledb
If I want to use this in a project and want both the sqlalchemy and zodb
backends, how do I spell this?
easy_install mortar[sqlalchemy,zodb]
On Thu, Dec 3, 2009 at 1:05 PM, P.J. Eby p...@telecommunity.com wrote:
At 10:21 AM 12/3/2009 -0800, Sridhar Ratnakumar wrote:
Do you have anything particular in mind? What I did was a ``grep
^.*[a-zA-Z]\[`` in the requires.txt of (almost) all the packages in PyPI.
Do note that this won't
Wouldn't it require zope.component to be a namespace package? Extras
allw you to add extra files (subpackages) withot making the container
package a namespace-package, it seems to me.
On 12/3/09, Ian Bicking i...@colorstudy.com wrote:
On Thu, Dec 3, 2009 at 1:05 PM, P.J. Eby
At 08:25 PM 12/3/2009 +, Chris Withers wrote:
Hi All,
Say I have a package, mortar, that offers multiple extras options
for different data storage mechanisms, eg: sqlalchemy, zodb, simpledb
If I want to use this in a project and want both the sqlalchemy and
zodb backends, how do I spell
At 09:53 PM 12/3/2009 +0100, Attila Oláh wrote:
Wouldn't it require zope.component to be a namespace package? Extras
allw you to add extra files (subpackages) withot making the container
package a namespace-package, it seems to me.
No, they don't. Extras just cause a project to pull in
On Thu, Dec 3, 2009 at 3:21 PM, P.J. Eby p...@telecommunity.com wrote:
At 09:53 PM 12/3/2009 +0100, Attila Oláh wrote:
Wouldn't it require zope.component to be a namespace package? Extras
allw you to add extra files (subpackages) withot making the container
package a namespace-package, it
P.J. Eby wrote:
If I want to use this in a project and want both the sqlalchemy and
zodb backends, how do I spell this?
easy_install mortar[sqlalchemy,zodb]
Just like that.
Cool :-)
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
-
Hi,
I recently implemented a plugin system using setuptools, and now I'm wondering
how to enumerate the packages contained in a given Distribution object.
What I'm doing is basically this:
I use egg files as self-describing plugins to allow users to distribute
plugins containing several
Tarek Ziadé wrote:
where package.spam_extension and spam_extension2 are modules Akara
would simply __import__()
Meaning a plugin will be a normal project that gets installed, and
then configured to be used in Akara.
This solution is simpler, but it does not solve the issue of installing
28 matches
Mail list logo
