Comment #12 on issue 3439 by asmeu...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Well if you want, you can raise the issue on the list, but I doubt many
will disagree with me.
Definitely importing matplotlib is a problem, but
Comment #11 on issue 3439 by jenshnie...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
The issue that I was originally trying to raise is that:
Sorry, I remembered something that is clearly not right. You in general do
a better jo
Comment #10 on issue 3439 by asmeu...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Ok perhaps your are right. Perhaps it is more an issue with various stack
overflow questions ect.
Yes, we care very much about this, so that if
Comment #9 on issue 3439 by jenshnie...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Ok perhaps your are right. Perhaps it is more an issue with various stack
overflow questions ect. I just looked into the notebooks that you have
Comment #8 on issue 3439 by asmeu...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Can you be more specific about what examples you are talking about? All of
the docstring examples have explicit imports at the top, and the same w
Comment #7 on issue 3439 by jenshnie...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
I perfectly well know what namespaces are thanks. The problem is that most
of your examples are written with the default assumption that isympy
Comment #6 on issue 3439 by asmeu...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
I think perhaps your real issue here is "pylab and isympy don't mix",
meaning that they both import the same names. The fix for the user (and to
Comment #5 on issue 3439 by asmeu...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Scripts should *never* use implicit imports, or pylab for that matter.
Pylab and isympy are intended for interactive use only.
Python has a mech
Comment #4 on issue 3439 by jenshnie...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Furthermore the most natural way of activating an interactive session in
Ipython is to use pylab. And there you have the name clash almost
una
Comment #3 on issue 3439 by jenshnie...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
I'm sorry that you chose to pretend that there is not an issue. I think
that the importing into global name spaces is one of the biggest issues
Updates:
Status: WontFix
Comment #2 on issue 3439 by asmeu...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Keeping our names disjoint from numpy's is not a design decision of SymPy.
We have a hard enough time not collidin
Comment #1 on issue 3439 by jenshnie...@gmail.com: Don't pollute global
namaespace with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
See for instance https://github.com/ipython/ipython/issues/2488
--
You received this message because you are subscribed to the Google Groups
"sy
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3439 by jenshnie...@gmail.com: Don't pollute global namaespace
with plot.
http://code.google.com/p/sympy/issues/detail?id=3439
Running from sympy import * as is the default in isympy
results in sympys plot function being im
13 matches
Mail list logo
