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

MNT/MAINT upgrading isort to 5.12.0 #294

Merged

Conversation

omar-araboghli
Copy link
Contributor

Closes #293

@omar-araboghli omar-araboghli changed the title MNT/MAINT #293: upgrading isort to 5.12.0 MNT/MAINT upgrading isort to 5.12.0 Feb 6, 2023
@BenjaminBossan
Copy link
Collaborator

BenjaminBossan commented Feb 6, 2023

Thanks for providing a fix so quickly.

Before going ahead, could you please describe how I could replicate the initial problem? I tried creating a fresh environment as described in CONTRIBUTING.rst (except I used conda instead of mamba) and it worked without your fix (incl. running pre-commit run). Is it something that only surfaces when using poetry? From the commit you linked, it's not clear to me why that would break pre-commit.

Independent of that, I think we can still merge it, I just want to better understand the issue.

@omar-araboghli
Copy link
Contributor Author

@BenjaminBossan Thanks for your feedback! Interesting... These are the reproduction steps:

  • Create a conda environment via PyCharm with python 3.10
  • python -m pip install -e ".[tests,docs]"
  • conda install pre-commit
  • pre-commit install

Maybe I should have followed CONTRIBUTING.rst more strictly, but as you already said. It's safer to merge and make skops up-to-date with its dependencies.

@BenjaminBossan
Copy link
Collaborator

BenjaminBossan commented Feb 6, 2023

  • Create a conda environment via PyCharm with python 3.10

Interesting, this seems to be the only step that differs. Do you have an idea what PyCharm could be doing differently here that would cause the issue? I have conda 23.1.0 but I don't think the conda version should be the cause. And somehow, in the error log you pasted, poetry seems to be involved. Does PyCharm use that under the hood?

@omar-araboghli
Copy link
Contributor Author

From the error log I understood that an older version of isort is being installed based on isort's recent pyproject.yaml. I also couldn't find any different behavior while creating a conda environment by PyCharm so far. So I freshly cloned the repo and exactly followed the contributing guidelines this time and still getting the same error 😮.

@BenjaminBossan BenjaminBossan merged commit 4181e6a into skops-dev:main Feb 6, 2023
@BenjaminBossan
Copy link
Collaborator

Heh, strange. Still, I merged since it shouldn't hurt and there may be other PyCharm users out there who run into the same issue (note that it seems like they backported the fix to 5.11 too: https://github.com/PyCQA/isort/releases/tag/5.11.5).

For the @skops-dev/maintainers and others who work on the repo, please make sure to update pre-commit, not sure if it does so automatically.

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.

pre-commit fails due to isort upgrade
2 participants