[Python-bugs-list] [ python-Bugs-438773 ] fpectl is not initiliazed on Windows

[noreply@sourceforge.net]

Bugs item #438773, was opened at 2001-07-05 06:35
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=438773&group_id=5470

Category: Documentation
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Paul Prescod (prescod)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: fpectl is not initiliazed on Windows

Initial Comment:
config.c initializes all of the modules that are 
compiled into the python22.dll, but not fpectl. So 
we're carrying around the functionality and documented 
it as being available on Windows, but it isn't.


----------------------------------------------------------------------

>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-07-05 14:20

Message:
Logged In: YES 
user_id=3066

I've marked this as "Won't Fix" since the bug as reported
won't be fixed.  The documentation has been updated to
reflect reality (Doc/lib/libfpectl.tex revisions 1.2 and
1.1.4.1).

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-07-05 14:20

Message:
Logged In: YES 
user_id=31435

Removed fpectlmodule.c and fpetestmodule.c from the Windows 
build, PCbuild/pythoncore.dsp, new revision: 1.16.


----------------------------------------------------------------------

Comment By: Paul Prescod (prescod)
Date: 2001-07-05 14:07

Message:
Logged In: YES 
user_id=31788

Okay, but is there any reason to keep it in the project 
file and DLL if it is just useless code? We'll just have 
this conversation again when someone else notices this 
strange situation.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-07-05 13:50

Message:
Logged In: YES 
user_id=31435

Changed to Documentation and back to Fred.  fpectl has 
never been available on Windows, so the docs shouldn't say 
that it is.

The raw code may actually work on Windows, but I haven't 
checked and have no interest in trying it:  it's not enough 
just to compile the module, you need also to #define 
WANT_SIGFPE_HANDLER in PC/config.h, and then the 
PyFPE_START_PROTECT and PyFPE_END_PROTECT macros change 
from nops to expensive setjmps and external calls.  I don't 
want to release Windows Python that way; fine by me if 
somebody wants to compile their own Python that way, though.

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-07-05 11:27

Message:
Logged In: YES 
user_id=3066

Assigning to Tim since he knows what to do on Windows.  I
think the documentation change was based on user comments.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=438773&group_id=5470