You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2009-02-03.09:39:37.677>created_at=<Date2003-10-28.09:43:52.000>labels= ['type-feature', 'library']
title='Set option for subprocess in setup.py'updated_at=<Date2009-02-03.09:39:37.676>user='https://bugs.python.org/pimbuur'
It is now only possible to prescribe options for
subprocesses (e.g. build_ext) in the file setup.cfg
But some of these options are obligatory to get the correct
result for the action.
These options can be set in the file setup.cfg, but it is not
clear that these options should not be changed, nor is it
clear in the setup.py file that the setup.cfg is relevant.
I tend now to not to use the setup.cfg and
call 'python setup.py' (without arguments).
The setup.py will then fill in the necessary options in
sys.argv .
It would be much nicer if these options could be explicitly
given as defaults for the subprocess.
I am not developing Python extensions anymore, so I am not interested
in this issue.
I am not sure whether this issue is still applicable to e.g. Python 3.0
You can close it if you wisj
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: