Change Details

**Current behavior:** When using pywikibot in an import statement the check for user-config.py is immediately done and throw a runtime error even if pywikibot is never called. It is explained that an Environment variable needs to be set to avoid this behavior. ``` Set PYWIKIBOT_NO_USER_CONFIG=1 to disable loading user-config.py ``` **Expected behavior:** * It should be possible to import pywikibot even it no user-config is available. * It should be possible to use pywikibot and disable the user-config.py check via API (not via Environment variable!) ** Reasoning** When deploying a library like https://github.com/WolfgangFahl/py-3rdparty-mediawiki and make it available for the general public that has a choice of using either mwclient or pywikibot as the API channel to MediaWiki it does not make sens to throw an error by pywikibot when people choose mwclient. In fact this makes offering pywikibot as a library impossible in the long run. Please fix this issue so that py-3rdparty-mediawiki will be able to offer a pywikibot. With the current state of affairs I'd have to remove the pywikibot support for the inconvenience it introduces for users.

**Current behavior:** When using pywikibot in an import statement the check for user-config.py is immediately done and throw a runtime error even if pywikibot is never called. It is explained that an Environment variable needs to be set to avoid this behavior. ``` Set PYWIKIBOT_NO_USER_CONFIG=1 to disable loading user-config.py ``` **Expected behavior:** * It should be possible to import pywikibot even it no user-config is available. * It should be possible to use pywikibot and disable the user-config.py check via API (not via Environment variable!) ** Reasoning** When deploying a library like https://github.com/WolfgangFahl/py-3rdparty-mediawiki and make it available for the general public that has a choice of using either mwclient or pywikibot as the API channel to MediaWiki it does not make sens to throw an error by pywikibot when people choose mwclient. In fact this makes offering pywikibot as a library impossible in the long run. Please fix this issue so that py-3rdparty-mediawiki will be able to offer a pywikibot. With the current state of affairs I'd have to remove the pywikibot support for the inconvenience it introduces for users.

**Current behavior:** When using pywikibot in an import statement the check for user-config.py is immediately done and throw a runtime error even if pywikibot is never called. It is explained that an Environment variable needs to be set to avoid this behavior. ``` Set PYWIKIBOT_NO_USER_CONFIG=1 to disable loading user-config.py ``` **Expected behavior:** * It should be possible to import pywikibot even it no user-config is available. * It should be possible to use pywikibot and disable the user-config.py check via API (not via Environment variable!) ** Reasoning** When deploying a library like https://github.com/WolfgangFahl/py-3rdparty-mediawiki and make it available for the general public that has a choice of using either mwclient or pywikibot as the API channel to MediaWiki it does not make sens to throw an error by pywikibot when people choose mwclient. In fact this makes offering pywikibot as a library impossible in the long run. Please fix this issue so that py-3rdparty-mediawiki will be able to offer a pywikibot. With the current state of affairs I'd have to remove the pywikibot support for the inconvenience it introduces for users.