Skip to content
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

Pyreverse output directory #4159

Closed
t4n1o opened this issue Feb 28, 2021 · 4 comments
Closed

Pyreverse output directory #4159

t4n1o opened this issue Feb 28, 2021 · 4 comments
Labels
Enhancement ✨ Improvement to a component Good first issue Friendly and approachable by new contributors Help wanted 🙏 Outside help would be appreciated, good for new contributors pyreverse Related to pyreverse component
Milestone

Comments

@t4n1o
Copy link

t4n1o commented Feb 28, 2021

Could pyreverse (included with pylint) please have an option to choose an output directory?

I wrote a script that auto-generates UML diagrams for each .py file in my package, but then I have to copy them one by one with shutil.move(), because you don't have an option to specify the output path in pyreverse. (Only the output format).

Also I'm not the only one who needs this feature:
https://stackoverflow.com/questions/48689311/pyreverse-how-to-set-output-directory-for-generated-diagrams

@t4n1o
Copy link
Author

t4n1o commented Feb 28, 2021

Example use case:
https://gist.github.com/t4n1o/87a8949589e1aefd6542f1887fd654d3

It would be easier if we could specify the output path and didn't have to copy every single file into the documentation folder.

@Pierre-Sassoulas Pierre-Sassoulas added Good first issue Friendly and approachable by new contributors Enhancement ✨ Improvement to a component pyreverse Related to pyreverse component labels Feb 28, 2021
@Pierre-Sassoulas
Copy link
Member

Make sense, thank for opening the issue.

@Pierre-Sassoulas Pierre-Sassoulas added the Help wanted 🙏 Outside help would be appreciated, good for new contributors label Mar 2, 2021
mbyrnepr2 added a commit to mbyrnepr2/pylint that referenced this issue Mar 6, 2021
mbyrnepr2 added a commit to mbyrnepr2/pylint that referenced this issue Mar 6, 2021
mbyrnepr2 added a commit to mbyrnepr2/pylint that referenced this issue Mar 7, 2021
- Use the formatting of `black` pre-commit hook

Issue: pylint-dev#4159
Pierre-Sassoulas pushed a commit that referenced this issue Mar 7, 2021
- Use the formatting of `black` pre-commit hook

Issue: #4159
@matusvalo
Copy link
Collaborator

@Pierre-Sassoulas shouldn't be closed this MR?

@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.7.3 milestone Mar 7, 2021
@Pierre-Sassoulas
Copy link
Member

Good catch, I thought it was done automatically during merge.

Pierre-Sassoulas pushed a commit that referenced this issue Mar 28, 2021
- Use the formatting of `black` pre-commit hook

Issue: #4159
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement ✨ Improvement to a component Good first issue Friendly and approachable by new contributors Help wanted 🙏 Outside help would be appreciated, good for new contributors pyreverse Related to pyreverse component
Projects
None yet
Development

No branches or pull requests

3 participants