Flagged malware on .odin test files
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 885
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
It looks like the test fIles are packaged together with the package (at least on miniforge), which is triggering our malware scanner on the .odin test files. Is there an option to exclude the test folders for building and distributing the package?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting Pygments' package build and distribution configuration, then reproduce the issue with a package built for miniforge. Identify how the .odin test files are included and adjust the packaging scope so test folders are excluded from distributions while the test suite remains available in the source tree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100