-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Merging test_pep263.py and test_coding.py #62248
Comments
There are two test files for the same feature -- defining Python source code encodings (PEP-263). It is not clear where new tests should be added. Perhaps two files should be merged into the one file. test_pep263.py was added in 2002, test_coding.py was added in 2005. |
For a bug fix release, I consider refactoring of test cases inappropriate. If they really ought to be merged, I consider neither file name particularly descriptive, so perhaps a new file name should be used altogether (e.g. test_source_encoding). |
This SGTM. I particularly dislike test_pep*, especially when I can't remember the pep number. |
OK, I think I fixed this. I merged the two tests into one, called test_source_encoding.py. It doesn't fail, and I'm not sure what else I need to do. Patch is attached. This is also my first patch, so please tell me if I'm doing anything wrong. |
New changeset 00a199c265c3 by Serhiy Storchaka in branch 'default': New changeset 3b906421245d by Serhiy Storchaka in branch 'default': New changeset 464e8fd7300d by Serhiy Storchaka in branch 'default': |
Merging itself is trivial. The trick is how preserve the history of both files. Unfortunately this can't be represented in one mercurial patch. Three commits needed for this. |
New changeset 776e9b8bdd96 by Serhiy Storchaka in branch '2.7': New changeset deadfb03dec0 by Serhiy Storchaka in branch '2.7': New changeset c42d743779bd by Serhiy Storchaka in branch '2.7': |
Backported to 2.7 for the sake of easier backporting new tests. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: