distutils2 1.0a4 and simple package

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

distutils2 1.0a4 and simple package

kgk-3
I am trying distutils2 cannot get anything to start.. The doc[1] and [2]
suggest that one should simply

from distutils2.core import setup


However, this does not seem to work anymore.
Is there a newer way, or is it a bug?

Thanks


[1] http://docs.python.org/dev/packaging/
[2]http://packages.python.org/Distutils2/distutils/setupscript.html

--
Kristian G. Kvilekval ([hidden email]) 805-636-1599
_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig
Reply | Threaded
Open this post in threaded view
|

Re: distutils2 1.0a4 and simple package

kgk-3
Thanks for the pointer, is there anyway to use another filename other
than setup.cfg?
I am trying to build several related package from a common root?



On Wed, Mar 21, 2012 at 1:57 PM, Thibault Kruse <[hidden email]> wrote:

> Seems that docu is outdated, as far as I understand the future of disutils2
> is in the setup.cfg instead of a setup.py:
>
> http://docs.python.org/dev/packaging/setupcfg.html
>
> though that doc could probably still be improved a bit.
>
>
> On Wed, Mar 21, 2012 at 1:22 PM, kgk <[hidden email]> wrote:
>>
>> I am trying distutils2 cannot get anything to start.. The doc[1] and [2]
>> suggest that one should simply
>>
>> from distutils2.core import setup
>>
>>
>> However, this does not seem to work anymore.
>> Is there a newer way, or is it a bug?
>>
>> Thanks
>>
>>
>> [1] http://docs.python.org/dev/packaging/
>> [2]http://packages.python.org/Distutils2/distutils/setupscript.html
>>
>> --
>> Kristian G. Kvilekval ([hidden email]) 805-636-1599
>> _______________________________________________
>> Distutils-SIG maillist  -  [hidden email]
>> http://mail.python.org/mailman/listinfo/distutils-sig
>
>



--
Kristian G. Kvilekval ([hidden email]) 805-636-1599
_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig
Reply | Threaded
Open this post in threaded view
|

Re: distutils2 1.0a4 and simple package

Éric Araujo
In reply to this post by kgk-3
Hi,

Sorry about that: the doc is very outdated and I have a ton of things to
update, fix and expand.  I have changed
http://bugs.python.org/issue12779 tracks my progress.

To get started with d2, create a setup.cfg file as documented in the
packaging/setupcfg page and run the pysetup script to see available
actions and commands.

Regards
_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig
Reply | Threaded
Open this post in threaded view
|

Re: distutils2 1.0a4 and simple package

Éric Araujo
In reply to this post by kgk-3
Message was sent incomplete.  I meant to say:
I have changed around 1200 lines and I’m really not done.
_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig
Reply | Threaded
Open this post in threaded view
|

Re: distutils2 1.0a4 and simple package

Éric Araujo
In reply to this post by kgk-3
> Thanks for the pointer, is there anyway to use another filename other
> than setup.cfg?
> I am trying to build several related package from a common root?
In the current code the filename must be setup.cfg.  I think the rise of
distributed version control systems and usable packaging tools like pip
and buildout (and setuptools’ namespace package feature) have encouraged
the separation of projects into separate libraries, each one with its
repository and setup.py file.  That may be the reason why setup.cfg is
hard-coded in distutils2.

What do other people think about this?  Is the ability to create more
than one Python distribution from one directory something we really need?

(MAL: I think you use a similar system for your mx releases, please
ignore this if I remembered wrong.)

Regards
_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig
Reply | Threaded
Open this post in threaded view
|

Re: distutils2 1.0a4 and simple package

Erik Bray-2
On Wed, Mar 21, 2012 at 11:27 PM, Éric Araujo <[hidden email]> wrote:

>> Thanks for the pointer, is there anyway to use another filename other
>> than setup.cfg?
>> I am trying to build several related package from a common root?
> In the current code the filename must be setup.cfg.  I think the rise of
> distributed version control systems and usable packaging tools like pip
> and buildout (and setuptools’ namespace package feature) have encouraged
> the separation of projects into separate libraries, each one with its
> repository and setup.py file.  That may be the reason why setup.cfg is
> hard-coded in distutils2.
>
> What do other people think about this?  Is the ability to create more
> than one Python distribution from one directory something we really need?

This is a use case I've had twice in the past, if I understand
correctly at least.  In both cases a fair bit of evil hackery was
employed to make it possible in distutils (actually setuptools).  So
it can be done, but it gets ugly, and can cause some surprisingly
problems, most of which I can't even think of at the moment.  What I
can say is that the take away lesson of that experiment was to not do
that, and to just break everything into separately distributed
packages.

Erik
_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig
Reply | Threaded
Open this post in threaded view
|

Re: distutils2 1.0a4 and simple package

Jim Fulton
In reply to this post by Éric Araujo
On Wed, Mar 21, 2012 at 11:27 PM, Éric Araujo <[hidden email]> wrote:
>> Thanks for the pointer, is there anyway to use another filename other
>> than setup.cfg?
>> I am trying to build several related package from a common root?
> In the current code the filename must be setup.cfg.  I think the rise of
> distributed version control systems and usable packaging tools like pip
> and buildout (and setuptools’ namespace package feature) have encouraged
> the separation of projects into separate libraries, each one with its
> repository and setup.py file.  That may be the reason why setup.cfg is
> hard-coded in distutils2.

It was likewise awkward to name setup.py anything other than setup.py.

I have a few VCS projects that contain multiple Python projects in separate
directories:

  http://svn.zope.org/zc.buildout/trunk/
  http://svn.zope.org/bobo/trunk/

This has worked fine for me.

I might like more flexibility, not sure, but the current limitation
probably makes installers simpler, which is worthwhile imo.

Jim

--
Jim Fulton
http://www.linkedin.com/in/jimfulton
_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig
Reply | Threaded
Open this post in threaded view
|

Re: distutils2 1.0a4 and simple package

kgk-3
In reply to this post by Éric Araujo
This is exactly the situation I have.. A single project with client and server side 
libraries.  The entire project is in a single VCS repository.  

 

On Wednesday, March 21, 2012 8:27:37 PM UTC-7, Éric Araujo wrote:
> Thanks for the pointer, is there anyway to use another filename other
> than setup.cfg?
> I am trying to build several related package from a common root?
In the current code the filename must be setup.cfg.  I think the rise of
distributed version control systems and usable packaging tools like pip
and buildout (and setuptools’ namespace package feature) have encouraged
the separation of projects into separate libraries, each one with its
repository and setup.py file.  That may be the reason why setup.cfg is
hard-coded in distutils2.

What do other people think about this?  Is the ability to create more
than one Python distribution from one directory something we really need?



We would like to build separate distributions for the client and server.
From my standpoint, I would like to build them together as they
share some common directories (i.e. config, docs and readme's)




 

(MAL: I think you use a similar system for your mx releases, please
ignore this if I remembered wrong.)

Regards
______________________________​_________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/​mailman/listinfo/distutils-sig


_______________________________________________
Distutils-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/distutils-sig