View Single Post
Old 05-29-2020, 09:04 AM   #6
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,674
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Understood and agreed. Do you know of a way to officially make any import of compatibility_utils and unipath give a Deprecation warning of some sort so new plugins do not use them during the interim?
I might be able to rig up an import hook to add a deprecation warning, but using sys.path_hooks and sys.meta_path to intercept/substitute/augment/deny module/package imports got overly complicated in Python 3 in my opinion (not to mention that there's several function deprecations between python 3.4 and 3.6 ). It might be easier (and certainly less complicated) to "patch" the builtins __import__ function in the plugin framework to add a warning whenever importing anything from compatibility_utils. I can look into it if you like.

Last edited by DiapDealer; 05-29-2020 at 09:20 AM.
DiapDealer is online now   Reply With Quote