On Fri, 24 Jul 2020 at 16:43, Gábor Bernát <jokerjoke...@gmail.com> wrote: > > While I agree the implementation on how to represent in limited space the > object should be the responsibility of the project that provides objects of > long size, I think it's a language-behaviour material what type of solution > we want to propose/recommend.
I still don't see why. Unless you consider "use something application specific" as a language-behaviour type of recommendation. I'm still seeing nothing here that suggests that "modify something provided by the language or stdlib" is the best answer. Maybe the point of the original question is that you're looking for a function that can be used by *any* debugger, rather than a solution for one specific debugger. In that case, the people writing debuggers should agree on a standard protocol (maybe something like debugger_repr(object)) that they will use. But it's still not a language-level question, any more than (for example) the definition of the numpy ufunc mechanism is a language matter... I'm clearly missing the point of your question here. Can you clarify? Paul _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/IWQGP64PUKOUHFYR2NQUZQQS7ZXAIX7Z/ Code of Conduct: http://python.org/psf/codeofconduct/
