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

Showing content from https://mail.python.org/pipermail/python-dev/2002-April/023393.html below:

[Python-Dev] autoheader warning for WITH_UNIVERSAL_NEWLINES

• Previous message: [Python-Dev] autoheader warning for WITH_UNIVERSAL_NEWLINES
• Next message: [Python-Dev] autoheader warning for WITH_UNIVERSAL_NEWLINES
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jack Jansen <Jack.Jansen@oratrix.com> writes:

> Bah, I am not happy with this. This makes it even more difficult to
> create the correct pyconfig.h for MacPython. How is updating
> pyconfig.h handled for Windows (and other non-autoconf platforms)?

Can you elaborate what "this" is? pyconfig.h.in always was a generated
file; it always started with the line

/* pyconfig.h.in.  Generated from configure.in by autoheader.  */

So when you manually edited pyconfig.h.in, you *could* have known better.

Regards,
Martin

• Previous message: [Python-Dev] autoheader warning for WITH_UNIVERSAL_NEWLINES
• Next message: [Python-Dev] autoheader warning for WITH_UNIVERSAL_NEWLINES
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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