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

[not an issue] suggestion for enhancing pip from https to leverage to ipfs #4215

Closed
johndpope opened this issue Jan 4, 2017 · 4 comments
Closed
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality

Comments

@johndpope
Copy link

did anyone ever consider using ipfs.io (interplanetary file system) as the backbone of pip?

ipfs has the capabilities of git but adds p2p in the mix - so it sort of swarms the availability of packages. https://ipfs.io/

It's would enable

  • military grade fault tolerance / fail over
  • total backups of pypy sources.
  • leverage local installations on networks / docker containers
  • avoid redundant http downloads

it would probably make more sense for docker to integrate this under the hood as that would nip the problem in the bud. but a local pip based install which could be enabled would revolutionize system setups. https://github.com/ipfs/ipfs

it would probably resemble transmission ui as the host/ computer would become a seeder.
Needs planning / thinking through.

@Ivoz Ivoz added the type: enhancement Improvements to functionality label Jan 4, 2017
@dstufft
Copy link
Member

dstufft commented Mar 30, 2017

While I think that IPFS is an incredibly interesting idea, I don't think that this is something that makes a lot of sense for pip itself. As I understand it, it would require having some sort of persistent pip process to handle the p2p nature of it (since without a process, someone can't be a peer to upload to others) but pip doesn't run as a persistent process, it only runs temporarily.

@dstufft dstufft closed this as completed Mar 30, 2017
@johndpope
Copy link
Author

consider that the running pip would fetch from an ipfs link which would be same as a url link with associated file hash.

@AuHau
Copy link

AuHau commented Feb 6, 2019

Just for reference, I am starting an initiative to bring IPFS to Python packaging ecosystem. Any feedback or help are welcomed!

The initial proposal is here: AuHau/dpip#1

Just out of curiosity, what do you think about directly depends on pip as a package and extending its capability versus calling pip as an external dependency (basically spinning a subprocess)?

@lock
Copy link

lock bot commented May 29, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label May 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality
Projects
None yet
Development

No branches or pull requests

4 participants