GujaLomsadze opened a new pull request, #50639:
URL: https://github.com/apache/arrow/pull/50639

   ### Rationale for this change
   
   `python/scripts/test_imports.py` and `python/scripts/test_leak.py` are 
leftovers from an older test layout. They are isolated from the current test 
structure, not referenced by CI, packaging or the pytest suite, and not 
documented anywhere. Their `test_`-prefixed names have also caused accidental 
pytest collection in the past (ARROW-1033).
   
   Closes #49046, per @pitrou's "I would probably remove them".
   
   One open question from the issue description: @raulcd noted `test_leak.py` 
could be worth keeping as a snippet showing how to check for leaks, if it were 
documented. This PR removes it, following the later comment. Happy to instead 
restore it and document it under the developer docs if reviewers prefer that 
direction — just say the word.
   
   ### What changes are included in this PR?
   
   Deletion of `python/scripts/test_imports.py` and 
`python/scripts/test_leak.py`. The remaining scripts in that directory 
(`run_emscripten_tests.py`, referenced from 
`ci/scripts/python_test_emscripten.sh`, and `update_stub_docstrings.py`) are 
untouched.
   
   ### Are these changes tested?
   
   No new tests. This is a deletion of files that nothing references; I grepped 
`ci/`, `dev/`, `python/setup.py`, `python/pyproject.toml` and `MANIFEST.in` for 
references and found none. The only remaining mention in the repository is a 
historical `CHANGELOG.md` entry for ARROW-1033, which is left as-is.
   
   ### Are there any user-facing changes?
   
   No.
   
   ### AI usage disclosure
   
   Claude Code was used to search the repository for remaining references to 
the two scripts and to draft this description. The change itself is a two-file 
deletion; I reviewed the reference search and the resulting diff.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to