Hi, I wrote "python -m test.pythoninfo", but I wrote it to debug buildbot failures. It produces a large output. Only very few info are useful, but previously it was hard to get these info. I wouldn't suggest to start to request it. Or if you want it, it should be attached as a file to not pollute the issue.
Note: On Fedora at least, you have to install python3-test package to get test.pythoninfo. Victor Le jeu. 21 févr. 2019 à 19:11, Barry Warsaw <ba...@python.org> a écrit : > > On Feb 21, 2019, at 06:53, Stephane Wirtel <steph...@wirtel.be> wrote: > > > > What do you think if we suggest a "template" for the new bugs? > > > > For example: > > * Python version (exact version) > > * Operating System * on Linux -> Distribution (python can have some > > patches) > > * Add a script for the reproduction of the bug > > * Eventually, try with the docker images (on i386,x86_64, ...) > > * etc... > > > > We can lost a lot of time just trying to find the right information for > > the reproduction of the issue. > > Getting reproducible cases is usually the hardest part of any bug fix. :) > > If there is information about the platform, version of Python, build flags > etc. that we want to capture in bug reports, there should be a `python -m > bugreport` or some such that we can ask people to run and attach or paste > into their issue. Maybe even cooler would be something that opens a new > GitHub issue with that information pre-populated. > > -Barry > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/vstinner%40redhat.com -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
