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

fixed DeprecationWarning #737

Closed
wants to merge 16 commits into from
Closed

Conversation

LarryMartell
Copy link
Contributor

@LarryMartell LarryMartell commented Jul 24, 2023

fixed DeprecationWarning

Fixes #727

Removes support for Python 3.7.

@claudep
Copy link
Contributor

claudep commented Jul 24, 2023

As I commented in the previous PR, Python 3.7 is EOL, so it should be removed from the test matrix. The the install-requires will not be needed any more.

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 24, 2023

So are you saying this issue can be closed and this PR is not needed any more?

@claudep
Copy link
Contributor

claudep commented Jul 24, 2023

No, it's not. However, if 3.7 support is dropped, this will simplify this patch, as the try/except will not be necessary.

@LarryMartell
Copy link
Contributor Author

I have a PR our to fix the tests in master. Shall I remove the 3.7 support in that branch?

Copy link
Contributor

@claudep claudep left a comment

Choose a reason for hiding this comment

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

Thanks, you are on the right track!

.github/workflows/test.yml Outdated Show resolved Hide resolved
setup.py Show resolved Hide resolved
sorl/__init__.py Outdated Show resolved Hide resolved
@LarryMartell
Copy link
Contributor Author

After making these small changes the tests are failing in my forked branch, but it's not clear why.

https://github.com/LarryMartell/sorl-thumbnail/actions/runs/5650549930/job/15307090121#step:10:458

@uri-rodberg
Copy link
Contributor

@claudep This PR looks fine to me now. Do you still require changes or is it OK with you now? And why are the tests canceled and failing? I expected the tests to pass now.

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@uri-rodberg
Copy link
Contributor

The tests are very persnickety. The presence or absence of a blank line seems to make them pass or fail. On Mon, Jul 24, 2023 at 8:37 PM Larry Martell @.***> wrote:

The tests were passing until I made some very small changes Claude requested. It’s not clear to me at all why they’re failing now.

@LarryMartell Can you please add a blank line at the end of .github/workflows/test.yml, and a blank line at the end of sorl/__init__.py, and then we will check if the tests pass?

@claudep
Copy link
Contributor

claudep commented Jul 25, 2023

I created #738 to only make the Python 3.7 drop (and let Larry as author), so we can then concentrate on the version issue only.

@claudep
Copy link
Contributor

claudep commented Jul 25, 2023

According to https://pypi.org/project/setuptools-scm/#retrieving-package-version-at-runtime, we should still catch PackageNotFoundError for cases where the package is not installed (typically during tests or dev).

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@claudep
Copy link
Contributor

claudep commented Jul 25, 2023

Blank lines have nothing to do with the failure. Please read my comment above.

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@codecov
Copy link

codecov bot commented Jul 25, 2023

Codecov Report

Merging #737 (ab75335) into master (012258b) will not change coverage.
The diff coverage is 100.00%.

❗ Current head ab75335 differs from pull request most recent head 60ee202. Consider uploading reports for the commit 60ee202 to get more accurate results

@@           Coverage Diff           @@
##           master     #737   +/-   ##
=======================================
  Coverage   74.11%   74.11%           
=======================================
  Files          30       30           
  Lines        1700     1700           
=======================================
  Hits         1260     1260           
  Misses        440      440           
Files Changed Coverage Δ
sorl/__init__.py 100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@claudep
Copy link
Contributor

claudep commented Jul 25, 2023

Looks good. Try now to rebase on master, the only changed file should be sorl/__init__.py.

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@uri-rodberg
Copy link
Contributor

@LarryMartell Do you know how to rebase? This PR should be rebased on branch master. It looks to me it's still not rebased. Please read about rebasing and rebase all your commits on branch master.

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@uri-rodberg
Copy link
Contributor

Yes, I know how to rebase. My 727.1 branch has been rebased with master.

@LarryMartell You rebased origin/master and not upstream/master. Please run the following commands:

git remote add upstream https://github.com/jazzband/sorl-thumbnail.git

git remote -v

The results should be:

origin  https://github.com/LarryMartell/sorl-thumbnail.git (fetch)
origin  https://github.com/LarryMartell/sorl-thumbnail.git (push)
upstream        https://github.com/jazzband/sorl-thumbnail.git (fetch)
upstream        https://github.com/jazzband/sorl-thumbnail.git (push)

git fetch upstream

git rebase upstream/master

Remember that any time when we ask you to rebase branch master, we mean upstream/master and not origin/master. But it's a good practice to have origin/master always point to the same commit as upstream/master.

The results should be 2 files changed from upstream/master, one of them only with one blank line. Currently the PR shows me 5 files changed. If it doesn't change, please close this PR and create a new one, because maybe the PR doesn't take into account changes to branch master made after you created this PR.

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@LarryMartell
Copy link
Contributor Author

LarryMartell commented Jul 25, 2023 via email

@LarryMartell
Copy link
Contributor Author

Are there any issues with this PR that are preventing it from being accepted and merged?

@uri-rodberg
Copy link
Contributor

@LarryMartell Please contact me by email. Your mailbox is full.

@uri-rodberg
Copy link
Contributor

I'm going to create another PR instead of this PR. Closing this PR.

@uri-rodberg uri-rodberg closed this Aug 1, 2023
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.

DeprecationWarning from setuptools 67.5.0 and above
4 participants