Yesterday the 1.4.0 version was released in PyPI but only binary releases were distributed, not the source one.

This causes a problem with CI system of Apache Airflow (we get JPype1 as transitive dependency of jaydebeapi which is used by our JDBC provider).

We are automatically upgrading our dependencies on CI and we upgraded them to 1.4.0 automatically but this upgrade caused our ARM image caching build to fail.

#145 96.12 The conflict is caused by:
#145 96.12     jaydebeapi 1.2.3 depends on JPype1; python_version > "2.7" and platform_python_implementation != "Jython"
#145 96.12     The user requested (constraint) jpype1==1.4.0
#145 96.12 
#145 96.12 To fix this you could try to:
#145 96.12 1. loosen the range of package versions you've specified
#145 96.12 2. remove package versions to allow pip attempt to solve the dependency conflict
#145 96.12 

After investigation it turned out that the problem is lack of source distribution for JPype1 for 1.4.0. JPype1 does not publish ARM binary images, so up until 1.3.0 pip automatically built the packages from sdist when instaling JPype1 on ARM. But since 1.4.0 version has no source distribution, trying to install it on ARM, fails.

Could you please publish the source distribution as well on PyPI for 1.4.0 onwards ?
Other solution could be to remove the ARM binary packages, but that could be way more difficult to setup for automation (and would leave other platforms out possibly).

Here is the 1.4.0 PyPI screenshot (missing sdist):

Corresponding 1.3.0 PyPI (sdist is there):