pyrepl should provide full traceback if possible to help debug possible buggy failures.

Bug report

Bug description:

Currently pyrepl has the following bug that is hard to debug:

config.site_import is value: '0'
config.user_site_directory is value: '0'
config.site_import is value: '0'
config.user_site_directory is value: '0'
Python 3.14.0a2+ (heads/main-dirty:49f15d8667e, Nov 29 2024, 21:28:03) [MSC v.1943 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
C:\Users\user\AppData\Roaming\Python\Python314\site-packages\easy-install.pth
warning: can't use pyrepl: 'NoneType' object does not support the context manager protocol (missed __exit__ method)
>>> 

This bug then results in site.py getting imported anyways despite my setting config.site_import AND config.user_site_directory in my own version of Py_Initialize in my C program that embeds the interpreter on Windows (exe). This results in the incorrect appending of the user site-packages folder at the end of sys.path that I did NOT OPT into at all. I did NOT want the interpreter to go about trying to open any pth file for which my own OpenCodeHook successfully captured and printed to my console to let me know that site.py was imported when it should not have been imported at all.

As such if tracebacks were printed whenever it would print the warning that pyrepl cannot be used it would help all possible situations where pyrepl cannot be used and give the user more information into fixing the root problem itself (even if it means pull requesting this repository with a fix for pyrepl itself).

Long story short EXTRA information is better than NOT ENOUGH information to debug and fix problems with pyrepl on embedded interpreters. Likewise site.py and the user site packages folder should be optional and not a hard requirement to using pyrepl either. Basically any and all places in this repository that imports site.py without checking if both config.site_import and config.user_site_directory should be made to check them first before attempting to import it, even if pyrepl cannot be used.

CPython versions tested on:

3.14, CPython main branch

Operating systems tested on:

Windows

Commencez par retracer l’endroit où pyrepl émet l’avertissement indiquant qu’il ne peut pas être utilisé et l’endroit où site.py est importé pendant l’initialisation de l’interpréteur. Vérifiez comment config.site_import et config.user_site_directory sont gérés, puis identifiez les tests couvrant les interpréteurs intégrés ou les échecs de pyrepl. Le travail est terminé lorsque l’avertissement inclut un traceback complet et que la configuration indiquée est respectée avant l’importation de site.py.