Comment #41 on issue 1757 by ronan.l...@gmail.com: coding style
http://code.google.com/p/sympy/issues/detail?id=1757
'self' isn't just any function argument, it has a (purely conventional)
specific meaning. Rebinding it breaks the implicit promises carried by the
name (e.g. the object named
Comment #42 on issue 1757 by ronan.l...@gmail.com: coding style
http://code.google.com/p/sympy/issues/detail?id=1757
I disagree with 1) because in many cases it's more natural to not use
self.
I really don't think there are "many cases". I agree it's debatable for
some special methods like
Comment #43 on issue 1757 by Vinzent.Steinberg: coding style
http://code.google.com/p/sympy/issues/detail?id=1757
like "def __add__(a, b):"
In this case I'd rather use 'self' and 'other', because you might have to
normalize 'other', if you want to support more than just instances of your
Updates:
Labels: -Priority-Medium Priority-High Milestone-Release0.7.0
Comment #3 on issue 1721 by ronan.l...@gmail.com: Rename class 'Real'
http://code.google.com/p/sympy/issues/detail?id=1721
This should be done before releasing 0.7.0 or not at all.
--
You received this message becaus
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 whil
Updates:
Status: Fixed
Comment #13 on issue 1915 by ronan.l...@gmail.com: Unify make_list with
as_Add/as_Mul
http://code.google.com/p/sympy/issues/detail?id=1915
Make_args was pushed in.
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" grou
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 po
Comment #14 on issue 1735 by mattpap: Rename .func attribute
http://code.google.com/p/sympy/issues/detail?id=1735
Maybe 'cls'? But I guess only four letter names are under consideration. I
like 'head'. Then we should have 'tail' alias for 'args' and we will have
Mathematica naming convention
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 subscribed
Comment #44 on issue 1757 by asmeurer: coding style
http://code.google.com/p/sympy/issues/detail?id=1757
In any case, this should be considered a guideline that can be broken if,
but only if, there is a good reason to do so.
OK. I agree. So this means that it should *not* go in the quality
Comment #4 on issue 1721 by asmeurer: Rename class 'Real'
http://code.google.com/p/sympy/issues/detail?id=1721
Why or not at all? Because it's a point release?
Anyway, I am +1 on renaming it to Float, this makes more sense, not so much
because of the precision thing, but because it makes it
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 fo
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
i.e.
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 thi
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 type(e
Status: Accepted
Owner: asmeurer
CC: mattpap
Labels: Type-Defect Priority-Medium Printing
New issue 2138 by asmeurer: isympy -o option does not affect print (str)
order
http://code.google.com/p/sympy/issues/detail?id=2138
isympy -o lex:
In [9]: print x**2 + x + 1
1 + x + x**2
In [10]: x**2
Updates:
Labels: -NeedsReview NeedsBetterPatch smichr
Comment #6 on issue 2126 by asmeurer: fix doctest or quality testing to
recognize doctests
http://code.google.com/p/sympy/issues/detail?id=2126
See the pull request.
--
You received this message because you are subscribed to the G
Updates:
Labels: -Milestone-Release0.8.0 Milestone-Release0.7.1
Comment #4 on issue 1880 by asmeurer: Matrix(...).det() takes forever
http://code.google.com/p/sympy/issues/detail?id=1880
(No comment was entered for this change.)
--
You received this message because you are subscribed to
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #19 on issue 1038 by asmeurer: (sin(x)*cos(x)).series(x, 0, 1000)
takes forever
http://code.google.com/p/sympy/issues/detail?id=1038
And again...
--
You received this message because you are subscribed to the Goo
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #52 on issue 1047 by asmeurer: Suggested new assumption system
http://code.google.com/p/sympy/issues/detail?id=1047
Unfortunately, the new assumptions won't be able to make into 0.7.0, other
than what is already in
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.8.0
Comment #12 on issue 1262 by asmeurer: fix sympy to work in python3.0
http://code.google.com/p/sympy/issues/detail?id=1262
This isn't too high of a priority for me (mostly because I am not looking
forward to maintaining th
Updates:
Cc: mattpap
Comment #9 on issue 1276 by asmeurer: solve(-1 + x**2 +
0.111*(1.00 + 2.00*x)**2,x) fails
http://code.google.com/p/sympy/issues/detail?id=1276
So is this issue completely fixed in the new polys, Mateusz?
--
You received this me
Status: Accepted
Owner: smichr
Labels: Type-Defect Priority-Medium NeedsReview
New issue 2139 by smichr: _new_rawargs needs to watch for Atoms
http://code.google.com/p/sympy/issues/detail?id=2139
from the commit message:
_new_rawargs is the function that should be used to rebuild the
un
Issue 2139: _new_rawargs needs to watch for Atoms
http://code.google.com/p/sympy/issues/detail?id=2139
This issue is now blocking issue 2136.
See http://code.google.com/p/sympy/issues/detail?id=2136
--
You received this message because you are listed in the owner
or CC fields of this issue, or b
Updates:
Blockedon: 2139
Comment #2 on issue 2136 by smichr: polygamma expansion problems
http://code.google.com/p/sympy/issues/detail?id=2136
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To
Comment #1 on issue 2139 by smichr: _new_rawargs needs to watch for Atoms
http://code.google.com/p/sympy/issues/detail?id=2139
https://github.com/sympy/sympy/pull/66
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send e
Updates:
Labels: NeedsReview smichr
Comment #3 on issue 2136 by smichr: polygamma expansion problems
http://code.google.com/p/sympy/issues/detail?id=2136
https://github.com/sympy/sympy/pull/66
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" g
Updates:
Labels: smichr
Comment #2 on issue 2139 by smichr: _new_rawargs needs to watch for Atoms
http://code.google.com/p/sympy/issues/detail?id=2139
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" g
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #23 on issue 1291 by asmeurer: reduce the import sympy time
http://code.google.com/p/sympy/issues/detail?id=1291
See some of the discussion at
http://groups.google.com/group/sympy/browse_thread/thread/f471ea9a8d3ef
Updates:
Status: Accepted
Comment #5 on issue 1721 by asmeurer: Rename class 'Real'
http://code.google.com/p/sympy/issues/detail?id=1721
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #7 on issue 1797 by asmeurer: fix isympy for upcoming ipython 0.11
http://code.google.com/p/sympy/issues/detail?id=1797
IPython 0.11 doesn't seem to be coming out for a while still, so pushing
back the milestone re
Status: Accepted
Owner: asmeurer
Labels: Type-Defect Priority-Medium Documentation
New issue 2140 by asmeurer: Fix broken links in the docs
http://code.google.com/p/sympy/issues/detail?id=2140
cd doc;make linkcheck will check all the web links in the Sphinx docs for
integrity. Any one that tu
Updates:
Labels: NeedsReview asmeurer
Comment #4 on issue 1945 by asmeurer: Fix as_numer_denom() docstring and
add Expr to the Sphinx docs
http://code.google.com/p/sympy/issues/detail?id=1945
I added Expr to the Sphinx docs and went ahead and fixed the
as_numer_denom() issue as well
Comment #9 on issue 1946 by asmeurer: Recursion error with
SYMPY_GROUND_TYPES=sympy (caching problem)
http://code.google.com/p/sympy/issues/detail?id=1946
Mateusz, did you ever apply your patch from comment 3 and/or the patch and
similar fixes from comment 4 (or using isinstance) in your br
Updates:
Labels: -Priority-High Priority-Critical NeedsReview asmeurer
Comment #5 on issue 1947 by asmeurer: @property methods are not doctested
http://code.google.com/p/sympy/issues/detail?id=1947
I figured it out.
From the commit message:
The problem is that we are sorting our do
Comment #6 on issue 2031 by asmeurer: Add 'auto' flag to div(), quo() and
rem()
http://code.google.com/p/sympy/issues/detail?id=2031
Mateusz, were you going to do this before the release or not? I really
don't care either way myself.
--
You received this message because you are subscribe
Updates:
Labels: -Priority-High -Milestone-Release0.7.0 -markdewing -NeedsReview
Comment #5 on issue 2070 by asmeurer: All elements of .args should be Basic
http://code.google.com/p/sympy/issues/detail?id=2070
I might consider issue 1206 to be part of this (I need to look into it
more)
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #4 on issue 2089 by asmeurer: Move MediaWiki pages over to the
GitHub site
http://code.google.com/p/sympy/issues/detail?id=2089
This is important, but it is definitely one thing I do not have time to do
before t
Updates:
Labels: Milestone-Release0.7.1
Comment #1 on issue 2140 by asmeurer: Fix broken links in the docs
http://code.google.com/p/sympy/issues/detail?id=2140
Let's fix this before the next release (unless someone wants to fix it
sooner :)
--
You received this message because you ar
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.8.0
Comment #20 on issue 391 by asmeurer: naming for subclasses of Function ?
http://code.google.com/p/sympy/issues/detail?id=391
(No comment was entered for this change.)
--
You received this message because you are subscribed
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #22 on issue 398 by asmeurer: An idea: assumption model based on
Interval
http://code.google.com/p/sympy/issues/detail?id=398
Very optimistically rescheduling to the next release.
--
You received this message bec
Comment #7 on issue 588 by asmeurer: simplify should be better at detecting
repeated factors
http://code.google.com/p/sympy/issues/detail?id=588
What should we do about this?
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this g
Updates:
Labels: -Milestone-Release0.7.0
Blockedon: 2010
Comment #10 on issue 829 by asmeurer: Improve simplify() to handle result
from integrate(log(k**2-m**2), k)
http://code.google.com/p/sympy/issues/detail?id=829
Here is comment 9 a little clearer, because we can now just
Issue 2010: Integration with the full Risch Algorithm
http://code.google.com/p/sympy/issues/detail?id=2010
This issue is now blocking issue 829.
See http://code.google.com/p/sympy/issues/detail?id=829
--
You received this message because you are listed in the owner
or CC fields of this issue, or
44 matches
Mail list logo