Changes by Éric Araujo mer...@netwok.org:
--
resolution: accepted - out of date
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
Éric Araujo mer...@netwok.org added the comment:
I have turned my branch into a clean patch for default:
https://bitbucket.org/Merwok/distutils2/changeset/076b15559290
Notes:
- You can diff configure.py against build.py and install_dist.py from an
earlier revision to see what code has been
Changes by Éric Araujo mer...@netwok.org:
--
keywords: +needs review, patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Éric Araujo mer...@netwok.org added the comment:
Status update.
* configure works: it checks options (like install does) and writes to a file.
* New design for build: It uses set_undefined_options to get options from
configure (previously it read the cache file, but this caused nasty issues;
Éric Araujo mer...@netwok.org added the comment:
(BTW I haven’t pushed the work in progress yet but I will shortly.)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
Jeremy Kloth jeremy.kl...@gmail.com added the comment:
for #1 instead of importing `build`/`install` commands for their options, why
not define the options only on the `configure` command? The B/I commands could
just lookup their needed options from the configure command.
On that note, how
Changes by Éric Araujo mer...@netwok.org:
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list mailing list
Unsubscribe:
Éric Araujo mer...@netwok.org added the comment:
Adding message from jkloth removed by error (remove/reply confusion):
for #1 instead of importing `build`/`install` commands for their options, why
not define the options only on the `configure` command? The B/I commands could
just lookup
Éric Araujo mer...@netwok.org added the comment:
why not define the options only on the `configure` command?
This is what Tarek told me and what I thought I said two messages earlier.
On that note, how does the B/I commands get the options defined by
`configure`?
See
Jeremy Kloth jeremy.kl...@gmail.com added the comment:
How would the build or install command get the options in this case:
python setup.py configure --prefix=$HOME build install
Remember that commands can be chained (and that commands can run other
commands). I would like to be able to do
Éric Araujo mer...@netwok.org added the comment:
configure is not config. As I understand it, the config command aimed to be
something like ./configure in autotools, thus usable in combination with build
and install. configure is different: it is meant to be run once to create a
Éric Araujo mer...@netwok.org added the comment:
Quick update: I have done a basic part of this, but Tarek explained to me the
real usefulness of this command, i.e. provide build and installation options
for third-party code (for the same purposes that get_config_var in Python’s
sysconfig). I
Éric Araujo mer...@netwok.org added the comment:
Tarek also answered my questions.
1) 4) build and install options should be defined and checked only once, in
configure. build and install would inherit from this class and get their option
from it.
3) I switched to using
Jeremy Kloth jeremy.kl...@gmail.com added the comment:
WRT #5, it would be possible to use section headers within the configure.cache
file to indicate a particular platform build. Very much like how 4Suite's
`config` command stored the cache file.
--
Éric Araujo mer...@netwok.org added the comment:
5) Should the command write different files per Python version and platform?
4Suite’s config command does that.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
Antoine Pitrou pit...@free.fr added the comment:
Shouldn't config and configure have more distinguishable names?
(if I understand correctly, they both are distutils2 commands)
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
Éric Araujo mer...@netwok.org added the comment:
4Suite’s DistExt has a config command similar to the new Distutils2 configure
command described in this bug report. The Distutils config command is an
unfinished command with use similar to autotools configure scripts. From the
module
Éric Araujo mer...@netwok.org added the comment:
I have a working configure command at
http://bitbucket.org/Merwok/distutils2-configure which works. (Read my short
reports on https://wokslog.wordpress.com/ for more details.) It’s not
completely finished, though:
1) I import build and install
Éric Araujo mer...@netwok.org added the comment:
Distutils2 already has a config command used to configure some aspects of C
compilation. Not sure if I should expand that or write an unrelated configure
command.
--
___
Python tracker
Tarek Ziadé ziade.ta...@gmail.com added the comment:
start a new command from scratch. The configure command is not dealing but with
generating a configuration file.
config is implementing a whole compilation chain.
--
___
Python tracker
Changes by Jeremy Kloth jeremy.kl...@gmail.com:
--
nosy: +jkloth
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list
Changes by Ralf Schmitt sch...@gmail.com:
--
nosy: +schmir
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list mailing
Éric Araujo mer...@netwok.org added the comment:
My review of 4Suite’s config command is on
http://bitbucket.org/Merwok/distutils2/wiki/4suite/config. Comments welcome.
(Adding my mentor to the nosy list.)
--
keywords: +gsoc
nosy: +titus
___
Python
Changes by Dan Buch daniel.b...@gmail.com:
--
nosy: +meatballhat
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list
Changes by Josip Djolonga jdzolo...@gmail.com:
--
nosy: +josip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list mailing
Changes by Zubin Mithra zubin.mit...@gmail.com:
--
nosy: +zubin71
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list
New submission from Tarek Ziadé ziade.ta...@gmail.com:
This command will contain all options that are used to build extensions (out of
the build* and install* commands) and will create a confifuration file.
build* and install* commands will be able to read back the file if present, and
use
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +merwok
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list mailing
Changes by Shashwat Anand anand.shash...@gmail.com:
--
nosy: +l0nwlf
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8254
___
___
Python-bugs-list
29 matches
Mail list logo
