Yes, you're right. One of PR was merged yesterday.
On Sunday, July 1, 2012 11:57:04 PM UTC+3, Stefan Krastanov wrote:
>
> Slightly off topic, you have already merged contributions, however I
> am not sure that you were added to the AUTHORS file.
>
--
You received this message because you are s
You talked me into it =) I implement it "simply" with default argument
(and make another PR). If this implementation will be better,
it will be possible to abandon decorator.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To view this discussion on t
Hi,
There are opposite opinions about usage of decorator
in PR #1226.
In brief: decorator used as an arguments checker for __new__ method
(it's really helps to reduce the length of code).
Honestly the PR is stuck. If you have any
ideas to resolve this dispute. please write your comment.
Regards
Hi,
There are opposite opinions about usage of decorator
in PR #1226.
In brief: decorator used as an arguments checker for __new__ method
(it's really helps to reduce the length of code).
Honestly the PR is stuck. If you have any
ideas to resolve this dispute. please write your comment.
Regards
The problem is that I am using a cls.property = True in a __new__ method.
Solved by adding __init__ method inherited class implementation
--
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.c
Hi,
Can someone help me to resolve following uncertainty ?
I have class that inherits Matrix class. And when I trying to add a
property to inherited class
I've got following:
>>> a = SomeClass(10, 3, property=True)
>>> a.property
True
>>> b = SomeClass(10, 2, property=False)
>>> a
It's a good idea. But a big number of arguments is confusing a lot.
may be instead of a large set of arguments in a function it's better
to implement something like a style-class?
On Sunday, April 15, 2012 11:22:02 PM UTC+3, Aaron Meurer wrote:
>
> It would probably be cleaner to make plot() call
The patch was revised.
The discussion on "gaussopt module patch" is opened in new pull request
https://github.com/sympy/sympy/pull/1226
--
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.co
Corresponding pull request:
https://github.com/sympy/sympy/pull/1226
Improved formalism in gaussopt module
Implemented new class ThinPrism which describes single angle thin
prism that can be used for deviation of geometrical and gaussian (not impl.)
beam propagation.
Added optimized *mul* meth
Hi,
Just finished to perform PATCH requirment for GSoC.
https://github.com/sympy/sympy/pull/1219
Added the beam_plot and beam_plot2 utilities (one of TODO tasks) for
plotting gaussian beam propagation (waist parameter). The first one uses
pyglet (this method appears to be not convenient and
jects.
As for the patch requirement, I'm currently finishing some of #TODO
tasks in gaussian optics module.
Best regards, Alexandr Popov.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To view this discussion on the web visit
https:/
11 matches
Mail list logo