Marc-Andre Lemburg <m...@egenix.com> added the comment: Mark Dickinson wrote: > > Mark Dickinson <dicki...@gmail.com> added the comment: > >> There should be an environment variable to make the symbol settable. > > That could work; it's a bit late to do this in 3.2, though. How about the > following transition strategy for the complex output. > > Python 3.3: Introduce PYTHONIMAGINARYSYMBOL environment variable (and > possibly also a related command-line option to the interpreter?). > > Python 3.4: Show a warning on startup if this environment variable isn't used. > > Python 3.5: Make the environment variable mandatory. > > Python 3.6: Make the environment variable optional again, but this time with > the default output being 'i' rather than 'j'. > > Python 3.7: Deprecate use of PYTHONIMAGINARYSYMBOL. (Warning on startup if > it's set.) > > Python 3.8: Error on startup if PYTHONIMAGINARYSYMBOL is set. > > Python 3.9: Go back to ignoring PYTHONIMAGINARYSYMBOL. > > I'm sure we could find a compatible transition strategy for the complex > *inputs*: (3.3: accept both 'i' and 'j'; 3.6: warn about 'j' usage; 3.8 > remove acceptance of 'j' on input).
Hmm, what calendar are you using ? April 1st is still a few months away on the Gregorian one and even the Julian calendar isn't that far off yet :-) Why not simply support both for number constructors (and stick with 'j' for the language spec) ? ---------- nosy: +lemburg _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10562> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
