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-July/005880.html below:

[Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python

[Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python [Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 PythonBarry Scott barry@scottb.demon.co.uk
Sun, 9 Jul 2000 15:56:31 +0100
I read in the archives the problem with import of a 1.5 extension
into newer Python release crashing say new Python.

A solution that works is to use a new naming scheme for the
initialisation entry point. Currently it is "init" + module-name
with "_d" appended if it is debug image.

Change "init" to "init16", "init20" and you can import the old
1.5 linked extension without a crash, you get an error reported
instead.

		BArry




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