Skip to content

Revert "feat: add pycln as a recommendation" #163

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

Closed
wants to merge 1 commit into from

Conversation

henryiii
Copy link
Member

Reverts #154, removes pycln as a recommendation, due to hadialqattan/pycln#81. I'm sorry for the issue; I usually check dependencies and adding an upper cap is a huge red flag for me, especially on Python version, but I never checked this one.

Copy link
Member

@eduardo-rodrigues eduardo-rodrigues left a comment

Choose a reason for hiding this comment

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

Fair point!

@henryiii
Copy link
Member Author

henryiii commented Nov 8, 2021

The next release will ease up on the version restriction. It's <4 instead of open due to Poetry's infectious version capping system, but as a practical matter, I think it's okay.

@hadialqattan
Copy link

Hi, I'm the creator of Pycln . I feel sorry about being too late, but I want to tell you that Python3.10 support has been added to Pycln (v1.1.0).

@hadialqattan
Copy link

hadialqattan commented Nov 13, 2021

BTW, now all Python3 versions are supported until Python4:

https://github.com/hadialqattan/pycln/blob/09a0068cedf1bdc4c2ab073f27c477b1485f2b78/pyproject.toml#L26

@henryiii
Copy link
Member Author

I'm happy that this won't happen again unless there's an actual code issue (which is totally fine and could happen to anyone). Let's keep the recommendation. Thanks! ✅

@henryiii henryiii closed this Nov 13, 2021
@henryiii henryiii deleted the revert-154-henryiii/feat/pycln branch February 28, 2022 16:09
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.

3 participants