Include pip packages in package_versions.txt

[davemfish]

package_versions.txt is meant to be a list of all packages & versions included in the binary builds. It's a convenient way to see which version of package was bundled with the workbench, after the workbench is installed.

We were building it with micromamba list, but that excludes pip installed packages (pygeoprocessing, taskgraph, among others). I did not find any way for micromamba to include these, so I appended the pip list to the micromamba list. There is some overlap, which I don't understand, but I think that's okay given the purpose of this file.

Fixes #1527

Checklist

• Updated HISTORY.rst and link to any relevant issue (if these changes are user-facing)
• Updated the user's guide (if needed)
• Tested the Workbench UI (if relevant)

[emlys]

@davemfish this makes sense, I just had a couple of questions. Is package_versions.txt a standard thing? I assumed it was but I couldn't find anything about it online.

And, if the intent is to list all the package versions used in the binary builds, would it make sense to get that info from Pyinstaller somehow? Since Pyinstaller should know what is actually included in the package.

[davemfish]

@davemfish this makes sense, I just had a couple of questions. Is package_versions.txt a standard thing? I assumed it was but I couldn't find anything about it online.

And, if the intent is to list all the package versions used in the binary builds, would it make sense to get that info from Pyinstaller somehow? Since Pyinstaller should know what is actually included in the package.

@emlys the Pyinstaller idea is a good one, I hadn't thought of that. As far as I know package_versions.txt is just something we do for our own info, but I don't know the origin of it.

[davemfish]

@davemfish this makes sense, I just had a couple of questions. Is package_versions.txt a standard thing? I assumed it was but I couldn't find anything about it online.
And, if the intent is to list all the package versions used in the binary builds, would it make sense to get that info from Pyinstaller somehow? Since Pyinstaller should know what is actually included in the package.

@emlys the Pyinstaller idea is a good one, I hadn't thought of that. As far as I know package_versions.txt is just something we do for our own info, but I don't know the origin of it.

It looks like we would have to add some custom code to our pyinstaller script to do this. I kinda feel like it's not worth it given how little we actually refer to package_versions.txt.

[emlys]

Ok, thanks for looking into it!