Hi,
On 21 January 2015 at 22:06, Bastian Weber <
bastia...@gmx-topmail.de> wrote:
> On 01/21/2015 08:26 PM, Aaron Meurer wrote:
>> The domain argument is likely undocumented.
> Thats a pity.
Yeah, documentation of polys module is below standards.
>
>> The polys are unfortunately
>> not so well documented, beyond the docstrings on the methods of Poly.
>
> What I am looking for is the documentation of the "constructor" of Poly.
>
> Suppose, I would like to write a doctest for
>
> Poly(..., domain='EX').
>
> Where would it live?
You could add it to Poly class, so that `Poly?` in IPython gave
something useful.
In general, you should avoid using EX, as this is the "catch all"
option, that's there to not fail miserably, but doesn't give you any
guarantees. Given the original polynomial, i.e. p_expr = a0 + a1*x +
a2*x**2, I would use simply Poly(p_expr, x) or Poly(p_expr, x,
field=True) if you want to work over a field. But all depends on the
problem you try to solve. Any specifics would be helpful to advice
anything.
The list of possible options to Poly is available in
sympy/polys/polyoptions.py:96 (obviously barely or not documented).
Mateusz
>
>> You could also look at Mateusz Paprocki's master's thesis.
>>
>> Regarding rebuilding the docs, as far as I know Sphinx doesn't generate
>> TOCs for methods.
>
> It would already help, if the _classes_ showed up in the TOC (e.g. the
> class Poly). Maybe I have a look on it.
>
>
> Bastian.
>
> To view this discussion on the web visit
https://groups.google.com/d/msgid/sympy/54C014C5.8070403%40gmx-topmail.de.