Can anyone explain this early problem?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 603
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Love the idea. Needs a bit more documentation perhaps?
I got as far as
$ ./gradlew build
and then this failed after a bit:
Task :installProject FAILED
Install PyLookup2019-09 ............................................. [STARTING]
Obtaining file:///home/mike/software%20projects/eclipse-workspace/PyLookup2019-09
No files/directories in /home/mike/software projects/eclipse-workspace/PyLookup2019-09 (from PKG-INFO)
"No files/directories"... what can that mean? There was a very basic starter file (__init__.py). Also can you explain what you mean by a "standard python project"? Does setup.cfg have to contain something specific perhaps?
Also, what might it mean by "(from PKG-INFO)"?
Thanks
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 reproducing the failure with ./gradlew build, then inspect setup.cfg, the starter init.py, and the generated PKG-INFO reference. Document what a standard Python project must contain and explain the “No files/directories” and “from PKG-INFO” messages; done means a new user can understand and address this setup failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100