This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nobody
Date 2000-08-01.21:10:13
SpamBayes Score
Marked as misclassified
Jitterbug-Id: 121
Submitted-By: "Brad Clements" <>
Date: Wed, 3 Nov 1999 15:53:01 -0500
Version: None
OS: None

The system encountered a fatal error 
After command: 
The last error code was: Connection refused 

Web interface using {HYPERLINK ""}Jitterbug 
{HYPERLINK "../python-bugs/"}Public interface 
{HYPERLINK "../python-bugs.private"}Private interface (requires password) 
{HYPERLINK ""}Python home page 

Here's what I said for Python 1.5.2 on Win32 #0

PyRun_SimpleFile, PyRun_File and other functions that take a FILE * are not 
usable on WIN32 from non-VC applications because python15.dll is statically 
linked to the MS runtime DLL. Embedding applications that try to use these 
functions are passing in FILE * structures that do not match MS's runtime 

For example, I'm using Python in a Borland C++ Builder application. Although I 
can open a FILE *, when passed to python15.dll the FILE * is not usable.

The addition of two helper functions would solve this problem:

FILE * PyRun_OpenFile(char *file, char *mode) 
  return fopen(file,mode)

int PyRun_CloseFile(FILE *ptr)
  return fclose(ptr)

This way embedding apps could get python15.dll to open the file and it would 

A temporary workaround is to always load the .pyc file in PyRun_SimpleFile..

Brad Clements,         (315)268-1000                          (315)268-9812 Fax
netmeeting: ils://               ICQ: 14856937

Audit trail:
Fri Nov 05 10:31:10 1999	guido	moved from incoming to request
Date User Action Args
2007-08-23 13:49:42adminlinkissue210821 messages
2007-08-23 13:49:42admincreate