Source tarball for Python 3 version 4.9.2 is missing test directory
- Dominant language
- Java
- Stars
- 19k
- Forks
- 3.5k
- PR merge metrics
- No merged PRs in 30d
Description
I just wanted to update `antlr4-python3-runtime` in openSUSE to 4.9.2 and I noticed the tarball no longer contains the `test` directory. Hence, it's not possible to run the testsuite at the moment when building an RPM package.
```
$ wget https://files.pythonhosted.org/packages/source/a/antlr4-python3-runtime/antlr4-python3-runtime-4.9.1.tar.gz
$ wget https://files.pythonhosted.org/packages/source/a/antlr4-python3-runtime/antlr4-python3-runtime-4.9.2.tar.gz
```
and
```
$ tar tf antlr4-python3-runtime-4.9.1.tar.gz |grep test
antlr4-python3-runtime-4.9.1/test/
antlr4-python3-runtime-4.9.1/test/TestFileStream.py
antlr4-python3-runtime-4.9.1/test/TestInputStream.py
antlr4-python3-runtime-4.9.1/test/TestIntervalSet.py
antlr4-python3-runtime-4.9.1/test/TestRecognizer.py
antlr4-python3-runtime-4.9.1/test/TestTokenStreamRewriter.py
antlr4-python3-runtime-4.9.1/test/__init__.py
antlr4-python3-runtime-4.9.1/test/c.c
antlr4-python3-runtime-4.9.1/test/ctest.py
antlr4-python3-runtime-4.9.1/test/expr/
antlr4-python3-runtime-4.9.1/test/expr/ExprLexer.py
antlr4-python3-runtime-4.9.1/test/expr/ExprParser.py
antlr4-python3-runtime-4.9.1/test/mocks/
antlr4-python3-runtime-4.9.1/test/mocks/TestLexer.py
antlr4-python3-runtime-4.9.1/test/mocks/__init__.py
antlr4-python3-runtime-4.9.1/test/parser/
antlr4-python3-runtime-4.9.1/test/parser/__init__.py
antlr4-python3-runtime-4.9.1/test/parser/clexer.py
antlr4-python3-runtime-4.9.1/test/parser/cparser.py
antlr4-python3-runtime-4.9.1/test/run.py
antlr4-python3-runtime-4.9.1/test/xpathtest.py
$ tar tf antlr4-python3-runtime-4.9.2.tar.gz |grep test
$
```
Contributor guide
Research direction
Compare the 4.9.1 and 4.9.2 source tarballs, focusing on the missing test directory and its contents. Trace the release or source-package process that assembles antlr4-python3-runtime-4.9.2.tar.gz; done means the published tarball includes the test directory so downstream RPM builds can run the testsuite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100