A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-October/009679.html below:

[Python-Dev] Usage of --with- configure options

[Python-Dev] Usage of --with- configure optionsMartin v. Loewis martin@loewis.home.cs.tu-berlin.de
Mon, 2 Oct 2000 09:48:37 +0200
I noticed that Python's configure.in does not follow the autoconf
style for using --enable- options. The autoconf documentation says

#   Some packages require, or can optionally use, other software packages
# which are already installed.  The user can give `configure' command
# line options to specify which such external software to use.  The
#  options have one of these forms:
#
#     --with-PACKAGE[=ARG]
#     --without-PACKAGE
...
#    If a software package has optional compile-time features, the user
# can give `configure' command line options to specify whether to compile
# them.  The options have one of these forms:
#
#     --enable-FEATURE[=ARG]
#     --disable-FEATURE

So --with- options should be used for integrating 3rd party libraries,
--enable- options for features that that can be independently turned
on or off.

I'd conclude that the following options are provided incorrectly in
Python 2.0: --with-pydebug (should be --enable-pydebug),
--with(out)-cycle-gc (should be --disable-cycle-gc). Is this something
that should change?

Regards,
Martin




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4