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
This was mentioned in #856, but setuptools_scm has an option to write the version information to a python module version.py. It was decided in my PR that we should use the pkg_resources method though which dynamically loads the installed package data to get the version. It has come to my attention since this PR that this is actually a terrible idea. What happens is that for large python environments, pkg_resources has to search through all package metadata to get the version information. I'm not sure why it is this way, but it has been reported for other projects I work on (vispy) where it ends up taking seconds just to import the package because of the time it takes to get the version number.
Related: #678 and #856
This was mentioned in #856, but setuptools_scm has an option to write the version information to a python module version.py. It was decided in my PR that we should use the
pkg_resources
method though which dynamically loads the installed package data to get the version. It has come to my attention since this PR that this is actually a terrible idea. What happens is that for large python environments,pkg_resources
has to search through all package metadata to get the version information. I'm not sure why it is this way, but it has been reported for other projects I work on (vispy) where it ends up taking seconds just to import the package because of the time it takes to get the version number.Thoughts @mraspaud?
The text was updated successfully, but these errors were encountered: