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

Make picotool available on PyPI #2

Open
franciscod opened this issue Nov 4, 2015 · 3 comments
Open

Make picotool available on PyPI #2

franciscod opened this issue Nov 4, 2015 · 3 comments

Comments

@franciscod
Copy link

@franciscod franciscod commented Nov 4, 2015

It'd be really nice to do pip install picotool :) What do you think?

@dansanderson
Copy link

@dansanderson dansanderson commented Aug 30, 2021

I've added a setup.py file for easier installation. I'm not sure I ever want to upload this to PyPI, but I'll consider it if picotool ever goes 1.0. :)

@hsandt
Copy link

@hsandt hsandt commented Apr 20, 2022

Hi, I followed the new instructions and doing a raw pip install . which generates the files (esp. p8tool) locally. As I see them in my VCS, I assume it's not exactly the intended process? I'm fine with having the built file locally, we could just add p8tool and the build/ folder to .gitignore, then I can manually symlink my ~/.local/bin/p8tool to this local p8tool.

However, I tried a pip install --user . and this one gave the expected result, installing p8tool directly in my ~/.local/bin. Maybe it's what you wanted us to do?

I know you can also sudo pip install . and that may put the binary in some /usr/bin, but I'm trying to work with user folders as much as possible so I didn't try this one. I think this one may also generate local files anyway.

@dansanderson
Copy link

@dansanderson dansanderson commented Apr 20, 2022

These are just the standard behaviors of pip install, so the instructions are just meant to say "this is how to pip install a package from a directory." I agree that --user is the right method for anyone installing into their system's Python install (vs. a virtual environment). That might be worth mentioning in the docs, especially if I'm not going to upload to PyPI.

(I'm not entirely opposed to uploading to PyPI but I wanted to clean things up before doing so, so it's a pending item. I have an unfinished 0.2 that I haven't committed yet.)

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

3 participants