py-ipfs

by ipfs-shipyard

ipfs-shipyard / py-ipfs

python implementation of ipfs

418 Stars 89 Forks Last release: Not found MIT License 57 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

py-ipfs

IPFS Logo

Made by the IPFS Community IRC #py-ipfs on chat.freenode.net Matrix #py-ipfs:ninetailed.ninja Standard README Compliant

Python implementation of IPFS

Python implementation of IPFS, the InterPlanetary File System. Not even remotely done yet.

For the current status, and where you can help, please see issue 49.

Table of Contents

Background

IPFS is a distributed file system that seeks to connect all computing devices with the same system of files. In some ways, this is similar to the original aims of the Web, but IPFS is actually more similar to a single bittorrent swarm exchanging git objects.

IPFS could become a new major subsystem of the internet. If built right, it could complement or replace HTTP. It could complement or replace even more. It sounds crazy. It is crazy.

Install

Not ready for prime time yet

Usage

Also not ready for prime time yet

Documentation

To build the Sphinx docs, execute:

shell
$ make -C docs/  # html, pdf etc.

Contribute

IPFS implementation in Python is a work in progress. As such, there's a few things you can do right now to help out:

  • Get in touch! You can find us on #py-ipfs on chat.freenode.org!
    • A Matrix chat option is also provided. Please note however that, at the time of writing, the default
      matrix.org
      server is severely overloaded and your messages may only arrive with extreme delay; using a different homeserver is hence highly recommended.
  • Check out issue 49 for an up-to-date list (maintained by @alexander255) of tasks that could use your help. Feel free to ask questions on that and we'll try to help. Be sure to drop a note if there is anything you'd like to work on and we'll update the issue to let others know.
  • Perform code reviews. More eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
  • Take a look at both go-ipfs and js-ipfs (which we intend to follow to a point), and also at some of the planning repositories or issues: for instance, the libp2p spec here. Contributions here that would be most helpful are top-level comments about how it should look based on our understanding. Again, the more eyes the better.
  • Add tests. There can never be enough tests.
  • Contribute to the FAQ repository with any questions you have about IPFS or any of the relevant technology. A good example would be asking, "What is a merkledag tree?". If you don't know a term, odds are someone else doesn't either. Eventually, we should have a good understanding of where we need to improve communications and teaching together to make IPFS and IPN better.
  • TODO: write our own
    CONTRIBUTE.md
    similar to IPFS's and once we know what we're doing and who's doing it.

Please be aware that all interactions related to IPFS, libp2p and Multiformats are subject to the IPFS Code of Conduct.

License

MIT

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.