Closed martinholmer closed 5 years ago
@martinholmer, I just have a side comment on #49. I've found it helpful to have the version hard coded in the init file. I then update it on each release. This makes it easy to verify that your local version is up to date. This is pertinent when you are working on a couple packages that depend on each other and you are doing some development work on them simultaneously or doing some preliminary testing of one package with the other package. The latter case sounds similar to the problem that you are having here. The downside of hard coding the version is that you have to remember to bump the version on each release.
@hdoupe said:
I just have a side comment on #49. I've found it helpful to have the version hard coded in the init file. I then update it on each release.
Thanks for the tip! Do you mean by "the init file" the envioronment.yml
file or some other file?
Sure thing. I mean __init__.py
. For example: https://github.com/PSLmodels/ParamTools/blob/master/paramtools/__init__.py#L34
@hdoupe said:
I mean init.py OK. I understand what you're saying. Thanks for the thought.
Now the
environment.yml
file has these contents:After a period of time (and everybody is using taxcalc 1.0+), the last line above should be changed to:
This change will make it easier to create for testing a local
behresp
package that uses a localtaxcalc
package, which is version 0.0.0.