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

Why PyCI does not meet my needs #30

Open
iliapolo opened this issue Jun 11, 2018 · 1 comment
Open

Why PyCI does not meet my needs #30

iliapolo opened this issue Jun 11, 2018 · 1 comment

Comments

@iliapolo
Copy link
Owner

This issue is intended for people who saw PyCI and decided not to use it. I highly appreciate every feedback, especially from those who decided against the tool :)

Just comment on this issue with a short explanation of your decision.

Much appreciated

@OriHoch
Copy link

OriHoch commented Jun 11, 2018

This kind of tool might be useful for me but the main problem at the moment is that it's too monolithic, basically, you require to choose to use your tool or not (it's also represented like that in the README)

I would much prefer to see a bunch of different tools / script which perform the different parts in isolation and with minimal dependencies

It boils down to composition vs. inheritance, basically, your tool requires me to "inherit" and extend it and work in the context of your tool, while I prefer composition model where I can "compose" and mix the different parts myself - replacing some parts / modifying the flow between the components

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants