[issue2219] Py30a3: Possibly confusing message when module detection fails

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: It's actually been quite a while since it changed from being Modules/Setup to being in setup.py, I think a couple of years at least. And, yes, I realize that Fedora is changing the Modules/Setup file in their SRPM, but with Python 3k they

[issue2219] Py30a3: Possibly confusing message when module detection fails

Mark Summerfield <[EMAIL PROTECTED]> added the comment: On 2008-03-20, Sean Reifschneider wrote: > Sean Reifschneider <[EMAIL PROTECTED]> added the comment: > > Don't modify Modules/Setup*, do as the message says and modify setup.py. > Search for "4, 5", and change that to "4, 6", then run confi

[issue2219] Py30a3: Possibly confusing message when module detection fails

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: Don't modify Modules/Setup*, do as the message says and modify setup.py. Search for "4, 5", and change that to "4, 6", then run configure and make and it will build without this message. I have done this against the py3k trunk and it bui

[issue2219] Py30a3: Possibly confusing message when module detection fails

Mark Summerfield added the comment: On 2008-03-03, Martin v. Löwis wrote: > Martin v. Löwis added the comment: > > What I find confusing is: > > > > Failed to find the necessary bits to build these modules: > > > > To find the necessary bits, look in setup.py in detect_modules() for the > > modu

[issue2219] Py30a3: Possibly confusing message when module detection fails

Martin v. Löwis added the comment: > What I find confusing is: > > Failed to find the necessary bits to build these modules: > > To find the necessary bits, look in setup.py in detect_modules() for the > module's name. > > I find it confusing because AFAIK if a module can't be built it usually

[issue2219] Py30a3: Possibly confusing message when module detection fails

Mark Summerfield added the comment: On 2008-03-03, Martin v. Löwis wrote: > Martin v. Löwis added the comment: > > Rereading your report, I cannot quite understand what issue specifically > you are reporting. What error message do you find confusing, and what do > you think should it say instead?

[issue2219] Py30a3: Possibly confusing message when module detection fails

Martin v. Löwis added the comment: Rereading your report, I cannot quite understand what issue specifically you are reporting. What error message do you find confusing, and what do you think should it say instead? In any case, it is deliberate that db 4.6 is not supported - that release doesn't

[issue2219] Py30a3: Possibly confusing message when module detection fails

Mark Summerfield added the comment: On 2008-03-03, Martin v. Löwis wrote: > Martin v. Löwis added the comment: > > Modules/Setup is out of date; _bsddb supports anything between 3.3 and 4.5. > FYI, only now I've just realised that Fedora 8's db version is 4.6.21, but I thought I'd try it anyway.

[issue2219] Py30a3: Possibly confusing message when module detection fails

Martin v. Löwis added the comment: Modules/Setup is out of date; _bsddb supports anything between 3.3 and 4.5. -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> __ __

[issue2219] Py30a3: Possibly confusing message when module detection fails

New submission from Mark Summerfield: On Fedora 8 I get this message: Failed to find the necessary bits to build these modules: _bsddb To find the necessary bits, look in setup.py in detect_modules() for the module's name. On Kubuntu 6.06 LTS I get the same message, but about different modules: