ion with the community.
Jason
moorepants.info
+01 530-601-9791
On Wed, Feb 10, 2021 at 4:07 PM Sudeep Sidhu
wrote:
> Jason,
>
> I'll surely look into it.
>
> So is JointsMethod good to go as GSoC project?
>
> On Wed, 10 Feb 2021, 19:15 Jason Moore, wrote:
>
>> Sudeep
ere and a good source to read about
>> JointsMethod. I have some knowledge of dynamics too so I think I can
>> implement it.
>>
>> Sudeep Sidhu
>>
>> On Tue, 9 Feb 2021, 15:28 Jason Moore, wrote:
>>
>>> I personally think completing the JointsMetho
), ...)
equations_of_motion = joint_method.generate_eoms(...)
Jason
moorepants.info
+01 530-601-9791
On Mon, Feb 8, 2021 at 2:37 PM Sudeep Sidhu
wrote:
>
>
> On Mon, 8 Feb 2021, 19:00 Jason Moore, wrote:
>
>> James worked with Featherstone's book "Rigid Body Dynamics
ctor in this year's GSoC . If
> possible please share a link of a good source to read and learn more about
> spatial vectors.
>
>>
>>
>>
>>
>>>
>>> On Mon, Feb 8, 2021, 12:50 Jason Moore wrote:
>>>
>>>> Sudeep,
>>>>
>>>>
plement *spatial vectors*.
>
> I would like to implement *Spatial Vectors* in this year's GSoC and would
> like to discuss it further.
>
> Sudeep Sidhu
>
>
>
>
>> On Sun, Feb 7, 2021 at 2:24 PM Jason Moore wrote:
>>
>>> Sudeep,
>>>
:
> Hello,
> Does someone have to be really conversant with physics to handle a project
> like that?
>
>
> On Sun, Feb 7, 2021 at 2:24 PM Jason Moore wrote:
>
>> Sudeep,
>>
>> The topics related to sympy.physics.vector/mechanics are still
>> possibili
For:
I would like to know if the idea, *Continuum Mechanics: Create a Rich 2D
> Beam Solving System*, will be considered this time or not.
> I would also like to know if it is better to
>
- implement more features in the existing beam module
- Or expand the continuum mechanics module to imp
Sudeep,
The topics related to sympy.physics.vector/mechanics are still
possibilities. I will have time to mentor this summer if someone wants to
do projects in this realm.
We have not updated the ideas page yet for this year so those could be
adjusted. Off the top of my head here are some things
Aniket,
Have a look at
https://github.com/sympy/sympy/wiki/introduction-to-contributing. Let us
know here if you have any questions.
Jason
moorepants.info
+01 530-601-9791
On Wed, Dec 23, 2020 at 1:38 PM 1 2 0 1 6 Aniket Digge <
kccaniketd2...@gmail.com> wrote:
> Hello sir/ma'am,
> ia
Thank you all for doing this. We're all seeing a future of tons of work
across thousands of repositories to migrate from Travis. SymPy is a nice
early case we can look to to mimic. These things are always quite painful
and we appreciate Oscar (and others that likely helped) for bearing that
burden.
This wouldn't work, as it needs to be done recursively:
com_sub_exprs, simpflied_new_expr = cse(new_expr.subs(dict(com_sub_exprs))
But the idea is reconstructing the new_expr fully and then cse'ing again.
Jason
moorepants.info
+01 530-601-9791
On Wed, Nov 4, 2020 at 9:57 PM Jason Mo
of common sub
expressions with that method.
Jason
moorepants.info
+01 530-601-9791
On Wed, Nov 4, 2020 at 9:57 PM Jason Moore wrote:
> I think you meant to do this:
>
> expr =
> com_sub_exprs, simplified_expr = cse(expr)
> new_expr = do_operations_on(simplif
+01 530-601-9791
On Wed, Nov 4, 2020 at 9:47 PM Aaron Meurer wrote:
> I'm not clear, what work would it have to do twice?
>
> Aaron Meurer
>
> On Wed, Nov 4, 2020 at 1:45 PM Jason Moore wrote:
> >
> > I could do that, but for very long expressions this means cse
the new
> expression before calling cse, then merging the results? I think that
> wouldn't be hard, though probably complicated enough that direct
> support could be added.
>
>
> Aaron Meurer
>
> On Wed, Nov 4, 2020 at 11:40 AM Jason Moore wrote:
> >
> > Hi,
Hi,
I'd like to be able to do something like this:
expr =
com_sub_exprs, simplified_expr = cse(expr)
new_expr = do_operations_on(simplified_expr)
com_sub_exprs, simpflied_new_expr = cse(new_expr, start_with=com_sub_exprs)
This would let the cse() of new_expr use the existing set of sub
expr
Looks like the biggest changes in GSoC over the last decade. FYI
Jason
moorepants.info
+01 530-601-9791
-- Forwarded message -
From: 'sttaylor' via Google Summer of Code Mentors List <
google-summer-of-code-mentors-l...@googlegroups.com>
Date: Mon, Oct 26, 2020 at 7:04 PM
Subject
1
On Fri, Oct 23, 2020 at 11:46 PM Jason Moore wrote:
> David,
>
> I'm not sure I understand what algebraic manipulations you are referring
> to. In the example, the algebraic manipulation is done with sympy
> variables. Only the final expressions are evaluated with floating
)
>
> for subexpr in exprs:
> print()
> print(subexpr)
> print(cse_compare(expr, syms, vals))
>
> test_expr = (sin(x+1) + 2*cos(x-3)).expand(trig=True)
> cse_compare_bottom_up(test_expr)
>
>
> Oscar
>
> On Fri, 23 Oct 2020 at 07:59, Jason
simulation and animation run. The sympy expressions
for this problem are quite large and it is tricky to get correct.
Jason
moorepants.info
+01 530-601-9791
On Fri, Oct 23, 2020 at 1:29 PM Jason Moore wrote:
> Oscar,
>
> Yes, this is what I want to check. Thanks for taking the time to wri
if e not in seen:
> yield e
> seen.add(e)
>
> # possibly better:
> #exprs = sorted(set(postorder_traversal(expr)), key=lambda e:
> e.count_ops())
> exprs = subexprs()
>
> for subexpr in exprs:
> print()
> pri
are "identical". If you are unlucky, the error propagation can be quite
> disastrous at times, but you are probably correct in that there is
> something else that is the primary issue here.
>
> BR Oscar
>
> Den tors 22 okt. 2020 kl 18:57 skrev Jason Moore :
>
&g
As far as I understand the results should match to machine precision.
We are able to match these kinds of models executed on different platforms
using different formulation techniques to machine precision (e-14 or more).
In fact, we use this to be able to verify that two independent modelers
have
Howdy,
I'm trying to track down a bug in this PR:
https://github.com/pydy/pydy/pull/122
I have quite large SymPy expressions which I evaluate with floating point
numbers. I also cse those expressions and evaluate those with the same
floating point numbers. I'm getting discrepancies in the result
Nikhil,
I recommend creating some kind of survey with carefully crafted questions
to discover what the SymPy community (users and devs) might want in a
website upgrade. Maybe you can come up with 5 or 6 key questions that take
< 5 mins to complete to try to get a broad sampling of opinions and the
Nikhil,
I'd suggest using and improving the existing tutorial:
https://docs.sympy.org/latest/tutorial/
This has been given at several prior conferences. I think it was designed
for a 4 hour session.
Jason
moorepants.info
+01 530-601-9791
On Thu, Aug 6, 2020 at 10:04 PM Nikhil Maan wrote:
>
A nice thing for a GSoD student to do would be to organize a documentation
sprint.
Jason
moorepants.info
+01 530-601-9791
On Thu, Aug 6, 2020 at 5:32 PM Matthew Brett
wrote:
> Hi,
>
> On Thu, Aug 6, 2020 at 4:10 PM David Bailey wrote:
> >
> > On 06/08/2020 00:47, Nicolas Guarin wrote:
> >
> >
I agree with this. SEPs would be a net positive. They seem to work well
with other projects.
Question: How do we know what changes require SEPs and what don't? Is the
idea that if informal proposals are brought up in our current communication
mechanisms that someone would say "this should probably
I think SymPy live is better than Thebelab because it doesn't require the
long startup time for the binder/docker container build.
Jason
moorepants.info
+01 530-601-9791
On Tue, Jul 7, 2020 at 1:42 PM Jason Moore wrote:
> > I didn't realize that thebelab requires jupyter-sph
ter-sphinx. That limits
> > its usefulness. It is a very interesting project and I hope we can
> > someday replace SymPy Live with either it or something like it.
> >
> > Aaron Meurer
> >
> > On Tue, Jul 7, 2020 at 2:13 PM Jason Moore wrote:
> > >
> >
7, 2020 at 1:05 PM Aaron Meurer wrote:
> On Tue, Jul 7, 2020 at 1:29 PM Jason Moore wrote:
> >
> > There are some ways to integrate Jupyter notebooks with Sphinx that
> didn't exist when we created the sympy-notebooks repo. One main issue is
> that you only want to commi
clarify what you
> mean?
>
> I was of the belief that SymPy possessed features relating to topics such
> as differential equations which might be used in the context of situations
> dealing with regressions.
>
> Best,
> John
>
> On Tuesday, July 7, 2020 at 3:30:06 P
John,
One issue with your proposal is that SymPy doesn't (at least explicitly) do
any of the things you mention.
Jason
moorepants.info
+01 530-601-9791
On Tue, Jul 7, 2020 at 12:26 PM John Yoon wrote:
> My tutorials/guides would primarily focus on classical machine learning
> and data science
There are some ways to integrate Jupyter notebooks with Sphinx that didn't
exist when we created the sympy-notebooks repo. One main issue is that you
only want to commit un-executed notebooks to the main SymPy repo so that
the binary outputs don't pollute and grow the git repo.
Some options:
- Co
You can suppress the output in Jupyter by appending a semi-colon at the end
of the line.
Jason
moorepants.info
+01 530-601-9791
On Mon, Jul 6, 2020 at 7:34 AM Javier Arántegui
wrote:
> Hello!
>
> Using Jupyter, when you use ‘plot’, you get the plot and a line saying
> “”. I have a couple of qu
Mohit,
The purpose of the program is to engage people that are already technical
writers with open source projects and bring in non-developers to open
source work. So it's not really a good fit for someone that's trying to
learn/start technical writing.
Jason
moorepants.info
+01 530-601-9791
On
n
moorepants.info
+01 530-601-9791
On Wed, Jun 3, 2020 at 1:06 PM Jason Moore wrote:
> Yes, this is intentional. It is really no different than this:
>
> In [1]: a = 1
>
>
> In [2]: b = 1
>
>
> In [3]: type(a)
>
> Out[3]: int
>
> In [4]: type(b)
>
&
Yes, this is intentional. It is really no different than this:
In [1]: a = 1
In [2]: b = 1
In [3]: type(a)
Out[3]: int
In [4]: type(b)
Out[4]: int
In [5]: a == b
Out[5]: True
In [6]: a is b
Out[6]: True
Jason
moorepants.info
+01 530-601-9791
On Wed, Jun 3, 2020 at 12:53 PM James Bate
ld offer some benefits.
>
> Aaron Meurer
>
> On Wed, May 27, 2020 at 3:22 AM S.Y. Lee wrote:
> >
> > I see numpy.org is now using hugo.
> > We may have consider changing the static site generator like
> > https://github.com/numpy/numpy.org/issues/29
> >
&g
e in HTML CSS Vanilla JS and
> React.JS. Link to my portfolio is https://fir-website-b6d6c.web.app/
>
> Regards
> Siddharth Kapoor
>
> On Tue, May 26, 2020 at 12:49 AM Jason Moore wrote:
>
>> Will do.
>>
>> Jason
>> moorepants.info
>> +01 530-601
We've recently released this document:
https://docs.sympy.org/latest/documentation-style-guide.html
It shows how to install everything needed to build the documentation and
gives guidelines on writing.
Jason
moorepants.info
+01 530-601-9791
On Mon, May 25, 2020 at 12:23 PM Mohit Shah
wrote:
, 2020 at 10:20 AM Jason Moore wrote:
> >
> > I was admiring the new NumPy website: https://numpy.org/ and thinking
> how some of these elements, design, and features could be a nice
> improvement to the SymPy website. The new NumPy website really gives an air
> of being a p
I was admiring the new NumPy website: https://numpy.org/ and thinking how
some of these elements, design, and features could be a nice improvement to
the SymPy website. The new NumPy website really gives an air of being a
professional piece of software that is a foundation for so many other
things.
al*
>> - gregmedlock*
>> - Michal Grňo*
>> - Bhaskar Gupta*
>> - Anubhav Gupta*
>> - Mohit Gupta*
>> - Oscar Gustafsson
>> - Johan Guzman*
>> - Johannes Hartung*
>> - Ashutosh Hathidara*
>> - Jean-Luc Herren*
>> - Thomas Hickman
&g
Thanks Oscar. I'll look at it later tonight to give you a review.
Jason
moorepants.info
+01 530-601-9791
On Thu, May 14, 2020 at 3:45 PM Oscar Benjamin
wrote:
> On Thu, 14 May 2020 at 21:12, Aaron Meurer wrote:
> >
> > > Oscar, your idea looks helpful. It would resolve my concerns, but I'm
>
ar Benjamin
wrote:
> On Thu, 14 May 2020 at 19:57, Jason Moore wrote:
> >
> > Is it possible to give a blanket deprecation warning if anyone does an
> import with a `*`? It could warn the user that functionality will change in
> the next version such that modules are not acc
Oscar Benjamin
wrote:
> On Thu, 14 May 2020 at 18:46, Jason Moore wrote:
> >
> > These all seem like good reasons to make the change. Did users get a
> deprecation cycle for the change? i.e. if I mport one of the affected
> imports in 1.5 I get a deprecation warning?
>
&g
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 *. Th
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 wit
> >
> > Thanks all for your suggestions.
> >
> >
> >
> > On Thu, May 7, 2020, 00:48 Jason Moore wrote:
> >>
> >> Gagandeep,
> >>
> >> Thanks for the consideration of my comments.
> >>
> >> Jason
> >&g
umber of contributors, then we can think of carving
> out, though at that time the situation will be very different and
> trade-offs may change.
>
> On Thu, May 7, 2020 at 12:24 AM Jason Moore wrote:
>
>> Gangandeep,
>>
>> I disagree with your thoughts on this.
rience with this
> with PyDy and the sympy.physics.mechanics packages. I don't remember
> if there was ever any major code that was moved from SymPy to PyDy or
> from PyDy to SymPy. If there was, were there any challenges in this?
>
> Aaron Meurer
>
> On Wed, May 6, 2020 at 11:40 AM Jas
Gangandeep,
I disagree with your thoughts on this. We've dealt with this over a decade
ago with the symbolic pydy package (which started as a separate package).
After careful consideration we decided to add this to SymPy and it was the
right decision. It allows the code to be tested along with Sym
Naman,
I'd have a look at the maxima package. They likely have good and useful
ideas for your design.
Jason
moorepants.info
+01 530-601-9791
On Wed, May 6, 2020 at 10:37 AM Javier Arantegui
wrote:
> Hello,
>
> it sounds interesting.
>
> What do you have in mind? Something like COMA <
> http:/
Naman,
I think we should add it to SymPy in the physics package.
Jason
moorepants.info
+01 530-601-9791
On Wed, May 6, 2020 at 8:43 AM Naman Nimmo wrote:
> Hi everyone.
>
> Since the accepted GSoC projects are out now, and my project - "Control
> Theory - Implement a control systems package"
The license they chose is open source, but it just isn't readily compatible
with OSI approved licenses.
I was recently surprised to find out that CC-BY isn't even compatible:
https://opensource.stackexchange.com/questions/9242/why-does-creative-commons-recommend-not-using-cc-by-licenses-for-softwa
docs has an easy way to make comments on proposals but I'm not sure
that is worth the lack of openness and archiving.
Jason
moorepants.info
+01 530-601-9791
On Fri, Mar 27, 2020 at 2:16 PM Jason Moore wrote:
> I don't agree that a requirement to introducing themselves should be
>
I don't agree that a requirement to introducing themselves should be
getting a PR merged. That is a barrier to community building for these new
potential contributors. My opinion is that we put far too much weight on
the PR(s) in the first place.
I like the idea of having each student opening an i
Harsha,
You've got a lot of good ideas in your proposal. Here are some quick
comments:
- The scope is way too large. You have too many different things. Bring the
scope down to a couple of things.
- Some of the items are likely not appropriate for a symbolic library.
- I like that you have code s
Vinit,
You are welcome to add more automated method that uses the Newton-Euler
approach but we wouldn't remove the automated Kane's method.
Jason
moorepants.info
+01 530-601-9791
On Wed, Mar 25, 2020 at 1:41 PM vinit wadgaonkar wrote:
> sir, i have been sending mails to mentors but didn't go
Vinit,
I recommend reading past successful proposals on the sympy wiki to get an
idea of what and how much your proposal should include. What you've written
is not sufficient.
Jason
moorepants.info
+01 530-601-9791
On Fri, Mar 13, 2020 at 10:06 AM vinit wadgaonkar
wrote:
> Since I am not gett
I'll likely be the mentor for that project if a proposal on it is accepted.
You need to follow these instructions to get started:
https://github.com/sympy/sympy/wiki/GSoC-2020-Student-Instructions
Jason
moorepants.info
+01 530-601-9791
On Mon, Mar 9, 2020 at 11:37 AM Parthesh Savla
wrote:
> G
There may be a sign convention inconsistently in the new draw() method.
Please submit and issue on github about this.
Thanks,
Jason
moorepants.info
+01 530-601-9791
On Sun, Mar 1, 2020 at 8:48 AM Alejandro Martín Hernán <
amartinher...@gmail.com> wrote:
> Hi Jashan,
>
> Thank you for your answ
Naman,
If you are excited about the control package, I think you should work on
it. It is a very nice addition that an electrical engineering student is
ideal to work on.
Don't let this broader conversation happening here discourage you. We
shouldn't have hijacked your thread.
I'm very supportiv
Historically we've been very supportive of adding well designed domain
specific packages. SymPy, in fact, was built originally with at least a
partial desire for solving symbolic physics.
There are of course advantages and disadvantages in doing this.
My personal opinion is that we limit GSoC pro
Is there an issue or email thread regarding the decision to do this? I'd
like to read the reasoning.
Thanks,
Jason
moorepants.info
+01 530-601-9791
On Fri, Jan 31, 2020 at 4:50 PM Aaron Meurer wrote:
> I have removed all old versions of the documentation from
> docs.sympy.org. docs.sympy.org
rotational kinetic energy, what if we only want to
> calculate translational kinetic energy or rotational kinetic energy.
>
> Since it is mentioned in the status of that idea that no work is done so
> far I am not sure where should I start from.
>
> I would love to hear from Jason Moore as h
Nicolás, Welcome to the mailing list!
Thank you so much for maintaining the database. We very much appreciate it.
Jason
moorepants.info
+01 530-601-9791
On Wed, Jan 29, 2020 at 6:11 AM Nicolás Guarín-Zapata
wrote:
> Hello,
>
> I am Nicolás Guarín-Zapata, PhD candidate at Purdue University. I
There are no examples of solving equations from Beam for variables other
than the reactions.
Can't you simply multiply the deflection equation by I to solve for it?
Isn't it a trivial solution if E and I are constants?
Jason
moorepants.info
+01 530-601-9791
On Tue, Jan 14, 2020 at 11:21 AM Jon
Jon,
You should be able to use SymPy's solve() function to solve for any
unknowns in the equations that Beam generates.
Jason
moorepants.info
+01 530-601-9791
On Tue, Jan 14, 2020 at 10:27 AM Jon Durand wrote:
> Duly noted. I will try to think of another way but I might not be able to.
>
> On
Using exec() is generally not a good idea. It is useful for some rare
needs, but I'd recommend avoiding it if you can.
Jason
moorepants.info
+01 530-601-9791
On Tue, Jan 14, 2020 at 9:10 AM Jon Durand wrote:
> Okay I got it working better now. The exec() function was putting it in as
> a strin
If you check the "dev" docs, those should be updated after each merged pull
request.
https://docs.sympy.org/dev/
Jason
moorepants.info
+01 530-601-9791
On Sat, Jan 11, 2020 at 2:30 PM Jaime Resano Aisa <
gemailpersona...@gmail.com> wrote:
> Oh I see that my pull request is only at master branc
You could use the qtconsole version of IPython. I think that may be what
Spyder defaults to.
Jason
moorepants.info
+01 530-601-9791
On Fri, Jan 3, 2020 at 12:13 AM Aaron Meurer wrote:
> Jupyter is what I'd generally recommend. Jypyter lab is newer than the
> notebook so I would suggest using t
d on Python 2.7 but nothing
> >> will immediately break for people who continue to use 2.7 with NumPy
> >> and/or SymPy. Those users will just be stuck with the current versions
> >> of 3rd party packages as well as an old version of the interpreter.
> >>
> &g
continue to use 2.7 with NumPy
> and/or SymPy. Those users will just be stuck with the current versions
> of 3rd party packages as well as an old version of the interpreter.
>
> On Sat, 14 Dec 2019 at 23:28, Jason Moore wrote:
> >
> > I'd like for us to hang on to Py27 un
I'd like for us to hang on to Py27 until we see what happens when NumPy
drops it. I personally feel like shit might hit the fan.
Jason
moorepants.info
+01 530-601-9791
On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer wrote:
>
>
> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin
> wrote:
>
>> Pytho
If you use conda to manage packages, it has a dependency solver and will
warn you about package clashes in environments as well as find compatible
install solutions for a set of packages. Unfortunately, pip does not have
that ability.
Jason
moorepants.info
+01 530-601-9791
On Sat, Dec 14, 2019 a
Same reason for the physics vector. It relies on mutability for
functionality.
Jason
moorepants.info
+01 530-601-9791
On Fri, Nov 29, 2019 at 4:26 PM Aaron Meurer wrote:
> MutableMatrix doesn't subclass from Basic because Basic subclasses
> have to be mutable. That's why there is an ImmutableM
Jamie,
You'll need to study the 2D class here:
https://github.com/sympy/sympy/blob/master/sympy/geometry/polygon.py and
start thinking about what a class might look like for 3D. You may have to
start by working on the core geometry classes so they can fully support 3D
geometry:
https://github.com/
The next step is getting your development environment setup:
https://github.com/sympy/sympy/wiki/Development-workflow
Jason
moorepants.info
+01 530-601-9791
On Sun, Nov 24, 2019 at 9:26 AM vikash sharma
wrote:
> Do guide me also , after selecting problem how to proceed further
>
> --
> You rec
Jamie and Mohammad,
Welcome. I recommend starting here:
https://github.com/sympy/sympy/wiki/introduction-to-contributing
Once you have gone through the tutorial, reviewed the documentation, and
open issues you can then ask more questions about how to move forward.
Jason
moorepants.info
+01 530-6
Vikash,
Welcome. I recommend starting here:
https://github.com/sympy/sympy/wiki/introduction-to-contributing
Once you have gone through the tutorial, reviewed the documentation, and
open issues you can then ask more questions about how to move forward.
Jason
moorepants.info
+01 530-601-9791
On
There are two things that I think are important:
- don't include backwards incompatible changes in releases without a
deprecation cycle (cycle should be measured in real time, not # cycles)
- don't introduce new features that we aren't confident we want to support
as public API
If we have strict
I meant xreplace().
Jason
moorepants.info
+01 530-601-9791
On Mon, Oct 28, 2019 at 8:57 AM Ashith Shyam wrote:
> Thank You Jason. Really appreciate it.
>
> Ash
>
> On Mon, Oct 28, 2019 at 3:07 PM Jason Moore wrote:
>
>> If you have an expression you can u
it will but still I need to go through
> examples and learn and develop again.
> Could you please let me know how to replace the functions of time with
> ordinary symbols. I am expecting something like q1(t) to be q[0] and d
> q1(t) /dt to be dq[0]?
>
> Ash
>
> On Mon, Oct 28,
https://github.com/pydy/pydy will do all this for you with just a few
commands.
If you want to use the code generation tools in sympy directly, it may help
to replace the functions of time with ordinary symbols.
Jason
moorepants.info
+01 530-601-9791
On Mon, Oct 28, 2019 at 4:04 AM Ash wrote:
I think that you can make the wiki page RST and it will render, that way
you want have to go form google docs > markdown > rst. FYI
Jason
moorepants.info
+01 530-601-9791
On Fri, Oct 4, 2019 at 1:37 PM Lauren Glattly
wrote:
> Thank you for the formatting suggestions! I see your point about sym
You can also replace the functions of t with symbols before pickling.
Jason
moorepants.info
+01 530-601-9791
On Wed, Aug 14, 2019 at 9:36 AM Aaron Meurer wrote:
> There are lots of issues with pickling and SymPy unfortunately.
> Functions in particular have issues because they are dynamically
very important,
> which is why a survey might help.
>
> Either way, this a great conversation to be having now!
>
>
> On Tue, Aug 13, 2019 at 2:14 PM Jason Moore wrote:
>
>> I was thinking more about Aaron's mention of measuring the documentation
>> use and st
> I don't know that for sure, so maybe there is some way we could measure
that.
This is something Lauren could do, a proper survey to solicit feedback on
docstrings/documentation from users would really help. Right now we are
just getting info from a few vocal speakers.
> Maybe our docstring stan
> I like this approach a lot.
I agree. It is a nice idea.
Jason
moorepants.info
+01 530-601-9791
On Tue, Aug 13, 2019 at 10:22 AM Ondřej Čertík wrote:
>
>
> On Tue, Aug 13, 2019, at 10:49 AM, Jason Moore wrote:
> > > I don't know that for sure, so maybe there is s
Soniya,
Welcome. If you haven't found this page yet:
https://github.com/sympy/sympy/wiki/introduction-to-contributing it is a
good place to get started. Let us know if you have any questions.
Jason
moorepants.info
+01 530-601-9791
On Tue, Aug 13, 2019 at 9:13 AM Soniya Nayak
wrote:
> Hi,
>
>
+01 530-601-9791
On Tue, Aug 13, 2019 at 10:23 AM Jason Moore wrote:
> > I like this approach a lot.
>
> I agree. It is a nice idea.
>
> Jason
> moorepants.info
> +01 530-601-9791
>
>
> On Tue, Aug 13, 2019 at 10:22 AM Ondřej Čertík wrote:
>
>>
>&g
ideal solution could be that the docstrings could be designed such that
the rendered math appears in the online docs and doesn't (or a simplified
version) appears at the command line. I don't know what the technical
solution to make that happen would be.
Jason
moorepants.info
+01 530-601-97
And the existing guide:
https://github.com/sympy/sympy/wiki/Writing-documentation (If you haven't
come across that).
Jason
moorepants.info
+01 530-601-9791
On Mon, Aug 12, 2019 at 6:37 PM Jason Moore wrote:
> One thing to start with on style, is following the numpydoc format. Here&
One thing to start with on style, is following the numpydoc format. Here's
some issues about that:
- https://github.com/sympy/sympy/issues/12710
- https://github.com/sympy/sympy/issues/15370
- https://github.com/sympy/sympy/issues/15375
- https://github.com/sympy/sympy/issues/17205
- https://githu
The Fungrim form is readable in plaintext, which is a good thing. It is
also easier to read a sympy integral than the latex too.
Jason
moorepants.info
+01 530-601-9791
On Mon, Aug 12, 2019 at 3:54 PM Ondřej Čertík wrote:
>
>
> On Mon, Aug 12, 2019, at 9:03 AM, Jason Moore wrote:
>
19 at 8:43 AM Jason Moore wrote:
> >
> > > If you're arguing against having the mathematical definitions inside
> the functions
> >
> > No where have I argued for that.
>
> If this isn't what you are suggesting then that's great. It sounded
>
> If you're arguing against having the mathematical definitions inside the
functions
No where have I argued for that.
Jason
moorepants.info
+01 530-601-9791
On Sun, Aug 11, 2019 at 10:48 AM Aaron Meurer wrote:
> On Sat, Aug 10, 2019 at 9:57 AM Jason Moore wrote:
> >
I one of the advocates of de-emphasizing complex math that requires latex
in the docsrings. When I'm programming my primary needs 1) are finding the
variable, function, or class that needs to be used and then 2)
understanding how to use that object. I am rarely concerned with the
mathematical detai
Yash,
You can start here:
https://github.com/sympy/sympy/wiki/introduction-to-contributing
Get familiar with using the software, setup your development environment,
and then look for issues to solve. Let us know if you have any questions.
Jason
moorepants.info
+01 530-601-9791
On Fri, Aug 9, 2
101 - 200 of 1091 matches
Mail list logo
