pip skips fetching package from "install_requires" section

Hi,

I have a package (testRecord1) hosted on PyPi. I’m able to pip install the package on Linux platform. If I add this package in install_requires section of another package’s setup.py and try to create a wheel for it, the wheel creation fails with the following :

 Analyzing links from page https://pypi.python.org/simple/testrecord1/
    Skipping link https://pypi.python.org/packages/ec/d6/a70e8a40358e05a41269feecfcb231d0f42680ddddab9dcdbe911e6310f0/testRecord1-2018.0.0-py2.py3-none-manylinux1_x86_64.whl#md5=b440157247b4d09102ab450b70b4b3ce (from https://pypi.python.org/simple/testrecord1/); No binaries permitted for testRecord1
 Could not find a version that satisfies the requirement testRecord1 (from testRecord2==0.2) (from versions: )

Would really appreciate some feedback on how to circumvent this. I’ve also tried creating testRecord1’s wheel with :

class BinaryDistribution(dist.Distribution):
    def is_pure(self):
      return False

setup(...
distclass=BinaryDistribution
)

Still no luck.

Thanks, Rohit (p.s. wheel for testRecord1 was created with the following setup.cfg:

[bdist_wheel]
universal = 1

)

[benoit-pierre]

Why don’t you create the wheels by using python ./setup.py bdist_wheel ... directly, instead of going through pip?

[rohit-jamuar]

I’m actually using conda-build to create wheels, the nicer thing about using pip as opposed to setup.py is that pip does a clean-up of temporary files post creation of wheel. “setup.py bdist_wheel” leaves behind meta files that are eventually tarball-ed into a conda-package with the wheel, which I want to avoid. But, “setup.py bdist_wheel” might be a better option in the long run.