-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Question about B-Tax release 0.1.7 #168
Comments
Agreed - B-Tax should be pinned to Tax-Calculator with a |
@PeterDSteinberg said:
I don't think doing the pinning in the policybrain-builder script is the right way to proceed. The reason is that in my view that the policybrain-builder script needs major changes in its architecture given the release process envisioned by @MattHJensen. The script should be changed so that it operates on only one repo at a time and never changes the repo's |
I am in agreement with @martinholmer. I think the contributors to this project should adjust the pins via PRs to this project. This places the ultimate responsibility for managing dependencies, including testing, on the core maintainer of this project rather than the maintainers of policybrain-builder. |
The discussion in B-Tax issue #168 seems to have reached the conclusion that the B-Tax conda.recipe/meta.yaml` specification of the taxcalc dependency should be done manually by the B-Tax developers as their tests show B-Tax works with a new version of the taxcalc package. So, for example, after testing B-Tax with taxcalc 0.9.1 and finding all is good, the B-Tax developers would make the following changes on two lines in
and the new lines would, in this example, would be as follows:
Given that this discussion seems to have run its course, this issue should be closed. |
The comment on B-Tax release 0.1.7 says
If that is the case, then why not pin to taxcalc 0.9.0 until you know B-Tax works with a more recent taxcalc release?
You could do this by changing in both places the
conda.recipe/meta.yaml
file to include:instead of the current
@jdebacker @rickecon @MattHJensen @PeterDSteinberg @jbcrail
The text was updated successfully, but these errors were encountered: