Not sure why the Windows (>=3.9) uses the absolute file path when Linux and MacOS use the relative one. Maybe someone with a Windows system can help debug this?

Not sure why the Windows (>=3.9) uses the absolute file path when Linux and MacOS use the relative one. Maybe someone with a Windows system can help debug this?

Not sure why the difference either. The closest change in Python 3.9 related to this I could find is the second bullet point herehttps://docs.python.org/3/whatsnew/3.9.html#other-language-changes but it doesn't explain the difference in behavior between operating systems.

It is probably safe to just shorten the file paths in the output traceback before comparing it with the expected output. I tried this patch with the test case "mypyc/test/test_run.py::TestRun::run-loops.test::testForIterable" and it seems to fix the issue:

diff --git a/mypyc/test/test_run.py b/mypyc/test/test_run.pyindex 37de192a9..112074047 100644--- a/mypyc/test/test_run.py+++ b/mypyc/test/test_run.py@@ -315,6 +315,7 @@ class TestRun(MypycDataSuite):             # TODO: testDecorators1 hangs on 3.12, remove this once fixed             proc.wait(timeout=30)         output = proc.communicate()[0].decode("utf8")+        output = output.replace(f'  File "{os.getcwd()}{os.sep}', '  File "')         outlines = output.splitlines()         if testcase.config.getoption("--mypyc-showc"):

It is kind of a hack but I don't know how to fix it otherwise.

Off-topic: why not use a more recent python version like 3.12 or 3.11 for Windows tests so that we don't have to update it every year?

Not sure why the Windows (>=3.9) uses the absolute file path when Linux and MacOS use the relative one. Maybe someone with a Windows system can help debug this?

Not sure why the difference either. The closest change in Python 3.9 related to this I could find is the second bullet point herehttps://docs.python.org/3/whatsnew/3.9.html#other-language-changes but it doesn't explain the difference in behavior between operating systems.

Thanks! Yeah, that seems to be the culprit. Pushed our patch as it's probably the best way forward here, especially since the path deviates depending on the OS used to run the tests.

Off-topic: why not use a more recent python version like 3.12 or 3.11 for Windows tests so that we don't have to update it every year?

I don't know the exact reason but I believe the intention is to always test the "oldest" Python release with Windows. Anyway, the issue mentioned earlier persists even in newer versions.That was one of the first things I checked.

I think mypy 1.12 at least should probably still support 3.8. That way we might have a release that supports both 3.13 and 3.8. Runtime support for 3.8 is needed for projects that use mypyc and target 3.8, since it's not possible to run mypyc on a more recent Python version and target an older version.

I think mypy 1.12 at least should probably still support 3.8. That way we might have a release that supports both 3.13 and 3.8.

One option of course. Though I'm not sure that's really necessary. We didn't do that the last time.3.7 was dropped with mypy1.5.0 whereas only1.6.0 added support for3.12. I suspect many projects are looking into dropping support for3.8 in the next few months anyway if they haven't already started doing so.

Though I'm not sure that's really necessary.

Yeah it doesn't seem necessary, but if it doesn't take any significant effort, I think it's still worth doing. 3.8 still appears to be more popular than 3.9 or 3.12, based on PyPI stats (https://pypistats.org/packages/mypy).

As of this week, Python 3.8 accounts for 10.5% of all mypy downloads and 4.8% of all downloads of mypy 1.11.*

As of this week, Python 3.8 accounts for 10.5% of all mypy downloads and 4.8% of all downloads of mypy 1.11.*

Would you recommend waiting longer to drop 3.8? I'd say it's probably still fine to do after the 1.12 release. Users interested in new type checking features are more likely to be using newer Python versions.

Additionally, it will still be possible to lint 3.8 code (for the time being) and devs can always continue using 1.12 if they are stuck on 3.8.

Sorry, I should have added an opinion, I think it's fine to drop. 4.8% isn't a lot and it will drop further.
pypistats doesn't let you see Python version breakdown for a specific mypy version, I was curious how much less than the 10.5% it would be for 1.11.*

Let's make the decision when we are closer to 1.13 release? If there have been significant regressions or issues with new functionality in 1.12 (that we haven't fixed in a point release), we can extend 3.8 support to 1.13 so that there are more options for projects that want to support both 3.8 and 3.13. Or we can decide to have one more release supporting 3.8 if it's only minimal extra effort at that point.

When this PR is closer to being merged, I suggest runningpyupgrade --py39-plus $(git ls-files | grep \.py$ | grep -v setup.py) , or as a follow-up PR, and storing the commit hash in.git-blame-ignore-revs

When this PR is closer to being merged, I suggest runningpyupgrade --py39-plus $(git ls-files | grep \.py$ | grep -v setup.py) , or as a follow-up PR, and storing the commit hash in.git-blame-ignore-revs

👍🏻 Yeah, I have planned to do that. It's intentionally omitted here to keep the changes to a minimum.

We are aiming at having another release branch created in late October/early November. If we can stick to this schedule, I think we can manage another feature release with 3.8 support, and we'll drop support afterwards.

We are aiming at having another release branch created in late October/early November. If we can stick to this schedule, I think we can manage another feature release with 3.8 support, and we'll drop support afterwards.

Sounds good 👍🏻 Just wanted to fix the merge conflicts here.

We can merge this after the release branch for 1.14 has been created.

According tomypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

Eyeballing it looks like 3.8 usage has halved since October. Thanks for keeping this PR fresh!