Error when installing via pip

[ZapAnton]

Both pipenv install hyperjson and pip install hyperjson produce the following error:

  Could not find a version that satisfies the requirement hyperjson (from versions: )
No matching distribution found for hyperjson

Tried this on Ubuntu 18.10 with python 3.6.7

[cjgu]

Yeah, seems there's only wheel's for OS X and 3.6/2.7 (https://pypi.org/project/hyperjson/#files). We need a normal source package that gets built on install as a fallback.

[mre]

Alright, that makes sense.
Don't know if pyo3-pack has support for publishing source packages or if there is some other way. Maybe @konstin knows.

On that note, I found that I'm not publishing --release builds. Will fix that.
Sorry for the inconvenience.

[konstin]

sdist are not yet possible with pyp3-pack as pip hasn't implemented PEP 517 yet (PyO3/maturin#2). I highly suggest releasing from CI, which means you get wheels for all major platforms (s. e.g. https://pypi.org/project/pyo3-pack/#files, https://github.com/PyO3/pyo3-pack/blob/master/.travis.yml and https://github.com/PyO3/pyo3-pack/blob/master/appveyor.yml).

For the release thing, I plan to change the default for upload to release and strip in pyo3-pack which should make that easier

[konstin]

I've added some linux wheels to the release page for now

[packysauce]

Howdy, are there any plans to upload the linux wheels to pypi?

[speedcell4]

I can not install hyperjson on Github Actions by using pip, and I have tried to change my requirements.txt from hyperjson to git+https://github.com/mre/hyperjson.git@3a96b9a8d54ba59e7ac29658974c88f15d39b6fc , but neither work.

the error from GitHub Actions:

Running command git clone -q https://github.com/mre/hyperjson.git /tmp/pip-req-build-thp3i4xs
  Running command git checkout -q 3a96b9a8d54ba59e7ac29658974c88f15d39b6fc
    ERROR: Command errored out with exit status 1:
     command: /opt/hostedtoolcache/Python/3.7.5/x64/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-thp3i4xs/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-thp3i4xs/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-req-build-thp3i4xs/pip-egg-info
         cwd: /tmp/pip-req-build-thp3i4xs/
    Complete output (5 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/opt/hostedtoolcache/Python/3.7.5/x64/lib/python3.7/tokenize.py", line 447, in open
        buffer = _builtin_open(filename, 'rb')
    FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-req-build-thp3i4xs/setup.py'
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
##[error]Process completed with exit code 1.

[mre]

I'm very sorry that it took so long but these problems should now be resolved thanks to our new release process through Github Actions (#130). Pre-built wheels are now available for Linux, macOS, and Windows and Python 3.5 up to 3.8. Make sure to post a comment here if you're still running into problems.

[iammortimer]

still running into problems:
pip install hyperjson
ERROR: Could not find a version that satisfies the requirement hyperjson (from versions: none)
ERROR: No matching distribution found for hyperjson

Python version:
Python 3.7.3 (v3.7.3:ef4ec6ed12, Mar 25 2019, 21:26:53) [MSC v.1916 32 bit (Intel)] on win32

[mre]

That's odd. Looking at the latest release on PyPI, I can see the Windows 3.7 package here... 🤔
Anyone has an idea?

[iammortimer]

It's probably due to that all your windows packages are x64 only, after installing python x64 i was able to pull and install the package.

[mre]

Oh, yeah that's it. Sorry, totally missed the win32 part.
Unfortunately Github actions doesn't support 32 bit runners (yet). See here and here. The only alternative I see would be a self-hosted runner, which would incur a maintenance burden.
Sooo 🤷. Glad you found a way to make it work for you, though. Closing. 😊