|
|
|
|
|
by jlewitt1
54 days ago
|
|
The dev/prod mismatch concern is reasonable but the actual failure surface is narrow. Pure Python is fine. The risk is native deps with C extensions (NumPy, SciPy, cryptography, lxml, Pillow). If your data science stack has those, the work is auditing your dep tree for arch-specific behavior, setting up a multi-arch CI matrix, and cutting over one service at a time on Graviton before touching prod. Most ARM moves either go great (no native deps) or get stuck because someone finds a half-broken arch-specific wheel. The audit is usually the part nobody wants to do. (Building Keshro for this kind of multi-step audit + cutover, but the answer stands either way.) |
|