[Patches] [Patch #103678] setup.py.in

[noreply@sourceforge.net]

Patch #103678 has been updated. 

Project: python
Category: Build
Status: Open
Submitted by: donnc
Assigned to : akuchling
Summary: setup.py.in

Follow-Ups:

Date: 2001-Feb-08 11:16
By: donnc

Comment:
I would be happy with extra symbols in Makefile, for
setup.py to use.  I think this system will be somewhat
obscure for someone trying to figure out how to make
a build work, so some pointer comments at the top of
setup.py would be good.  The last point there is not
so clear to me -- it sounds like there's an intent
to move a lot of logic from "configure" to setup.py.
I look forward to seeing whether that does give us much
more power and flexibility.  It will put some pressure
on the Python code base, though - I already have changes
in for distutils and even os.py, to get through the build,
not to mention the two unsuccessful attempts to get changes
into setup.py.  In 2.0, I came along pretty late in the beta
with changes that make it build for BeOS.  Here I am right
at the beginning of 2.1 alpha, but the hurdle seems a lot
higher.
-------------------------------------------------------

Date: 2001-Feb-08 10:45
By: nascheme

Comment:
One more reason for not using step.py.in or setup.cfg.in: 
The Makefile is available to distutils when building
extension modules after the source is gone (ie. its 
installed in lib).
-------------------------------------------------------

Date: 2001-Feb-08 10:29
By: lemburg

Comment:
I'd prefer if you'd put all the code into setup.py -- the tools are
all there. If you need extra symbols, then have configure place
them in the Makefile or config.h. Both are available for distutils
to use. Platform specifica can then be dealt with under Python's
control which gives you much more power and flexibility.
-------------------------------------------------------

Date: 2001-Feb-08 10:12
By: donnc

Comment:
That's OK with me, all I need is a place where I can
deal with platform specific issues, and it doesn't
matter a bit to me where.  setup.py.in, Makefile,
setup.cfg, write the stuff right into setup.py
(e.g., if platform == 'Darwin').  What do you like?
-------------------------------------------------------

Date: 2001-Feb-08 08:38
By: akuchling

Comment:
Agreed; generating Makefiles from the configure script is bad enough, and
generating executable scripts is worse still.  Reintroducing setup.cfg.in
would be better, if that proves necessary.

-------------------------------------------------------

Date: 2001-Feb-08 05:01
By: lemburg

Comment:
Using setup.py.in is the wrong strategy here: you should consider
placing the symbols into the generated Makefile or config.h
and then have setup.py parse these files (the tools for this
are all there in distutils).
-------------------------------------------------------

-------------------------------------------------------
For more info, visit:

http://sourceforge.net/patch/?func=detailpatch&patch_id=103678&group_id=5470