-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switching to pdbpp is making it impossible to install with pypy and git #364
Comments
Such a good project, yet, I cannot install it. |
@Zaczero 😂 Yeah sorry our last alpha was borked on pypi... been meaning to do another release but it's just been lower on the TODO list. Install from git should work no?
Seems to be some non-tractor issue that @grizzlybearg experienced 🤔 @Zaczero @grizzlybearg RE the If there's anything else I can help with please LMK. I will try to get a new pypi release out this week. ALSO, how does everyone feel about using |
@goodboy Installing from git also fails |
@grizzlybearg Hmm. It's the same error as from OP yah? Technically we haven't really tested nor claimed to support In terms of installing with
AGAIN, PyPi install are known to borked rn, i already linked the existing issue. |
On a related note, after having used |
This is a fresh ubuntu image with git, python, pip installed. |
@Zaczero your 2nd command is timing out on the network? I'm not sure i can help much with that. Either way try doing a from source install by cloning and cd-ing to the repor dir and running Will hopefully get to patching this all up and another release in the next month once a ton of patches get landed. |
I'm not sure what more to express here. The problem seems isolated to the Tractor package in my case. It's possible that it's experiencing timeouts due to its continued use of the deprecated git:// protocol. As discussed in this GitHub blog post (https://github.blog/2021-09-01-improving-git-protocol-security-github/). I'm aware that numerous installation approaches exist. However, I'd kindly request that the functional methods be documented in the Installation section of the README. |
Ok well our CI thinks that installs work just fine, otherwise this job would fail 😉. Mind you this is doing manual sdist installs with https://github.com/goodboy/tractor/actions/runs/6001334998/job/16275291910
Yes indeedy 😂 we for sure do not want to have the legacy url syntax in there. |
FWIW, we'll of course quickly accept a patch for this to the README 😉 |
Thank You! |
@Zaczero yah so there's quite a few dev branches + PRs that need to get landed before a release including: |
Ok so we need to switch to the https url form for the readme: |
I get the followinf error when trying to install using pypy:
ERROR: Packages installed from PyPI cannot depend on packages which are not also hosted on PyPI.
tractor depends on pdbpp@ git+https://github.com/pdbpp/pdbpp@76c4be5#egg=pdbpp ; python_version > "3.9"
I can't install using git because I get this error:
`PS C:\Users\user> pip install git+git://github.com/goodboy/tractor.git
Defaulting to user installation because normal site-packages is not writeable
Collecting git+git://github.com/goodboy/tractor.git
Cloning git://github.com/goodboy/tractor.git to c:\users\user\appdata\local\temp\pip-req-build-ryqbr1ew
Running command git clone --filter=blob:none --quiet git://github.com/goodboy/tractor.git 'C:\Users\user\AppData\Local\Temp\pip-req-build-ryqbr1ew'
fatal: unable to connect to github.com:
github.com[0: 20.87.225.212]: errno=Unknown error
error: subprocess-exited-with-error
× git clone --filter=blob:none --quiet git://github.com/goodboy/tractor.git 'C:\Users\user\AppData\Local\Temp\pip-req-build-ryqbr1ew' did not run successfully.
│ exit code: 128
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× git clone --filter=blob:none --quiet git://github.com/goodboy/tractor.git 'C:\Users\user\AppData\Local\Temp\pip-req-build-ryqbr1ew' did not run successfully.
│ exit code: 128
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.`
The text was updated successfully, but these errors were encountered: