[Distutils] patch for more SWIG support

[Bastian Kleineidam]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Andi,

On Wed, Oct 06, 2004 at 03:17:31PM -0700, Andi Vajda wrote:
> I just subscribed to this list, pardon my ignorance about the process 
> to follow to get this patch accepted and integrated into the sources, 
> what do I need to do next ?
I think the best way is to submit a patch to SourceForge.
Here is the SF page for patches, there is also a distutils category:
http://sourceforge.net/tracker/?group_id=5470&atid=305470

> ps: the attached patch file is relative to the Pythonn 2.3.3 source
It would be nice to have it against CVS, or at least against newest
upstream version (2.3.4).
There are some developer guidelines on the python homepage:
http://www.python.org/dev/devfaq.html

> --- Python-2.3.3/Lib/distutils/command/build_ext.py	Tue Nov 19 05:12:28 2002
> +++ Python-2.3.3-patched/Lib/distutils/command/build_ext.py	Tue Oct  5 14:24:48 2004
> @@ -79,11 +79,13 @@
>           "forcibly build everything (ignore file timestamps)"),
>          ('compiler=', 'c',
>           "specify the compiler type"),
> -        ('swig-cpp', None,
> -         "make SWIG create C++ files (default is C)"),
I think it is not necessary here to break backwards compatibility
(ie. removing --swig-cpp).
As you wrote above the --swig-cpp options is equivalent to
- --swig-opts="-c++" ? This way you can keep the old option there, and
perhaps print a deprecation message.


Regards,

  Bastian
- -- 
  ,''`.    Bastian Kleineidam  .  calvin (at) debian.org
 : :' :
 `. `'    GnuPG Schlüssel http://kampfwurst.net/gpgkey.txt
   `-

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBZTN6eBwlBDLsbz4RAtqZAJ9oiSXB7PVPPd9cNlXdX7cLcN2ncgCeNvyj
xdJfvgHYtR29CcjwpgTuzJM=
=136L
-----END PGP SIGNATURE-----