feat: Migrate to uv from pipenv

[DhavalGojiya]

Description

Migrated from Pipenv to uv

Added support for pyproject.toml with uv

Removed files:

setup.py
setup.cfg
MANIFEST.in
Pipfile
Pipfile.lock

---

uv build or pipx run build

Source Distribution

Wheel Distribution

[ulgens]

Thank you so much for this. I was plannign to handle the CI pipeline first, then come to this but that order is not a strict requirement.

[ulgens]

This list doesn't match the versions from #226 The project is in a transition period, and we are not testing againist any Python version yet but this is the closest thing we have to "supported Python list".

[ulgens]

I'd also recommend updating the existing classifiers in setup.py file with supported versions before changing the list.

[DhavalGojiya]

@ulgens OK

[DhavalGojiya]

I also think we should drop support for Python 3.8 and Python 3.9 for this package, as they are already EOL before this uv PR is merged.

I checked the test cases and noticed that they use the pytz package and it is also not available by default (Third party library).

Since Python 3.9+ introduced the zoneinfo library, we can replace pytz with it.
We can proceed step by step.

Any thoughts, @ulgens?

[ulgens]

I also think we should drop support for Python 3.8 and Python 3.9 for this package, as they are already EOL before this uv PR is merged.

I was trying to keep an overlap for supported Django - Python versions between the latest release and the next one, so that the update process will be less painful for the users but I just removed django<4.2 yesterday (the latest release was supporting <=4.1) to have a better experience with the CI testing adoption. Removing 3.8 and 3.9 is definitely possible, but I don't want to prioritize it if it's not absolutely necessary.

I'm okay with adding pytz depedency for a temporary period.

[DhavalGojiya]

I also think we should drop support for Python 3.8 and Python 3.9 for this package, as they are already EOL before this uv PR is merged.

I was trying to keep an overlap for supported Django - Python versions between the latest release and the next one, so that the update process will be less painful for the users but I just removed django<4.2 yesterday (the latest release was supporting <=4.1) to have a better experience with the CI testing adoption. Removing 3.8 and 3.9 is definitely possible, but I don't want to prioritize it if it's not absolutely necessary.

I'm okay with adding pytz depedency for a temporary period.

👍

[DhavalGojiya]

Update:

• Added pytz to the dev dependencies temporarily
• Rebased successfully with the latest project state
• Updated classifiers

[ulgens]

Thanks for the update.

About pytz, is it useful now? Were you able to run tests locally, or does the project itself depend on it? If not, I'd recommend adding the pytz where it's useful.

Do we still need ez_setup.py file?

[DhavalGojiya]

Thanks for the update.

About pytz, is it useful now? Were you able to run tests locally, or does the project itself depend on it? If not, I'd recommend adding the pytz where it's useful.

Do we still need ez_setup.py file?

Currently working on it (test cases)

[DhavalGojiya]

ez_setup.py

We don't need this file anymore, also it's too complex.