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 serhiy.storchaka
Recipients berker.peksag, brett.cannon, davin, eric.snow, erik.bray, jnoller, ncoghlan, olebole, sbt, serhiy.storchaka
Date 2015-03-06.22:29:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601680.2zdnaPhQso@raxxla>
In-reply-to <>
> Please keep in mind that this issue should only be encountered by people
> using Python 3.x on a platform like Hurd (an unsupported platform) that has
> no working sem_open implementation.

Yes, and I compiled Python with disabled sem_open for testing.

Python not always specifies what exact type of exception is raised. When you 
pass wrong type of argument to a function, it can raise TypeError or 
AttributeError. If you request unsupported feature, it can raise ImportError, 
AttributeError, or even NameError. Python and C implementations can raise 
different errors (C implementation usually more strict). Not all such cases are 
considered as bugs.

> Adding the "from .synchronize import SEM_VALUE_MAX as maxsize" as was
> suggested would indeed trigger the ImportError but it would also trigger
> this ImportError immediately upon simply doing an "import multiprocessing"
> which is not the current behavior on systems like Hurd.

No, I suggested to replace only the line that produces AttributeError now.
Date User Action Args
2015-03-06 22:29:08serhiy.storchakasetrecipients: + serhiy.storchaka, brett.cannon, ncoghlan, jnoller, erik.bray, sbt, eric.snow, berker.peksag, davin, olebole
2015-03-06 22:29:08serhiy.storchakalinkissue23400 messages
2015-03-06 22:29:08serhiy.storchakacreate