➜
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.
Created on 2014-01-30 12:57 by George.Kouryachy, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg209712 - (view) | Author: George Kouryachy (George.Kouryachy) | Date: 2014-01-30 12:57 | |
It's declared in pyconfig.h that HAVE_BROKEN_NICE is set if nice() returns success/failure instead of the new priority. But configure checks just opposite (as for http://hg.python.org/cpython/file/03fc7449f204/configure.ac#l4234): if (val1 != -1 && val1 == nice(2)) exit(0); We need "val1 != nice(2)" instead (to ensure that nicelevel is increased) or "val1 == nice(2)+2" (to check increment is proper; this can be tricky in some cases). |
|||
| msg209715 - (view) | Author: George Kouryachy (George.Kouryachy) | Date: 2014-01-30 13:17 | |
It seems to be permanent typo through all branches :( |
|||
| msg209727 - (view) | Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2014-01-30 17:05 | |
Are you sure? The configure test sets ac_cv_broken_nice=1 if "val1 == nice(2)". That is if the call returns the same succesful value each time. |
|||
| msg209912 - (view) | Author: George Kouryachy (George.Kouryachy) | Date: 2014-02-01 19:15 | |
Oops, looks like my local build system artifact. Thank you for your attention, all-clear. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:57 | admin | set | github: 64644 |
| 2014-02-01 19:15:04 | George.Kouryachy | set | status: open -> closed resolution: not a bug messages: + msg209912 |
| 2014-01-30 17:05:40 | benjamin.peterson | set | nosy:
+ benjamin.peterson messages: + msg209727 |
| 2014-01-30 13:17:18 | George.Kouryachy | set | messages:
+ msg209715 versions: + Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 |
| 2014-01-30 12:57:41 | George.Kouryachy | create | |