Thread: [Pythius-developers] aop module as separate package

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

A thought: it might be advisable to put out the aop.py module as a
separate package of Pythius.  Kinda like a 'subproject' of Pythius.

-- 
Frank Tobin		http://www.neverending.org/~ftobin/

On Tue, 18 Dec 2001 23:24:56 -0500 (EST), Frank Tobin wrote:

>A thought: it might be advisable to put out the aop.py module as a
>separate package of Pythius.  Kinda like a 'subproject' of Pythius.

I see absolutely no problem in making it a subpackage of pythius 
(pythius/pythius/aop/__init__.py). Feel free to do anything in that 
respect (but do not forget to add your new subpackage to setup.py).

If you think of either creating a second top-level package, or even an 
own CVS module, that opens a can of worms regarding packaging and stuff =

that I'd want to discuss before it happens.

Ciao, J=FCrgen

Juergen Hermann, at 05:58 +0100 on 2001-12-19, wrote:

> >A thought: it might be advisable to put out the aop.py module as a
> >separate package of Pythius.  Kinda like a 'subproject' of Pythius.
>
> I see absolutely no problem in making it a subpackage of pythius
> (pythius/pythius/aop/__init__.py). Feel free to do anything in that
> respect (but do not forget to add your new subpackage to setup.py).
>
> If you think of either creating a second top-level package, or even an
> own CVS module, that opens a can of worms regarding packaging and stuff
> that I'd want to discuss before it happens.

More of, I'd like to release the aop.py separately as a package; is the
setup.py scheme stuff capable of handling a 'subpackage' in that respect?

-- 
Frank Tobin		http://www.neverending.org/~ftobin/

On Wed, 16 Jan 2002 17:52:50 -0500 (EST), Frank Tobin wrote:

>More of, I'd like to release the aop.py separately as a package; is the=

>setup.py scheme stuff capable of handling a 'subpackage' in that respec=
t?

No clue, never needed that. And I don't really see a reason for the 
separate distro. After all, people can always ignore what they do not ne=
ed, 
IMHO it just adds confusion to rip apart things.

Ciao, J=FCrgen

Juergen Hermann, at 00:15 +0100 on 2002-01-17, wrote:

> No clue, never needed that. And I don't really see a reason for the
> separate distro. After all, people can always ignore what they do not
> need, IMHO it just adds confusion to rip apart things.

The reason I ask is because the aop.py module is fairly completed, but the
rest Pythius has stagnated, preventing a release.  I'd like to get a
release of the aop.py out, so that I can get comments back on its
usefulness, bugs, etc.

-- 
Frank Tobin		http://www.neverending.org/~ftobin/

On Wed, 16 Jan 2002 18:17:51 -0500 (EST), Frank Tobin wrote:

>Juergen Hermann, at 00:15 +0100 on 2002-01-17, wrote:
>
>> No clue, never needed that. And I don't really see a reason for the
>> separate distro. After all, people can always ignore what they do not=

>> need, IMHO it just adds confusion to rip apart things.
>
>The reason I ask is because the aop.py module is fairly completed, but =
the
>rest Pythius has stagnated, preventing a release.  I'd like to get a
>release of the aop.py out, so that I can get comments back on its
>usefulness, bugs, etc.

Just do a full release.

Ciao, J=FCrgen

Juergen Hermann, at 01:02 +0100 on 2002-01-17, wrote:

> Just do a full release.

I'm not sure what you mean.  The only releases I've done of Python modules
are with my GnuPGInterface module (py-gnupg project on SF), where I have a
setup.py, and other metadata files (NEWS, MANIFEST, README, etc) along
with the actual module.

Do you mean: 'Do a full release of Pythius'?

-- 
Frank Tobin		http://www.neverending.org/~ftobin/

Thread: [Pythius-developers] aop module as separate package

pythius-developers