A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-list/2005-September/313111.html below:

Strange Extension Module Behavior

Strange Extension Module BehaviorJeremy Moles jeremy at emperorlinux.com
Wed Sep 28 20:26:26 EDT 2005
Hey guys. I have an extension module written in C that abstracts and
simplifies a lot of what we do here. I'm observing some strange behavior
and wanted to know if anyone had any advice as to how I should start
tracking this down. More specific suggestions are obviously appreciated,
but I really don't have a lot of information to provide so I'm not
hoping for a lot. :)

The module works 100% of the time if I run it non-interactively.
However, any attempt to run it in the "interactive" python interpreter
fails, in some cases silently and in other cases raising exceptions that
really shouldn't be appearing.

Anyways, I guess the core issue here is:

   What could cause an extension module to work within a script
   and not interactively? Are there fundamental issues with the
   standard Python infrastructure I'm not grasping?


More information about the Python-list mailing list

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