Message 123117 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	Retro
Recipients	Retro, belopolsky, brian.curtin, georg.brandl, mark.dickinson, michael.foord, pitrou, rhettinger
Date	2010-12-02.21:13:18
SpamBayes Score	0.004191343
Marked as misclassified	No
Message-id	<AANLkTik3VY8cQK4ibmVCqBK26-ZjU5ac2yK+Wo2SsVym@mail.gmail.com>
In-reply-to	<1291324002.61.0.225184093039.issue10562@psf.upfronthosting.co.za>

Content
"In electrical engineering<http://en.wikipedia.org/wiki/Electrical_engineering> and related fields, the imaginary unit is often denoted by j to avoid confusion with electrical current<http://en.wikipedia.org/wiki/Current_(electricity)> as a function of time, traditionally denoted by i(t) or just i." -Wikipedia Does Python have to deal with electrical current as a function of time to associate j with the imaginary unit and not i?

"In electrical engineering<http://en.wikipedia.org/wiki/Electrical_engineering>
and
related fields, the imaginary unit is often denoted by *j* to avoid
confusion with electrical
current<http://en.wikipedia.org/wiki/Current_(electricity)> as
a function of time, traditionally denoted by *i*(*t*) or just *i*."
-Wikipedia

Does Python have to deal with electrical current as a function of time to
associate j with the imaginary unit and not i?

Files
File name	Uploaded
unnamed	Retro, 2010-12-02.21:13:18

History
Date	User	Action	Args
2010-12-02 21:13:22	Retro	set	recipients: + Retro, georg.brandl, rhettinger, mark.dickinson, belopolsky, pitrou, michael.foord, brian.curtin
2010-12-02 21:13:18	Retro	link	issue10562 messages
2010-12-02 21:13:18	Retro	create