On Wednesday, May 13, 2020 at 11:47:22 PM UTC+5:30, Aaron Meurer wrote:
>
> What sorts of things is it able to parse?
>
As of now, it can do stuff like
- "What is the maximum of x,3,4,5,y" which returns Max(3,4,5,x,y)
(passed to sympify)
- "Find the sum of x, x+y, x^3" -> sum(x,
(ps I'm aware that the examples (sum, Max) I gave up there use iterables )
Here's an excerpt from the model training dataset
what be the maximum of D, m => Max ( D , m )
what be the max of D, m => Max ( D , m )
what be the biggest of D, m => Max ( D , m )
find the sum of D, m => sum ( D , m )
find
We should add this to SymPy Gamma once you have this working.
Aaron Meurer
On Wed, May 13, 2020 at 1:03 PM Moses Paul wrote:
>
> (ps I'm aware that the examples (sum, Max) I gave up there use iterables )
> Here's an excerpt from the model training dataset
> what be the maximum of D, m => Max (
What sorts of things is it able to parse?
I don't know if there is a well structured glossary of SymPy
functions. The default namespace (what gets imported with "from sympy
import *") is the best place to start.
Aaron Meurer
On Wed, May 13, 2020 at 11:19 AM Moses Paul wrote:
>
> So I've been
So I've been working on an NLP parser for sympy.
This is how it works,
- The Input is first "cleaned up" and rewritten into a structure that is
comprehended by a NMT model (seq2seq)
- The processed input is passed on to the model which then gives a
specific type of output, which is
On 13/05/2020 23:36, Jason Moore wrote:
I had a look at the backwards incompatibilities.
This one stood out:
Submodule names are no longer imported with |from sympy import *|.
They can still be imported directly like |from sympy import core| or
accessed like |sympy.core|, or like
On Wed, 13 May 2020 at 23:39, David Bailey wrote:
>
> Dear Group,
>
> I notice this item in the highlights of 1.6.
>
> DEPRECATION: Passing Poly as the integrand to the integrate function or
> Integral class is now deprecated. Use the integrate method instead e.g.
> Poly(x, x).integrate(x)
>
>
Hi all,
I'm about to put up the release candidate for sympy 1.6. I think that
the release blockers are covered and the performance regressions
identified so far have been addressed. Thanks to all who have helped
with that.
I have been through the release notes and tried to extract what are
the
I've noticed in the past as well that it is not always easy to pick
out highlights. Typically the only obvious thing has been completed
GSoC projects. It may be prudent to just remove the section if we
can't find anything obvious to put there. It isn't as necessary as it
used to be since we now
On Wed, 13 May 2020 at 23:36, Jason Moore wrote:
>
> I had a look at the backwards incompatibilities.
>
> This one stood out:
>
> Submodule names are no longer imported with from sympy import *. They can
> still be imported directly like from sympy import core or accessed like
> sympy.core, or
I had a look at the backwards incompatibilities.
This one stood out:
Submodule names are no longer imported with from sympy import *. They can
still be imported directly like from sympy import core or accessed like
sympy.core, or like sys.modules['sympy.simplify'] for modules that share
names
This fixes a lot of issues like
https://github.com/sympy/sympy/issues/15536 and
https://github.com/sympy/sympy/issues/17626, where it was previously
impossible to reference names in a way you would expect, due to
submodule names that are the same as other submodules or as functions.
Another
On Thu, 14 May 2020 at 00:34, David Bailey wrote:
>
> On 13/05/2020 23:36, Jason Moore wrote:
>
> I had a look at the backwards incompatibilities.
>
> This one stood out:
>
> Submodule names are no longer imported with from sympy import *. They can
> still be imported directly like from sympy
On 13/05/2020 20:03, Moses Paul wrote:
(ps I'm aware that the examples (sum, Max) I gave up there use iterables )
Here's an excerpt from the model training dataset
|
what be the maximum of D,m =>Max(D ,m )
what be the max of D,m =>Max(D ,m )
what be the biggest of D,m =>Max(D ,m )
find the sum
Hi all,
It is my pleasure to announce the release of SymPy 1.6rc1 which is the
first and probably only release candidate for SymPy 1.6. This is a
preview release and its use is not recommended in production settings.
Please do test this out because unless we hear of problems this will
shortly
Thank you so much for working on this.
Aaron Meurer
On Wed, May 13, 2020 at 4:54 PM Oscar Benjamin
wrote:
>
> Hi all,
>
> It is my pleasure to announce the release of SymPy 1.6rc1 which is the
> first and probably only release candidate for SymPy 1.6. This is a
> preview release and its use is
On Wed, May 13, 2020 at 5:34 PM David Bailey wrote:
>
> On 13/05/2020 23:36, Jason Moore wrote:
>
> I had a look at the backwards incompatibilities.
>
> This one stood out:
>
> Submodule names are no longer imported with from sympy import *. They can
> still be imported directly like from sympy
> (Actually I've just realised this still happens on 1.6 because evalf
> is listed in __all__...)
Do we have tests for import *? We ought to test that certain things
are not included, like modules or non-sympy objects. It's less
necessary with __all__ and pyflakes checks, but maybe still a good
Dear Group,
I notice this item in the highlights of 1.6.
DEPRECATION: Passing Poly as the integrand to the |integrate| function
or |Integral| class is now deprecated. Use the integrate method instead
e.g. |Poly(x, x).integrate(x)|
|I do feel a little uneasy about pushing people to use
19 matches
Mail list logo
