[ python-Feature Requests-960325 ] "require <feature>" configure option

SourceForge.net noreply at sourceforge.net
Mon Jun 21 01:49:31 EDT 2004


Feature Requests item #960325, was opened at 2004-05-25 21:07
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=960325&group_id=5470

>Category: None
>Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Hallvard B Furuseth (hfuru)
Assigned to: Nobody/Anonymous (nobody)
Summary: "require <feature>" configure option

Initial Comment:
I'd like to be able to configure Python so that
Configure or Make will fail if a particular
feature is unavailable.  Currently I'm concerned
with SSL, which just gets a warning from Make:

  building '_ssl' extension
  *** WARNING: renaming "_ssl" since importing it
failed: ld.so.1: ./python: fatal: libssl.so.0.9.8: open
failed: No such file or directory

Since that's buried in a lot of Make output, it's
easy to miss.  Besides, for semi-automatic builds
it's in any case good to get a non-success exit
status from the build process.

Looking at the Make output, I see the bz2 extension
is another example where this might be useful.

Maybe the option would simply be '--enable-ssl',
unless you want that to merely try to build with
ssl.

Or '--require=ssl,bz2,...'.


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

>Comment By: Martin v. Löwis (loewis)
Date: 2004-06-21 07:49

Message:
Logged In: YES 
user_id=21627

Moved to RFE.

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

Comment By: Terry J. Reedy (tjreedy)
Date: 2004-06-04 23:35

Message:
Logged In: YES 
user_id=593130

See item 964703 for further information and then decide.

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

Comment By: Hallvard B Furuseth (hfuru)
Date: 2004-06-02 13:56

Message:
Logged In: YES 
user_id=726647

Ah, so that's what RFE means.  You could rename
that to 'Enhancement Requests'.  Anyway, QoI
issues tend to resemble bug issues more than
enhancement issues, so '"bug" of type feature
request' looks good to me.
Though I'll resubmit as RFE if you ask.

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

Comment By: Terry J. Reedy (tjreedy)
Date: 2004-06-02 04:07

Message:
Logged In: YES 
user_id=593130

Yes, this is not a PEP item.  I didn't notice Feature Reqest 
since it is redundant vis a vis the separate RFE list.


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

Comment By: Hallvard B Furuseth (hfuru)
Date: 2004-06-01 20:13

Message:
Logged In: YES 
user_id=726647

I marked it with Group: Feature Request.
Not a bug, but a quality of implementation issue.
It seemed more proper here than as a PEP.

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

Comment By: Terry J. Reedy (tjreedy)
Date: 2004-06-01 19:58

Message:
Logged In: YES 
user_id=593130

Are you claiming that there is an actual bug, or is this merely 
an RFE (Request For Enhancement) item?

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=960325&group_id=5470



More information about the Python-bugs-list mailing list