Dynamic development versioning in the OpenAstronomy package template

I used the package template for my new package and chose the Dynamic Development Versioning option. I noticed after I did a second “pip install -e .” that the “_version.py” file in my package changed. I read that this is just a backup for non-development installations. It still feels odd to me. My question is, should I commit these changes to “_version.py” when they occur, or should I add this file to “.gitignore”?

Someone who wrote the package template should chime in.

For sunpy, where we have the same system, that file is in the gitignore as its dynamically created.

1 Like