awslabs / awslabs/amazon-dynamodb-tools
Limit what can end up in python_modules.zip
- Dominant language
- Python
- Stars
- 181
- Forks
- 50
- Avg merge
- 4h 11m
- Merged PRs (30d)
- 36
Description
If a developer has cruft in their codebase it can end up in python_modules.zip.
```
32 python_modules/fill/__pycache__/
33 python_modules/fill/__pycache__/nosk.cpython-314.pyc
34 python_modules/fill/__pycache__/default.cpython-314.pyc
35 python_modules/fill/__pycache__/__init__.cpython-314.pyc
36 python_modules/fill/__pycache__/multi_entity_relationship.cpython-314.pyc
37 python_modules/load_export/.DS_Store
76 python_modules/load_export/data/jzhunter/.DS_Store
77 python_modules/load_export/data/jzhunter/01777434077719-58efe0e3/
78 python_modules/load_export/data/jzhunter/01777434077719-58efe0e3/manifest-summary.md5
79 python_modules/load_export/data/jzhunter/01777434077719-58efe0e3/manifest-files.md5
```
Perhaps we should ignore __pycache__ and .DS_Store and anything that's common cruft. Like a "zipignore"?
Contributor guide
Research direction
Start by locating the code that creates python_modules.zip and reproduce the archive with the listed __pycache__, .DS_Store, and generated files. Determine how exclusions should be configured, then verify that common cruft is omitted while needed project files remain included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100