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
Is your feature request related to a problem? Please describe.
Currently, rope/contrib/autoimport/sqlite.py creates an sqlite database at autoimport.db that caches the result of scanning site-packages for names that are useful during autoimport.
Currently, when you upgrade rope version and the database schema has changed, it doesn't have any way to know that it should purge the database and do a re-scan.
Describe the solution you'd like
version_hash should be calculated from rope.VERSION, a hash of rope/contrib/autoimport/models.py file, and a hash of user preferences. (Implement version hash #631)
create a new metadata table, this table should contain a single column named version_hash
if the version_hash changes, then the database should be considered outdated and autoimport should re-scan the environment
Is your feature request related to a problem? Please describe.
Currently, rope/contrib/autoimport/sqlite.py creates an sqlite database at autoimport.db that caches the result of scanning
site-packages
for names that are useful during autoimport.Currently, when you upgrade rope version and the database schema has changed, it doesn't have any way to know that it should purge the database and do a re-scan.
Describe the solution you'd like
version_hash
should be calculated fromrope.VERSION
, a hash ofrope/contrib/autoimport/models.py
file, and a hash of user preferences. (Implement version hash #631)metadata
table, this table should contain a single column namedversion_hash
version_hash
changes, then the database should be considered outdated and autoimport should re-scan the environmentAdditional context
The text was updated successfully, but these errors were encountered: