Skip to content

Conversation

@scotwk
Copy link

@scotwkscotwk commented Feb 27, 2018

Fixes#86 (@karthich)

** Breaks backwards compatibility! **

I changed the --use-requirements flag to --requirements <PATH> to allow a path to be specified.

If you are concerned about backwards compatibility the existing flag and behavior can be preserved. I think it might be confusing to have two flags that do roughly the same thing, but I'm not sure how many people are using the current behavior.

** Breaks backwards compatability! **
@scotwkscotwk changed the title Change --use-requirements to --requirements <PATH>Change --use-requirements to --requirements <PATH> (#86)Mar 6, 2018
@scotwk
Copy link
Author

@nficano - I'm deleting my local environments that I developed this in, so if it needs any changes I'd like to work with you on them while I still have that environment available. Note that it breaks backwards compatibility. (The previous behavior is still available, but the flag name changed)

Please let me know if you have any concerns about the change. Thanks.

@nficanonficano merged commit 10ef0aa into nficano:masterMar 26, 2018
@scotwkscotwk deleted the feature-specify-requirements-file branch March 26, 2018 15:59
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@scotwk@nficano