Skip to content

bpo-40086: remove test_etree test case #19189

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

Merged
merged 10 commits into from
Mar 28, 2020
Merged

bpo-40086: remove test_etree test case #19189

merged 10 commits into from
Mar 28, 2020

Conversation

furkanonder
Copy link
Contributor

@furkanonder furkanonder commented Mar 27, 2020

@furkanonder
Copy link
Contributor Author

Since cElementTree was deprecated and removed in Python 3 with 36543. So this test is now skipped. So this test had to be removed.

furkan@manjaro ~/cpython$ ./python -m test test_typing -m test_etree -vvv == CPython 3.9.0a5+ (heads/master:62d21c9d90, Mar 27 2020, 16:10:32) [GCC 9.3.0]
== Linux-5.5.11-1-MANJARO-x86_64-with-glibc2.31 little-endian
== cwd: /home/furkan/cpython/build/test_python_20035
== CPU count: 8
== encodings: locale=UTF-8, FS=utf-8
0:00:00 load avg: 1.67 Run tests sequentially
0:00:00 load avg: 1.67 [1/1] test_typing
test_etree (test.test_typing.UnionTests) ... skipped 'cElementTree not found'


Ran 1 test in 0.000s

OK (skipped=1)

== Tests result: SUCCESS ==

1 test OK.

Total duration: 183 ms
Tests result: SUCCESS

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

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

I think that it would be more correct to not remove the test, but making it working with ElementTree (which uses the C implementation by default).

@furkanonder
Copy link
Contributor Author

I think that it would be more correct to not remove the test, but making it working with ElementTree (which uses the C implementation by default).

Such a note was written in the test function,Only relevant for Python 2.Wouldn't it be more accurate to remove the test since we are not using python2?

@serhiy-storchaka
Copy link
Member

If it is only relevant for Python 2, why it was added at first place? There is no test_typing in Python 2.

@ilevkivskyi
Copy link
Member

I think that it would be more correct to not remove the test, but making it working with ElementTree (which uses the C implementation by default).

+1

I think it makes sense to keep the test. IIRC the idea was to test that C functions don't cause runtime exceptions if used as types.

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

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

Please keep the comment.

@furkanonder
Copy link
Contributor Author

Please keep the comment.

Ok

@ilevkivskyi
Copy link
Member

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

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

We usually do not add NEWS entries for minor test changes. They do not affect the end Python user and do not have a useful information for they.

Especially since "This test was skipped" is not informative at all.

@furkanonder
Copy link
Contributor Author

We usually do not add NEWS entries for minor test changes. They do not affect the end Python user and do not have a useful information for they.

Especially since "This test was skipped" is not informative at all.

Should i delete my NEWS file?

@serhiy-storchaka
Copy link
Member

Please delete it.

@furkanonder furkanonder requested a review from ilevkivskyi March 28, 2020 11:48
@ilevkivskyi ilevkivskyi merged commit 34b0598 into python:master Mar 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news tests Tests in the Lib/test dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants