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

Installation via pip #40

Closed
nikolay opened this issue Jan 3, 2015 · 12 comments
Closed

Installation via pip #40

nikolay opened this issue Jan 3, 2015 · 12 comments

Comments

@nikolay
Copy link

nikolay commented Jan 3, 2015

It would be nice to upload icdiff to PyPI for easier installation on Linux.

@yprez
Copy link

yprez commented Jan 5, 2015

+1

In the meantime, this works fine:

pip install git+https://github.com/jeffkaufman/icdiff.git

@nikolay
Copy link
Author

nikolay commented Jan 6, 2015

@yprez Yeah, that's how I use it for now, but would still be better to upload to PyPI.

@colonelpanic8
Copy link

+1

1 similar comment
@alaindomissy
Copy link

+1

@amirouche
Copy link

icdiff all the things 👍

@vnitinv
Copy link

vnitinv commented Feb 25, 2016

@jeffkaufman If you are fine I can take initiative to upload it to PyPI. Even though I will be uploading it you only will be seen as the owner out there as it fetch details from setup.py

@albfan
Copy link

albfan commented May 21, 2017

Why this is still open? https://pypi.python.org/pypi/icdiff

@nikolay
Copy link
Author

nikolay commented May 21, 2017

@albfan @jeffkaufman Because it's outdated: current version is 1.9, not 1.8.6 (which is not official anyway), and that is not published by @jeffkaufman himself, i.e. the PyPI package is risky to be used.

@albfan
Copy link

albfan commented May 22, 2017

@nikolay better then to close this (as was already done) and open another issue to upgrade pip. no?

@nikolay
Copy link
Author

nikolay commented May 22, 2017

@albfan Not really! We have no idea who's published that (user vnitinv). Advising people to use untrusted code is a bad advice! Especially when they have published a version that's not official, i.e. v1.8.6, not present in the releases' list here!

I know you guys really love to close issues and move over, this pseudo-agile mentality, in this case, can hurt people.

@albfan
Copy link

albfan commented May 22, 2017

So you want an upgrade issue and a sign pipy module issue.

Only meta issues with lot of goals can hurt, everything else can be splitted to simple tasks. If maintainer sees this issue closed why you don't see it the same way? publish to pipy is done, issues are related of what you ask for, not about all you think "install via pip" means.

Note: For a possible trust pipy issue: https://security.stackexchange.com/questions/79326/which-security-measures-does-pypi-and-similar-third-party-software-repositories. seems pipy is untrusted by default so nothing prevents a user on pipy to get a name like this maintainer.

@vnitinv Can you upgrade pipy to 1.9.0?

@vnitinv
Copy link

vnitinv commented May 30, 2017

@albfan it's pending from my end only. Will be done by this weekend.

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

8 participants