DenverCoder1 / DenverCoder1/table2ascii
Broken/lacking metadata in latest versions (1.1.0 and 1.1.1)
- Dominant language
- Python
- Stars
- 77
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Encountering following issues with latest versions (1.1.0 and 1.1.1) of table2ascii:
```
WARNING: Generating metadata for package table2ascii produced metadata for project name unknown. Fix your #egg=table2ascii fragments.
has inconsistent name: filename has 'table2ascii', but metadata has 'unknown'
```
Presumably caused by the lack of the name and version parameters in the setup.py, considering those are there in the previous working version 1.0.4. I have also manually fixed this exact issue with some other packages in the past by editing that information into the setup.py and installing via that updated local package, so all things considered seems like a likely (and easy) fix.
Worth a note that all worked fine on my local machine for whatever reason; the issue presented itself only when I deployed it to my remote pipeline, but that's probably just to do with differing environments (particularly pip, because the new stricter pip versions are likely the cause of this).
It would be sweet to have a fix for this in any case, because while there are great many workarounds you can do manually, those defeat the point of being able to cleanly automate pip environment via requirements.txt and some scripting.
Contributor guide
Research direction
Start by comparing the current setup.py with the working 1.0.4 version, focusing on the package metadata named in the report. Reproduce installation through the remote pipeline or a current pip environment, then confirm that the package installs from requirements.txt without the unknown-project metadata warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100