Updates:
Labels: -Milestone-Release0.7.2
Comment #35 on issue 1735 by vlada.pe...@gmail.com: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
I'm going to go ahead and drop the milestone from this. The discussion
stalled, and this shouldn't really block any
Comment #33 on issue 1735 by vlada.pe...@gmail.com: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
What is the status of this? It's marked for the next release milestone, but
I don't think there's any progress.
As I understand it, we are considering renaming
Comment #34 on issue 1735 by asmeu...@gmail.com: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
I guess we never agreed on a better name to change it to.
I'm not sure this needs to be blocked on the release. It was originally
blocked on 0.7.0 because that was a
Comment #30 on issue 1735 by ondrej.c...@gmail.com: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
I would be ok with head and tail, however I am against renaming args (+1 to
what Aaron said), so if we stick to args (and I actually like .args), then
I don't see
Updates:
Labels: -WrongResult
Comment #32 on issue 1735 by asmeu...@gmail.com: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
Updates:
Status: NeedsDecision
Comment #29 on issue 1735 by asmeu...@gmail.com: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
Well, if we are going to rename it, let's do it now, so we can start the
deprecation cycle. Did we ever come up with a better
Updates:
Summary: Rename .func attribute
Labels: -Priority-High -Milestone-Release0.7.0 Priority-Medium
Milestone-Release0.7.1
Comment #27 on issue 1735 by asmeurer: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
I am postponing this. If we decide to
Comment #26 on issue 1735 by asmeurer: Rename .func attribute (.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
What needs to be done here?
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group, send email to
Comment #25 on issue 1735 by elliso...@gmail.com: Rename .func attribute
(.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
I have found the .func name to be extremely confusing and would definitely
recommend renaming itAs I have implemented more things in sympy for the
Comment #23 on issue 1735 by ronan.l...@gmail.com: Rename .func attribute
(.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
'func' isn't generic enough. It doesn't work well for objects like Tuple,
Add or Integral which don't map to mathematical functions. It's even
Comment #24 on issue 1735 by smi...@gmail.com: Rename .func attribute
(.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
It's generic in the sense that a func has args (and there is function for
Integrals to get the function contained in the func). But what about
cls?,
Comment #20 on issue 1735 by ronan.l...@gmail.com: Rename .func attribute
(.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
The point is that we don't want that invariant if we want to resolve issue
1688 (and issue 2006, etc.) There's basically no way to allow sin to behave
Comment #21 on issue 1735 by asmeurer: Rename .func attribute (.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
I see. I vote for .func then.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group, send email to
Updates:
Summary: Rename .func attribute
Labels: -Priority-Medium Priority-High Milestone-Release0.7.0
Comment #12 on issue 1735 by ronan.l...@gmail.com: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
The decision on renaming .func should be made
Comment #13 on issue 1735 by Vinzent.Steinberg: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
So the candidates are 'head', 'type' and 'func'? Any preferences?
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To
Updates:
Summary: Rename .func attribute (.args too?)
Comment #15 on issue 1735 by Vinzent.Steinberg: Rename .func attribute
(.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
'tail' is also an interesting choice.
--
You received this message because you are
Comment #16 on issue 1735 by asmeurer: Rename .func attribute (.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
I think type is the only one that actually describes what it is (cls is
generally reserved for the first argument of class methods, so I wouldn't
use that).
-1
Comment #17 on issue 1735 by asmeurer: Rename .func attribute (.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
Actually, 'type' is only good if we plan on maintaining this invariant:
In [30]: atan(x).func is atan
Out[30]: True
In [31]: type(atan(x)) is atan
Out[31]: True
Comment #18 on issue 1735 by Vinzent.Steinberg: Rename .func attribute
(.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
'type' clashes with the built-in though.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this
Comment #19 on issue 1735 by asmeurer: Rename .func attribute (.args too?)
http://code.google.com/p/sympy/issues/detail?id=1735
Is there a problem with that if it will only be an attribute?
Actually, if we want that invariant, then why can't we just not have it and
just have people use
20 matches
Mail list logo
