Thank you, this is exactly what I wanted. Sorry for the late reply.
Regards,
Mani
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/sympy/-/YhWKUu4SOYUJ.
To post to this group, se
Hello,
I'm trying to use the binary from the git source tree since I wanted the
latest version of simplify(), but I get the following error when I try to
use bin/isympy.
Traceback (most recent call last):
File "isympy", line 162, in
main()
File "isympy", line 159, in main
init_sess
Hi.
Can you give more information about your system? What version of
Python do you have installed? What kind of terminal are you using (in
particular, does it support unicode)? Are you passing any options to
the isympy command?
Aaron Meurer
On Tue, Jun 21, 2011 at 1:29 AM, Mani Chandra wrote
Hi,
On 21 June 2011 09:32, Aaron Meurer wrote:
> Hi.
>
> Can you give more information about your system? What version of
> Python do you have installed? What kind of terminal are you using (in
> particular, does it support unicode)? Are you passing any options to
> the isympy command?
>
Als
Hi,
2011/6/20 krastanov.ste...@gmail.com
>
>
> 2011/6/20 Mateusz Paprocki
>
>> Hi,
>>
>> 2011/6/20 krastanov.ste...@gmail.com
>>
>> Certain tests pass if unicode characters are escaped (like in u"\")
>>> but do not pass if the character is written in unicode (like u"Ф"). For
>>> examples s
2011/6/21 Mateusz Paprocki :
> Hi,
>
> 2011/6/20 krastanov.ste...@gmail.com
>>
>>
>> 2011/6/20 Mateusz Paprocki
>>>
>>> Hi,
>>>
>>> 2011/6/20 krastanov.ste...@gmail.com
Certain tests pass if unicode characters are escaped (like in u"\")
but do not pass if the character is writ
Hi,
1) Python version: Python 2.7.1 (Enthought Python Distribution 7.0)
2) Terminal: Gnome terminal
3) I run it using ./isympy in the bin folder.
Mani
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To view this discussion on the web visit
https://g
On Tue, Jun 21, 2011 at 2:04 AM, Mani Chandra wrote:
> Hi,
> 1) Python version: Python 2.7.1 (Enthought Python Distribution 7.0)
> 2) Terminal: Gnome terminal
> 3) I run it using ./isympy in the bin folder.
This is your problem. You need to run it from the sympy folder, i.e.,
you should be runni
Thanks! It works now.
Mani
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/sympy/-/Omavm8TZT30J.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from
So I suppose the whole printing of physics.quantum must be refactored. Maybe
I'm capable of doing that, but before thinking about it I prefer to refactor
the tests and get the current pull request in as I see it as an improvement.
Should I pursue this or you think it's better to scrap the pull req
https://github.com/sympy/sympy/pull/444
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from this group, send email to
sympy+unsubscr...@googlegroups.com.
For more options, vi
Hello,
I have been using PostGis and Django Geos for a long time now, however
today they both failed me. This prompted me to search and find sympy,
so here I am.
I am trying to find the perpendicular distance from a Line to a Point.
PostGis and Django Geos will only let me calculate the distance
>>> help(Line.perpendicular_segment)
Help on method perpendicular_segment in module sympy.geometry.line:
perpendicular_segment(self, p) unbound sympy.geometry.line.Line
method
Returns a new Segment which connects p to a point on this linear
entity and is al
Chris thank you for your quick reply.
The original example I posted used test data, below is as far as I
have gotten with real numbers.
from sympy.geometry import *
# Define a Line given two points p1 and p2.
p1 = Point(-694310.42867240659, 7051910.5392115889)
p2 = Point(-694286.161023414, 705191
Hi,
2011/6/21 krastanov.ste...@gmail.com
> So I suppose the whole printing of physics.quantum must be refactored.
> Maybe I'm capable of doing that, but before thinking about it I prefer to
> refactor the tests and get the current pull request in as I see it as an
> improvement.
>
> Should I pur
I think we should not warn about floats; we should just convert them in
routines such as this. Until then, try change your floats to Rational, e.g.
>>> def rat(d):
... return S(str(d), rational=True)
...
>>> p1 = Point(rat(-694310.42867240659), rat(7051910.5392115889))
>>> p2
Hello sympy-folk,
I just pulled a fresh master and then did a git rebase on one of my
branches. After I did the rebase, I ran the tests and got a few failures.
I'm running Python 2.6.2 on Mac OS X. They all seemed to be related to
ordered_iter. Is this a problem on my end or something bad in maste
Hi,
On Tue, Jun 21, 2011 at 5:09 PM, Tomo Lazovich wrote:
> Hello sympy-folk,
>
> I just pulled a fresh master and then did a git rebase on one of my
> branches. After I did the rebase, I ran the tests and got a few failures.
> I'm running Python 2.6.2 on Mac OS X. They all seemed to be related t
Ah it seems I lost the ordered_iter at some point during rebasing. Thanks!
On Tue, Jun 21, 2011 at 3:18 PM, Renato Coutinho
wrote:
> Hi,
>
> On Tue, Jun 21, 2011 at 5:09 PM, Tomo Lazovich
> wrote:
> > Hello sympy-folk,
> >
> > I just pulled a fresh master and then did a git rebase on one of my
>
Ok, it now seems I'm lost in the world of git. I did the git rebase
mentioned above, and in the process I think I lost a couple of imports,
which I then re-added to get the tests to pass. After having made some
changes of my own to other parts of the code, I committed, but when I try to
push this c
On 21.06.2011 22:56, Tomo Lazovich wrote:
Ok, it now seems I'm lost in the world of git. I did the git rebase
mentioned above, and in the process I think I lost a couple of imports,
which I then re-added to get the tests to pass. After having made some
changes of my own to other parts of the co
On Tue, Jun 21, 2011 at 9:57 AM, cathal coffey wrote:
> Chris thank you for your quick reply.
> The original example I posted used test data, below is as far as I
> have gotten with real numbers.
>
> from sympy.geometry import *
>
> # Define a Line given two points p1 and p2.
> p1 = Point(-694310.
In the future, it's a good idea to run the tests after a merge
conflict resolution (i.e., before typing "git rebase --continue"), at
least for the relevant files, to make sure you did it correctly.
Aaron Meurer
On Tue, Jun 21, 2011 at 4:02 PM, Tom Bachmann wrote:
>
>
> On 21.06.2011 22:56, Tomo
On Sun, Jun 19, 2011 at 9:31 PM, Aaron Meurer wrote:
> I think the answer to 1 and 3 depend on what the server limitations
> are. If the server can handle running the tests after each commit,
> then I say go for it. Depending on what the setup is, this might also
> include cost limitations. So
24 matches
Mail list logo
