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
As we continue writing more production Python code, particularly in the context of our dbt project, it's become clear that having a Python version of this package would be helpful for reducing duplication of code across our Python scripts. This would follow the same pattern set by assesspy and assessr, although we should colocate the R and Python versions of the ccao package in this repo so that they can share data files in data-raw.
We should refactor this repo to add a Python ccao package that shares data with the existing R package but is deployed separately to PyPI. Since there's a lot of code to be ported, we should start small with the highest-leverage parts of the package, get the package deployed to prod, and then migrate more features over incrementally.
As we continue writing more production Python code, particularly in the context of our dbt project, it's become clear that having a Python version of this package would be helpful for reducing duplication of code across our Python scripts. This would follow the same pattern set by assesspy and assessr, although we should colocate the R and Python versions of the
ccao
package in this repo so that they can share data files indata-raw
.We should refactor this repo to add a Python
ccao
package that shares data with the existing R package but is deployed separately to PyPI. Since there's a lot of code to be ported, we should start small with the highest-leverage parts of the package, get the package deployed to prod, and then migrate more features over incrementally.The scope of this issue includes:
python
vars_funs.R
to Pythondata-raw
so that it works with Python (see the issue template for context on how this pipeline works for R)Set up PyPI deploymentEDIT: This package does not get deployed to any package authoritiesOnce these steps are complete and deployed, we can open up a follow-up issue to copy the rest of the package functionality to Python.
The text was updated successfully, but these errors were encountered: