issue parsing a Python requirements file
Issue #140
resolved
receiving "ERROR: project file could not be parsed. Maybe the file is empty? Or not valid?" for a valid requirements file
Comments (6)
-
reporter
-
@ismith How did you parse the files? Did you upload them? I guess you have to rename them to "requirements.txt" or "requirements_SOMETHING.txt". Currently 11 package managers are supported. Through the filename VersionEye decides which parser to pick for your file. I guess that's the problem.
-
reporter
yes .. I uploaded them .. its standard practice for us to have a "requirements" directory with different files for the different environments
would be nice to be able to choose the parser manually
-
reporter
maybe another approach could be to look for ".txt" instead or in addition?
-
Yes. That would be a solution, because there is no other project file ending with .txt.
-
- changed status to resolved
OK. It's changed now. Every file which is ending with .txt will be assigned to the requirement.txt parser.
- Log in to comment
