Skip to content
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

Get rid of our pydep fork in favor of a single script #2816

Closed
sschuberth opened this issue Jul 2, 2020 · 3 comments
Closed

Get rid of our pydep fork in favor of a single script #2816

sschuberth opened this issue Jul 2, 2020 · 3 comments
Labels
analyzer About the analyzer tool

Comments

@sschuberth
Copy link
Member

That said, I was long dreaming of actually getting rid of our pydep fork completely, in favor of a single Python script that we maintain as part of this repository and temporarily write out when needed like we already do e.g. for Bundler.

Originally posted by @sschuberth in #2703 (comment)

@sschuberth sschuberth added analyzer About the analyzer tool enhancement labels Jul 2, 2020
@tsteenbe
Copy link
Member

tsteenbe commented Jul 24, 2020

The Python foundation is funding a new pip dependency resolver see https://pyfound.blogspot.com/2019/11/seeking-developers-for-paid-contract.html and related ticket pypa/pip#988

We could investigate https://github.com/ddelange/pipgrip/ as a temporary replacement for our pydep fork pending pip getting its own dependency resolver.

@sschuberth
Copy link
Member Author

pipgrip indeed looks interesting, but I'm having issues with it. Let's see how responsive the developer is.

@sschuberth
Copy link
Member Author

pipgrip indeed looks interesting, but I'm having issues with it. Let's see how responsive the developer is.

The developer actually was very responsive and the issue was fixed along with another one that I had mentioned.

sschuberth added a commit that referenced this issue Apr 11, 2022
The original `pydep` tool is archived by now [1] and running it with
newer Python versions might cause problems [2]. So replace it by simply
"running" `setup.py` with the option for the metadata field to get.

Resolves #2816.

[1]: https://github.com/sourcegraph/pydep
[2]: #5159 (comment)

Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth added a commit that referenced this issue Apr 11, 2022
The original `pydep` tool is archived by now [1] and running it with
newer Python versions might cause problems [2]. So replace it by simply
"running" `setup.py` with the option for the metadata field to get.

Resolves #2816.

[1]: https://github.com/sourcegraph/pydep
[2]: #5159 (comment)

Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth added a commit that referenced this issue Apr 11, 2022
The original `pydep` tool is archived by now [1] and running it with
newer Python versions might cause problems [2]. So replace it by simply
"running" `setup.py` with the option for the metadata field to get.

Resolves #2816.

[1]: https://github.com/sourcegraph/pydep
[2]: #5159 (comment)

Signed-off-by: Sebastian Schuberth <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer About the analyzer tool
Projects
None yet
Development

No branches or pull requests

2 participants