On Tue, Feb 08, 2022 at 12:44:46PM +0000, Steve Dower wrote:
Agreed. CPython should be specific, Python should be as vague as possible. Otherwise, we would prevent _by specification_ using Python as a scripting language for things where floats may not even be relevant.
I don't think that being *vague* is desirable. Being *permissive* on the other hand may be.
It's not even about hardware capabilities (unless you believe Python is only for running in a terminal, in which case we'll just have to disagree). It could be about an app using short Python snippets as a customisation language for some domain-specific task rather than inventing a brand new language for it.
I'm sorry, I don't understand what point you are trying to make here. Regarding "running in a terminal", I don't see how the environment (terminal, GUI, something else) is relevent. Regarding your second point, about domain-specific tasks, I don't understand. If your domain-specific task doesn't need to use floats, just don't use floats. There's surely no need to invent a whole new language for some task because your app only needs to do string processing, say. Have I misunderstood what you are trying to say? -- Steve