-
Notifications
You must be signed in to change notification settings - Fork 59
Issues: workhorsy/py-cpuinfo
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Wrong processors count reporting 64 instead of 80
bug
Help Wanted
#90
opened Jan 26, 2018 by
gdelfino
Read CPU flags related to Spectre and Meltdown Vulnerabilities
Help Wanted
#92
opened Feb 8, 2018 by
ale5000-git
get_cpu_info() returns current frequency for both current and maximum frequency
bug
#93
opened Feb 14, 2018 by
all-the-good-ones-are-gone
Add ability to specify which core you want information for. (ARM BIG.little support)
bug
#109
opened Sep 18, 2018 by
DoctorObvious
Exception: py-cpuinfo currently only works on X86 and some PPC and ARM CPUs.
Needs More Info
#141
opened May 19, 2020 by
gMan1990
New version of cpuinfo is very slow (4.0.0 versus 5.0.0 or higher)...
#155
opened Aug 20, 2020 by
nicolargo
cpuinfo is forcing open console windows if imported into a non-console execution environment
#196
opened Mar 2, 2023 by
EricBLivingston
MacOS 15 get_cput_info() hangs on rosetta python on Apple M1 Ultra
#218
opened Jan 10, 2025 by
edbarnard
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.