Add rye as a package manager.

[manisha841]

• Added rye config

Use the following commands to set up rye in your system.

• Install rye in your machine: https://rye-up.com/guide/installation/
• rye sync
• rye add package
• rye run pre-commit install
• rye run dev

[horrormyth]

One minor comment otherwise great stuff ⛩️ 💪

[horrormyth]

It would also be good to hint that sync is necessary, as add does not provide the packages to the working env

[manisha841]

Sure

[horrormyth]

Nit: Probably not needed, commit has all the necessary information

[manisha841]

I think these informations are necessary as they serve as the main configuration of the project, but open for discussions.

[horrormyth]

I meant the author details

[imkaka]

project author should be moest-np.

[sapradhan]

I see a lot of effort being put into this, greatly appreciate it.
I had not heard about rye before this, not much into python ecosystem, so a few questions -

• How wide is the adoption of rye as a package manager?
• skimming through the documentation, rye does appear to be better than pip, in par with modern package managers. But I believe it does not ship with python installation, so for a newbie like me, it would be one more thing to install and learn. For a project of this size would it add value to make this switch?

[horrormyth]

I see a lot of effort being put into this, greatly appreciate it. I had not heard about rye before this, not much into python ecosystem, so a few questions -

• How wide is the adoption of rye as a package manager?
• skimming through the documentation, rye does appear to be better than pip, in par with modern package managers. But I believe it does not ship with python installation, so for a newbie like me, it would be one more thing to install and learn. For a project of this size would it add value to make this switch?

Rye manages the package, including the virtual environments and Python one needs, so I think it would be much easier to use Rye as a one-stop solution, as one won't need to worry about Python's virtual environments madness.

For a project of this size would it add value to make this switch?

I agree that for the size of this project, it might be a bit cumbersome, but if we think from the dev's perspective, it might be better off with this one with the main rationale being separation and management of the packages, depending on the dev, test, and ... environment and managing the virtualenvs. After all, we should always opt for the betterment direction. Since we are already using the Streamlint app, I am sure there will be many more packages coming in the future. It's always good to have one less tech debt from the get-go.

[imkaka]

Great work 🎉👏

[imkaka]

project author should be moest-np.