py-libp2p Revamp: Organizational and Code Structure Contributions

[seetadev]

@arcinston : Your recent contributions and insights into improving py-libp2p—both at the organization level and in code architecture—have been truly fantastic. 🙌 We're excited about the direction you're helping to shape and believe your ideas can significantly elevate the project.

We’d love to invite you to share your thoughts, suggestions, or even RFC-style proposals here with the broader team and community.

Feel free to start threads on:

Architectural improvements you're implementing or envisioning

Design patterns or refactors that have helped

Ideas on structuring the project more cleanly for contributors

Anything that could use community input!

Looking forward to your input and further collaboration. 🚀

[arcinston]

1. migration from setup.py to pyproject.toml (which is the current standard )to bring native support for all python package managers (including pip , poetry , uv) to make managing packages seammless
2. current CI / Pre-commit hook fails to catch a lot of basic type issues and possible runtime errors (also pretty bloated imo) , using a standard linter/formatter to do this which a seperate config file makes the whole process cleaner , i would recommend using Ruff (as both linter and formatter) - v fast and seemless - i will ensure that the previously used linting and formating rules are used

examples of this

1. tcp.py (pyright throwing type error)

2. echo.py

the above issue is pretty imp to resolve - as broken code can possibly be pushed

low-priority

1. personally find pre-commit hooks not as great - prevent using the version control system locally , would be in favour of replacing them with Github Actions for CI
   Ruff has a github action for typechecks linting & formatting https://github.com/astral-sh/ruff-action
   can add more soon to have much better DevEx

[arcinston]

https://github.com/arcinston/py-libp2p - have a Work In Progress fork here with the above mentioned changes