Keep `is_cpu_amd_intel` variable?

[FrancescAlted]

I recently got news that is_cpu_amd_intel variable is gone from numexpr. Although PyTables was not using this variable directly, it was importing it explicitly, and getting rid of it would create more havoc than strictly necessary. @robbmcleod do you think this can be back again in numexpr for the next release? We would really appreciate this.

[robbmcleod]

So we turfed that in #291 to reduce the import time as pandas is getting unwieldy.

What about:

import platform
__proc = platform.processor.lower()
is_cpu_amd_intel = 'intel' in __proc or 'amd' in __proc

That's like 14 ms..., or about 1/2 the time of cpuinfo.py. Alternatively, we could make a dummy variable:

is_cpu_amd_intel = False

Either would be better done at the PyTables end to be frank. Can I replace is_cpu_amd_intel for now and PyTables changes their dev-branch so I can pull it again in 2.6.6?

[FrancescAlted]

I think PyTables would be fine with is_cpu_amd_intel = False. My worries would be that people that are updating numexpr but not PyTables, would end with PyTables crashing. I think we can get rid of this risk for numexpr 2. As a historical note, numexpr used to be vendored with PyTables for a number of years, and this is why it depends on non-public numexpr variables (should be fixed when numexpr 3.0 would be out).

[robbmcleod]

Let's go with the dummy variable then b6138a0 and issue a deprecation warning on release. We don't really ever need to delete the vars, since it's potentially breaking for people whom have new NumExpr and old PyTables, for whatever reason.

I'll release tomorrow, unless you have further thoughts?

[robbmcleod]

Closing