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

Showing content from https://mail.python.org/pipermail/python-dev/2001-March/013909.html below:

[Python-Dev] setup.py is too aggressive

• Previous message: [Python-Dev] setup.py is too aggressive
• Next message: [Python-Dev] setup.py is too aggressive
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> > In any case, distributors are certainly advised to run the testsuite
> > and potentially remove or fix modules for which the tests fail.
> 
> These, however, aren't flagged as failures -- they're flagged as
> ImportErrors which are ignored during tests

I see. Is it safe to say, for all modules in the core, that importing
them has no "dangerous" side effect? In that case, setup.py could
attempt to import them after they've been build, and delete the ones
that fail to import. Of course, that would also delete modules where
setting LD_LIBRARY_PATH might cure the problem...

Regards,
Martin

• Previous message: [Python-Dev] setup.py is too aggressive
• Next message: [Python-Dev] setup.py is too aggressive
• 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