You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Pandas developers seem to be planning to quit supporting Python 2.7 at the end of 2018 as described here. In the coming months the Tax-Calculator developers would like to transition Tax-Calculator to be a Python 3.6+ project.
Will this project find it acceptable to have access to only Python 3.6 taxcalc packages?
The text was updated successfully, but these errors were encountered:
Will this project find it acceptable to have access to only Python 3.6 taxcalc packages?
Yes. I'm also going to work on updating this project to work with Python 3.6 in the coming months. The only major obstacle is the linear programming model used in stage 2 extrapolation for the PUF. The CyLP package we currently use is only compatible with Python 2.7 and it is unlikely that will change anytime soon. My search for a replacement model has taken a backseat to my work on the UBI project, but I'll pick it back up when that is complete.
Will this project find it acceptable to have access to only Python 3.6 taxcalc packages?
Yes. I'm also going to work on updating this project to work with Python 3.6 in the coming months. The only major obstacle is the linear programming model used in stage 2 extrapolation for the PUF. The CyLP package we currently use is only compatible with Python 2.7 and it is unlikely that will change anytime soon. My search for a replacement model has taken a backseat to my work on the UBI project, but I'll pick it back up when that is complete.
The Pandas developers seem to be planning to quit supporting Python 2.7 at the end of 2018 as described here. In the coming months the Tax-Calculator developers would like to transition Tax-Calculator to be a Python 3.6+ project.
Will this project find it acceptable to have access to only Python 3.6 taxcalc packages?
The text was updated successfully, but these errors were encountered: