Kind Regards, Abdur-Rahmaan Janhangeer compileralchemy.com <https://www.compileralchemy.com> | github <https://github.com/Abdur-rahmaanJ/> Mauritius On Thu, Apr 2, 2020 at 8:15 PM Andrew Barnert <abarnert@yahoo.com> wrote:
Why should modules break all of that, and be different from strings, tuples, functions, classes, etc.?
python-ideas is for ideas without worrying about implementations unless it's about some glaring breaking changes
The str, which you get from print(package), might be a different story. If there’s a representation of a module that’s more useful to end users than the repr, even if it’s not as good for debugging, the str should use that representation. But is there? What would the message be? How would the module specify it? And how it would be useful for the end user to see that message? ... I may be misinterpreting something about the goals of your proposal. If so, I apologize—but it would really help if you give a real example: some known module, what message you think it should include in its repr, where you plan to print out that repr, how you’d like to specify it within the module source, etc.
Well as for example from known module, the proposal is all about introducing the __repr__ option in modules. If i understood well it does not seem to exist. As for purpose, well a friendlier representation of a package.