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

Add ZoneInfo support. #93

Merged
merged 1 commit into from Dec 20, 2021
Merged

Add ZoneInfo support. #93

merged 1 commit into from Dec 20, 2021

Conversation

hramezani
Copy link
Collaborator

@hramezani hramezani force-pushed the zoneinfo branch 2 times, most recently from c113065 to ab03036 Compare December 13, 2021 09:52
@slashmili
Copy link
Owner

@hramezani do you think we should bump the major version?

@@ -1,5 +1,9 @@
# Changelog

## Unreleased
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet! Nice idea to keep track of changes 👏

@hramezani
Copy link
Collaborator Author

@hramezani do you think we should bump the major version?

Sure!

Before release, do we want to drop support for Python < 3.6?

@slashmili
Copy link
Owner

TBH I don't know. What is wrong with Python < 3.6?

@hramezani
Copy link
Collaborator Author

TBH I don't know. What is wrong with Python < 3.6?

Nothing, as Python < 3.6 no longer receives updates and most of python packages usually drop support for unsupported python versions, I would suggest dropping python < 3.6 support.

If we want to drop the support we can postpone the release otherwise we can release now.

@hramezani
Copy link
Collaborator Author

@slashmili I would suggest first merging this PR and releasing a major version then we can think about dropping python < 3.6 support. I am going to make django-jalali compatible with Django 4.0 and this fix is needed there!

Copy link
Collaborator

@farzadghanei farzadghanei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice 👍

I don't see if we're breaking backward compatibility, so we can just increase the minor version.
I don't see the benefit of dropping older python versions now, we can keep them supported, until the day it becomes a burden (if at all), then we can increase major version and drop support for older versions.

@hramezani
Copy link
Collaborator Author

Thanks @farzadghanei for the review.
Yes, I think we can just increase the minor version for now.

I don't see the benefit of dropping older python versions now

I think there are some benefits like using new features in python(for example string formating). make development easier because you don't need to check multiple python version specifications. also, by dropping a python version support(for example 2.7) we will push users to upgrade to a newer python package which is good IMHO. and they still have the possibility to use the older version of this package which supports old python.
Also, I can see we support Python 2.6 which is not in our pipeline and we don't test the changes against it.

@hramezani hramezani merged commit 68eb4a5 into slashmili:main Dec 20, 2021
@hramezani hramezani deleted the zoneinfo branch December 20, 2021 09:39
@hramezani
Copy link
Collaborator Author

@farzadghanei I merged the PR. Could you please make a new release? As I mentioned before, I need it for the django-jalali

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants