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

pj #81

Open
amotl opened this issue Apr 17, 2024 · 2 comments
Open

pj #81

amotl opened this issue Apr 17, 2024 · 2 comments

Comments

@amotl
Copy link
Member

amotl commented Apr 17, 2024

About

Automatically detect backends & initialize virtual environments for your Python repo clones.
Set up projects for development quickly.

-- https://github.com/coherent-oss/pj

Thoughts

The ideas of pj, conceived by @bswck / @coherent-oss, resonate well with a few of pueblo.ngr. Thanks, Bartosz.

@bswck
Copy link

bswck commented Apr 17, 2024

Thank you for mentioning. Let me know if you're willing to collaborate on the project in its earliest stages.

@amotl
Copy link
Member Author

amotl commented Apr 17, 2024

Hi Bartosz. I probably will not find much time, apologies. On the other hand, please feel free to cherry-pick anything you may need, or find interesting, from the implementation of pueblo.ngr.

If you think pj would be ready to replace the Python runner of pueblo.ngr, please let me know, so we may swap it in. Contrary to its docstring documentation, it is currently able to detect/handle/invoke Python project variants that use either of requirements.txt, setup.py, setup.cfg or pyproject.toml (pip and Poetry), as a minimal project bootstrap file.

This may actually count as a contribution we may collaborate on: Eventually improving pj to make it ready for library use, in this case. If that idea resonates with you, let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants