Update pypi repo
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start in the repository by checking the current package version and running the reported pip wheel -e . -w wheels --no-deps command. Compare the resulting package with the version published at PyPI, then determine the repository's release steps. Done means the latest bugfix is available as the current installable arrowhead-client version on PyPI.
Written by the indexing model from the issue text.
Description
The version here in the repository contains the latest bugfix which is needed for using the library.
Unfortunately, the current version in pypi doesn't contain the fix. Maybe it's the caching issue again.
As workaround:
Checkout the repo and build your own .whl file from it.
e.g. pip wheel -e . -w wheels --no-deps
Then, you use it in your new project, e.g:
pip install arrowhead-client arrowhead_client-0.4.3a0-py3-none-any.whl
On the long run it would be nice to have the current latest version in the pypi repo.
- Dominant language
- Python
- Stars
- 5
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from arrowhead-f/client-library-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 1/5 Under an hour Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in arrowhead-f/client-library-python
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openvinotoolkit/openvino_notebooks#3665 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
benchmark-gap
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day