This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Unable to pip install pyjasperclient
Type: Stage: resolved
Components: Installation Versions: 3rd party
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: r.david.murray, viel
Priority: normal Keywords:

Created on 2014-02-13 16:52 by viel, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg211161 - (view) Author: Tammy (viel) Date: 2014-02-13 16:52
We used to be able to perform a "pip install pyjasperclient" with success.  The last time I did this was within the last couple months.
I tried this today and received an error,
...
Downloading/unpacking elementtree (from pyjasperclient)
  Could not find any downloads that satisfy the requirement elementtree (from pyjasperclient)
  Some externally hosted files were ignored (use --allow-external elementtree to allow).
Cleaning up...
No distributions at all found for elementtree (from pyjasperclient)
Storing debug log for failure in /home/belairlab/.pip/pip.log
msg211162 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2014-02-13 17:12
I'm afraid this isn't the appropriate tracker for either PIP issues or pypi issues, or issues with particular 3rd party packages (such as pyjasperclient).  This tracker is for bugs in the CPython implementation of the language, and the standard library.

(While elementtree is part of the standard library, the requirement issue in pip is not an stdlib/CPython problem :)
History
Date User Action Args
2022-04-11 14:57:58adminsetgithub: 64817
2014-02-13 17:12:29r.david.murraysetstatus: open -> closed

versions: + 3rd party, - Python 2.7
nosy: + r.david.murray

messages: + msg211162
resolution: not a bug
stage: resolved
2014-02-13 16:52:29vielcreate