-
-
Notifications
You must be signed in to change notification settings - Fork 497
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
Conversation
As I commented in the previous PR, Python 3.7 is EOL, so it should be removed from the test matrix. The the |
So are you saying this issue can be closed and this PR is not needed any more? |
No, it's not. However, if 3.7 support is dropped, this will simplify this patch, as the try/except will not be necessary. |
I have a PR our to fix the tests in master. Shall I remove the 3.7 support in that branch? |
There was a problem hiding this 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!
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 |
@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. |
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.
…On Mon, Jul 24, 2023 at 5:36 PM אורי ***@***.***> wrote:
@claudep <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#737 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7MIFNAXQL6CYCWH2NIALXR4IIRANCNFSM6AAAAAA2VR6BWQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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.
On Mon, Jul 24, 2023 at 5:36 PM אורי ***@***.***> wrote:
> @claudep <https://github.com/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.
>
> —
> Reply to this email directly, view it on GitHub
> <#737 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAJ7MIFNAXQL6CYCWH2NIALXR4IIRANCNFSM6AAAAAA2VR6BWQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
@LarryMartell Can you please add a blank line at the end of |
I created #738 to only make the Python 3.7 drop (and let Larry as author), so we can then concentrate on the |
According to https://pypi.org/project/setuptools-scm/#retrieving-package-version-at-runtime, we should still catch |
test.yml already had a blank line. Added one to __init__.py, tests still
failing.
On Mon, Jul 24, 2023 at 10:40 PM אורי ***@***.***> wrote:
… 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:
… <#m_-5043465268867401432_>
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 <https://github.com/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?
—
Reply to this email directly, view it on GitHub
<#737 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7MICU2CHH75GCZKHO6ZTXR5L4XANCNFSM6AAAAAA2VR6BWQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Blank lines have nothing to do with the failure. Please read my comment above. |
Here is the error from the test:
sorl/__init__.py:8:1: W391 blank line at end of file
Which comment? About PackageNotFound? I added that.
…On Tue, Jul 25, 2023 at 7:19 AM Claude Paroz ***@***.***> wrote:
Blank lines have nothing to do with the failure. Please read my comment above.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Codecov Report
@@ Coverage Diff @@
## master #737 +/- ##
=======================================
Coverage 74.11% 74.11%
=======================================
Files 30 30
Lines 1700 1700
=======================================
Hits 1260 1260
Misses 440 440
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Looks good. Try now to rebase on master, the only changed file should be |
Removed blank line, tests are passing now.
…On Tue, Jul 25, 2023 at 7:30 AM Claude Paroz ***@***.***> wrote:
Looks good. Try now to rebase on master, the only changed file should be
sorl/__init__.py.
—
Reply to this email directly, view it on GitHub
<#737 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7MIFGD3EWYDAIHFM52RLXR7J6HANCNFSM6AAAAAA2VR6BWQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@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. |
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:
The results should be:
Remember that any time when we ask you to rebase branch master, we mean The results should be 2 files changed from |
I have a fork and from github I sync my fork's master with the upstream, so
it should be the same. But in any case I followed your exact directions and
rebased.
The 5 files shown as modified have indeed all been modified in my branch.
On Tue, Jul 25, 2023 at 9:44 AM אורי ***@***.***> wrote:
… Yes, I know how to rebase. My 727.1 branch has been rebased with master.
@LarryMartell <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#737 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7MIB7BVXYDIR2NGJNLI3XR7ZWFANCNFSM6AAAAAA2VR6BWQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
There are 2 things in this branch - fixing the deprecation warning and
removing python 3.7.
On Tue, Jul 25, 2023 at 9:57 AM Larry Martell ***@***.***>
wrote:
… I have a fork and from github I sync my fork's master with the upstream,
so it should be the same. But in any case I followed your exact directions
and rebased.
The 5 files shown as modified have indeed all been modified in my branch.
On Tue, Jul 25, 2023 at 9:44 AM אורי ***@***.***>
wrote:
> Yes, I know how to rebase. My 727.1 branch has been rebased with master.
>
> @LarryMartell <https://github.com/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.
>
> —
> Reply to this email directly, view it on GitHub
> <#737 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAJ7MIB7BVXYDIR2NGJNLI3XR7ZWFANCNFSM6AAAAAA2VR6BWQ>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Are there any issues with this PR that are preventing it from being accepted and merged? |
@LarryMartell Please contact me by email. Your mailbox is full. |
I'm going to create another PR instead of this PR. Closing this PR. |
fixed DeprecationWarning
Fixes #727
Removes support for Python 3.7.