-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Printing Report from requirements.txt
#77
Comments
I like the idea behind it a lot. However, I don't think we should reinvent the wheel and parse the |
Yep, I totally agree with the spirit not re-inventing the wheel! However I'm unaware of any easy way to do that with |
Here is a list of potential solutions: https://stackoverflow.com/a/67111193 -- Most seem not to work or are outdated. I think getting the dependencies right is a difficult task, and not one scooby should care. But then, your question is sort of a different one. You don't want to get necessary the dependencies right, you just want to print the packages which are listed in the requirements. I still think that is interesting. (For your own project, I would recommend the way specified in the readme: https://github.com/banesullivan/scooby#implementing-scooby-in-your-project). @banesullivan , @akaszynski , what do you think? |
I just had a brief look. So I am definitely not in favour of parsing a A requirements can, e.g., also have wheels. It can have other requirements files. I could foresee many issues to be opened because scooby fails to parse a particular requirements file... |
(It can also have the |
I really like the idea behind this and would support work towards it, but I am also concerned about all the different ways in which a dependency can be specified in a Another concern to list: the package name does not have to match the import name, e.g. This idea actually gave me another idea: what if we could generate the code for creating a report with the |
Hey there!
Had a potential feature to suggest:
I find myself often wanting to quickly make a
Report
based on the contents of a project'srequirements.txt
file. Maybe we could shorthand that by adding a new function toscooby
with a call signature likescooby.report.from_requirements(filename) -> scooby.Report
?The output of such a function would be to create a
scooby
Report with all the packages mentioned in arequirements.txt
file.Here's the minimal code I've been using for this, type-hinted for readability:
LMK if interested and I can PR it.
The text was updated successfully, but these errors were encountered: