Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 1977 by dlenski: symbols() gives unexpected behavior when passed
a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
It makes sense for symbols() to return a single Symbol object when passed a
single p
Updates:
Status: Accepted
Comment #1 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
I agree, make it always return a list. If you want exactly one symbol, use
Symbol(). Feel free to
Comment #2 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
var() should be fixed too:
In [18]: var('t')
Out[18]: t
In [19]: var(['t'])
Out[19]: t
In [20]: var(['t', 'x'])
Out[20]: (t, x)
In
Updates:
Status: Started
Comment #3 on issue 1977 by mattpap: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
In polys10 I cleaned up var() and symbols() a little bit, disallowing the
old syntax for symbols() an
Comment #4 on issue 1977 by smichr: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
These look like great changes! Does it have an option to inject the
variables into the locals like var?
--
You received this message
Comment #5 on issue 1977 by mattpap: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
var() is still there and has now the same syntax as symbols() has.
--
You received this message because you are subscribed to the Googl
Updates:
Cc: mattpap
Comment #6 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
Regarding the commit in polys10, what exactly is the reasoning of changing
all instances of var("a b") a
Comment #7 on issue 1977 by mattpap: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
When changing symbols('xyz') to symbols('x,y,z') I just uniformly changed
every occurrence of symbols() and var() to use comma syntax.
Updates:
Labels: NeedsReview Milestone-Release0.7.0
Comment #8 on issue 1977 by mattpap: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
(No comment was entered for this change.)
--
You received this message beca
Updates:
Labels: -NeedsReview NeedsBetterPatch
Comment #10 on issue 1977 by ronan.l...@gmail.com: symbols() gives
unexpected behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
+1 to comment 6.
I don't think it's a good idea to suddenly break
Comment #11 on issue 1977 by Vinzent.Steinberg: symbols() gives unexpected
behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
Well, actually it has been deprecated for a long time in the docstring,
there was only no DeprecationWarning.
--
You rece
Comment #12 on issue 1977 by ronan.l...@gmail.com: symbols() gives
unexpected behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
Considering that every isympy session in 0.6.7 starts with this:
x, y, z = symbols('xyz')
k, m, n = symbols('kmn', integ
Comment #13 on issue 1977 by Vinzent.Steinberg: symbols() gives unexpected
behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
It is trivial to fix those scripts though.
--
You received this message because you are subscribed to the Google Groups
"sy
Comment #14 on issue 1977 by ronan.l...@gmail.com: symbols() gives
unexpected behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
It's trivial for us, but annoying for most users.
--
You received this message because you are subscribed to the Google G
Comment #15 on issue 1977 by smi...@gmail.com: symbols() gives unexpected
behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
Let's not quibble about this...why not put an official deprecation warning
in sympy until 0.8; don't accept any patch that r
Updates:
Status: NeedsDecision
Comment #16 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
(No comment was entered for this change.)
--
You received this message because you are subscri
Comment #17 on issue 1977 by smi...@gmail.com: symbols() gives unexpected
behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
I propose the following 3 deprecation warnings:
>>> symbols('x y',each_char=True)
keyword "each_char" is deprecated;
Comment #18 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
Well, those might be OK, since they don't prevent us from using new
behavior (unless I am mistaken).
--
You received this message
Comment #19 on issue 1977 by smi...@gmail.com: symbols() gives unexpected
behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
The only glitch is that the totally new behavior (symbols('xyz') ==
Symbol('xyz')) can't be implemented. But hopefully we ca
Comment #20 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
Well, that is the thing. Is it worth it to deprecate that for this release
instead of just fixing the issue for once and for all.
Comment #21 on issue 1977 by smi...@gmail.com: symbols() gives unexpected
behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
I think Ronan's point is that we haven't had a proper deprecation. The
number of people using symbols('abc') to mean a, b, c
Updates:
Cc: ondrej.c...@gmail.com
Labels: -Priority-Medium Priority-Critical
Comment #22 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
OK, so we need to make a decision here.
Comment #23 on issue 1977 by smi...@gmail.com: symbols() gives unexpected
behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
So much changes(changed) without an attempt to keep backward
compatibility...I don't care if this is also one of those issues
Comment #24 on issue 1977 by ondrej.c...@gmail.com: symbols() gives
unexpected behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
I vote for no deprecation, breaks backwards compatibility.
--
You received this message because you are subscribed to th
Comment #25 on issue 1977 by ondrej.c...@gmail.com: symbols() gives
unexpected behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
To smichr I think we care about backward compatibility, but this issue
wasn't used a lot and was just confusing. I
Comment #26 on issue 1977 by ronan.l...@gmail.com: symbols() gives
unexpected behavior when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
It turns out that I don't actually care enough about this to patch it
myself before the release, so I'm OK with breaking
Updates:
Status: Fixed
Comment #27 on issue 1977 by asmeurer: symbols() gives unexpected behavior
when passed a list of length 1
http://code.google.com/p/sympy/issues/detail?id=1977
Excellent! :-)
There was nothing more to do here, right?
--
You received this message because you are
27 matches
Mail list logo
