-
Notifications
You must be signed in to change notification settings - Fork 32
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 separate dropq_version when it's identical to taxcalc_version? #639
Comments
That seems like a wise suggestion to me. |
@martinholmer I agree. Since I've been working on #619, I've noticed that the webapp code be cleaned up significantly. I think this issue is just one example. There are a lot of unused imports and what appears to be overly complicated code. |
@martinholmer can you point out some code where you are seeing this? |
@brittainhard asked in issue #639:
This obsolete usage is littered all over the PolicBrain repository:
There is no difference between Can we remove this obsolete code from the PolicyBrain repository? |
This issue has been labeled "Priority" for almost a year, so I guess it is either fixed or it really isn't a priority. |
The code for TaxBrain is pretty complicated. Some of that complexity is required because TaxBrain is a complex web application. But some of it seems obsolete, and therefore, makes the code unnecessarily complex. An example of this, is the
dropq_version
variable, which (now that dropq is part of the taxcalc package) is identical totaxcalc_version
. So, why not simplify the code by removing all references todropq_version
and, where necessary, replace it withtaxcalc_verison
?@brittainhard @MattHJensen @hdoupe @GoFroggyRun
The text was updated successfully, but these errors were encountered: