When Porting advisor for Graviton evaluates a python code base, it checks the python version and verify the content of the requirements.txt file against a list of know packages for which it has a recommended version.
However, if a package that is not part of the list of know packages is available in PyPI (or any other repository) and missing a aarch64 wheel (in the case of a binary package), porting advisor doesn't issue a warning.
Solution idea(s)
For each package listed in requirements.txt, Porting advisor for Graviton should check on PyPI (or any other repository listed in requirements.txt) whether the package is binary or pure python, check whether there's a aarch64 binary wheel for the package and indicate the minimum version.
If there's no aarch64 package available, it should show a warning.
Description
When Porting advisor for Graviton evaluates a python code base, it checks the python version and verify the content of the requirements.txt file against a list of know packages for which it has a recommended version. However, if a package that is not part of the list of know packages is available in PyPI (or any other repository) and missing a aarch64 wheel (in the case of a binary package), porting advisor doesn't issue a warning.
Solution idea(s)
For each package listed in requirements.txt, Porting advisor for Graviton should check on PyPI (or any other repository listed in requirements.txt) whether the package is binary or pure python, check whether there's a aarch64 binary wheel for the package and indicate the minimum version. If there's no aarch64 package available, it should show a warning.