-
Notifications
You must be signed in to change notification settings - Fork 167
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
Test lpython.py with multiple CPython versions #1827
Comments
How about just picking CPython 3.11 and committing to it to reduce our
workload until LPython is 99% feature-complete?
…On Wed, May 17, 2023 at 12:21 PM Ondřej Čertík ***@***.***> wrote:
We need to test the lpython.py tests in integration_tests with multiple
CPython versions. It looks like there are some bugs related to that.
—
Reply to this email directly, view it on GitHub
<#1827>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABSRR7VRIBO7IKZOPLRVT3XGUQNDANCNFSM6AAAAAAYFQ2Y2E>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
We currently test with |
We should test with all the Python versions at: https://www.python.org/downloads/, so let's test with 3.8, 3.10, 3.11. Once 3.12 is released, let's test with it as well. To save time, we can probably skip 3.9. Once 3.8 is deprecated, we can test 3.9 instead. |
It seems
Please, could you share what we should do? |
Is it subscriptable in Python 3.9? If so, then I would drop 3.8 and only support >= 3.9. |
It seems annotation for |
Ok, then let's test Python 3.9, 3.10 and 3.11 explicitly, all three. Once 3.12 is released in October, we'll add it as well. |
For Python 3.8 and before, it seems one needs to use |
Sure, got it. |
We need to test the lpython.py tests in integration_tests with multiple CPython versions. It looks like there are some bugs related to that.
The text was updated successfully, but these errors were encountered: