Status: New
Owner:
Labels: Type-Defect Priority-Medium Logic
New issue 3679 by srjoglek...@gmail.com: literal_symbol should return error
if arg not literal
http://code.google.com/p/sympy/issues/detail?id=3679
By the definition of the word 'literal', shouldn't literal_symbol raise an
Updates:
Status: Fixed
Labels: -NeedsReview
Comment #3 on issue 3670 by julien.r...@gmail.com: Latex printing of (x +
1)**Rational(3, 2) with fold_frac_powers=True
http://code.google.com/p/sympy/issues/detail?id=3670
(No comment was entered for this change.)
--
You received
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3680 by bjo...@gmail.com: Unexpected behaviour of .copy() on
Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
In [1]: import sympy
In [2]: x=sympy.Symbol('x')
In [3]: x.copy()
Comment #7 on issue 2969 by skirpic...@gmail.com: sqrt(sin(x)).series(x, 0,
7) is wrong
http://code.google.com/p/sympy/issues/detail?id=2969
https://github.com/sympy/sympy/pull/1863
--
You received this message because this project is configured to send all
issue notifications to this
Status: Valid
Owner:
CC: mrock...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 3681 by smi...@gmail.com: bottom_up runs into problem with Pow
http://code.google.com/p/sympy/issues/detail?id=3681
from sympy.strategies.traverse import *
def f(x):
... if x.is_Symbol:
... x
Updates:
Status: Valid
Comment #1 on issue 3679 by smi...@gmail.com: literal_symbol should return
error if arg not literal
http://code.google.com/p/sympy/issues/detail?id=3679
This is in sympy.logic.inference.py. Perhaps the logic could be
```
if literal.func is Not:
Comment #2 on issue 3679 by srjoglek...@gmail.com: literal_symbol should
return error if arg not literal
http://code.google.com/p/sympy/issues/detail?id=3679
An error would make more sense than None I guess. That is why I suggested a
is_literal function, for the user to check if an
Updates:
Status: Valid
Comment #1 on issue 3680 by smi...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
Hmmm...a copy method could be given to Symbol, but a there is no such thing
as a copy of
Comment #2 on issue 3680 by bjo...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
I think a copy method would be very useful. I have a class where I want the
instances to be able to create a new
Comment #3 on issue 3680 by smi...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
Someone else will have to chime in here. I don't think it's possible to
have a copy of a symbol with all the same
Comment #35 on issue 694 by iurii.de...@gmail.com: Add tests from Review
of CAS mathematical capabilities, by Michael Wester
http://code.google.com/p/sympy/issues/detail?id=694
Hello!
I want to participate in gsoc 2013. Can I get this task as a test?
--
You received this message because
Comment #1 on issue 3681 by mrock...@gmail.com: bottom_up runs into problem
with Pow
http://code.google.com/p/sympy/issues/detail?id=3681
Traveral strategies use Basic.__new__ to construct the tree without calling
object constructors. Many Exprs require construction to function
Comment #4 on issue 3680 by asmeu...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
I guess just implement Symbol.copy. SymPy objects are immutable, so
pointing to the same objects should not be a
Status: Valid
Owner:
Labels: Type-Defect Priority-Medium Core
New issue 3682 by sean.v@gmail.com: .copy() does not work on Symbol
http://code.google.com/p/sympy/issues/detail?id=3682
When creating a new symbol, nothing is returned in the .args, making the
copy method fail.
In [1]:
Comment #5 on issue 3680 by bjo...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
Ok, thanks. I looked into the caching, and as you said, it will still point
to the same object no matter what. So I
Comment #4 on issue 3563 by rathmann...@gmail.com: Implement faster
combinatorial enumeration algorithms
http://code.google.com/p/sympy/issues/detail?id=3563
A start on some of this is at pull request
https://github.com/sympy/sympy/pull/1848
I am attaching an updated multiset_taocp.py,
Updates:
Status: Duplicate
Mergedinto: 3680
Comment #1 on issue 3682 by asmeu...@gmail.com: .copy() does not work on
Symbol
http://code.google.com/p/sympy/issues/detail?id=3682
Coincidence?
--
You received this message because this project is configured to send all
issue
Comment #6 on issue 3680 by asmeu...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
Issue 3682 has been merged into this issue.
--
You received this message because this project is configured to send all
Comment #7 on issue 3680 by asmeu...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
It's not private because it is public API. You are encouraged to use that
attribute to read the name of a symbol. But
Comment #2 on issue 3682 by sean.v@gmail.com: .copy() does not work on
Symbol
http://code.google.com/p/sympy/issues/detail?id=3682
Oops, forgot to do a search. Yes, that's the same.
--
You received this message because this project is configured to send all
issue notifications to this
Comment #8 on issue 3680 by sean.v@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
Issue 3682 has been merged into this issue.
--
You received this message because this project is configured to send
Comment #3 on issue 3682 by asmeu...@gmail.com: .copy() does not work on
Symbol
http://code.google.com/p/sympy/issues/detail?id=3682
It was just odd that these were reported so soon after one another. But I
see now that you were discussing this on IRC.
--
You received this message
Comment #9 on issue 3680 by asmeu...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
Issue 3682 has been merged into this issue.
--
You received this message because this project is configured to send all
Updates:
Cc: smi...@gmail.com
Comment #10 on issue 3680 by asmeu...@gmail.com: Unexpected behaviour
of .copy() on Symbol instance (master git branch)
http://code.google.com/p/sympy/issues/detail?id=3680
Chris, what is the point of Basic.copy()? Having a copy method on an
immutable
Comment #2 on issue 3681 by smi...@gmail.com: bottom_up runs into problem
with Pow
http://code.google.com/p/sympy/issues/detail?id=3681
How about on this one:
rebuild(bottom_up(lambda x: expand(x))(x+x*(x+1)))
...
File sympy\simplify\simplify.py, line 91, in fraction
if
Comment #3 on issue 3679 by srjoglek...@gmail.com: literal_symbol should
return error if arg not literal
http://code.google.com/p/sympy/issues/detail?id=3679
https://github.com/sympy/sympy/pull/1865
--
You received this message because this project is configured to send all
issue
On Sat, Mar 2, 2013 at 2:29 AM, G B g.c.b.at.w...@gmail.com wrote:
Ah thanks-- always comforting to know I'm not the first person to
complain... =) And the broadcasting argument makes the current design less
mystifying.
In my case, I have a sympy equation that I lambdify to a function that
As is probably becoming apparent, I've been busy lambdifying stuff...
My latest runtime problem is trying to convolve things with DiracDeltas.
The result comes back with a Heaviside function. A quick look through the
numpy docs doesn't show a numpy equivalent function for either DiracDelta
Thanks,
I'll try implementing them that way, as you said naively implementing
it can worsen the timings. Maybe I can find some better way out.
As I'm new to sympy and opensource programming even naive
implementations can serve as a learning experience.
I'll surely update you about the results.
Just look where the inputs go/get saved. That will usually be enough.
However, there might be some nasty magic involved because of the way
we create mathematical objects in sympy (subclasses of Basic).
All subclasses of Basic have a private attribute _args, that is used
when comparing objects,
Hello,
This is in reference to my pull request
https://github.com/sympy/sympy/pull/1864 . All the tests are passing, but a
doctest gives a strange error.
This is my doctest.
dsolve(sin(x)*cos(f(x)) + cos(x)*sin(f(x))*f(x).diff(x), f(x),
... hint='best')
which gives the output as
Thank you very much for the quick reply and the code! I will start to play
around with the new code.
Multivectors do not inherit from sympy symbols so solve does not work.
How hard would it be to implement this? Is it only a (possibly difficult,
time consuming) programming exercise or is there
Hello,
My name's Ben and I would like to become involved developing SymPy.
However, I'm finding the situation confusing. I've spent a while becoming
familiar with the code, but can't find an area where I can
help. I've checked the issues page but because I am just beginning I found
the page
Hi,
I am a doing my masters in Intelligent Embedded Systems, and planning to
apply for GSOC-2013.
I have already found the most of the relevant links, and am reading about
the git and sympy workflow right now.
Just thought I would drop by to introduce myself and say Hello. :)
-regards,
On 03/04/2013 03:41 PM, tsc wrote:
Thank you very much for the quick reply and the code! I will start to
play around with the new code.
Multivectors do not inherit from sympy symbols so solve does not work.
How hard would it be to implement this? Is it only a (possibly
difficult, time
Hi,
On 4 March 2013 12:10, Ben Fishbein fishbe...@gmail.com wrote:
Hello,
My name's Ben and I would like to become involved developing SymPy. However,
I'm finding the situation confusing. I've spent a while becoming familiar
with the code, but can't find an area where I can help. I've checked
I don't get the doctest failure in your current branch.
--
You received this message because you are subscribed to the Google Groups
sympy group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sympy+unsubscr...@googlegroups.com.
To post to this group, send
Exactly what I was looking for. Thanks you.
On Monday, March 4, 2013 4:13:45 PM UTC-5, Mateusz Paprocki wrote:
Hi,
On 4 March 2013 12:10, Ben Fishbein fish...@gmail.com javascript:
wrote:
Hello,
My name's Ben and I would like to become involved developing SymPy.
However,
I'm
Now having tried it, it looks like the current implementation of Piecewise
using a if test else b expressions doesn't work with numpy. The test
clause returns an array result, which doesn't like being tested as a unit.
I've implemented _print_Heaviside like this:
def
On Mar 4, 2013, at 4:02 PM, G B g.c.b.at.w...@gmail.com wrote:
Now having tried it, it looks like the current implementation of Piecewise
using a if test else b expressions doesn't work with numpy. The test
clause returns an array result, which doesn't like being tested as a unit.
I've
Here is the ticket:
cp .git/ORIG_HEAD .git/HEAD
rm -f .git/index
git reset
git rebase --abort
(at least that is the best that I've been able to do so far)
--
You received this message because you are subscribed to the Google Groups
sympy group.
To unsubscribe from this group and stop
Am 05.03.2013 03:45, schrieb smichr:
Here is the ticket:
cp .git/ORIG_HEAD .git/HEAD
rm -f .git/index
git reset
git rebase --abort
(at least that is the best that I've been able to do so far)
Removing the index seems like a good way to kill any git repo.
I'd simply start over with a new
42 matches
Mail list logo
