Dear all,

I have submitted a Pull Request with the notebook and some restructuring of 
the repo.

Regarding the discussion on keeping notebooks up to date what about using 
something similar to NumPy Tutorials 
(https://numpy.org/numpy-tutorials/content/tutorial-style-guide.html)? They 
suggest to pair notebooks with  MyST-NB.



On Wednesday, May 5, 2021 at 3:53:19 AM UTC-5 asme...@gmail.com wrote:

> Jupyter notebooks are just JSON files so you can examine what metadata
> is stored in them by opening them in your text editor. I'm guessing
> neither of these things is a concern since a lot of people use
> notebooks and I have never heard anyone complain about either issue.
>
> Aaron Meurer
>
> On Wed, May 5, 2021 at 2:25 AM S.Y. Lee <syle...@gmail.com> wrote:
> >
> > I have attempted attempt to submit pull requests at sympy_notebooks 
> repository at least to move stuff outside of sympy main repo,
> > but one of the concerns I have is whether the notebook files can store 
> some personal information (Like the creation datetime, user account, some 
> local PC folder structure),
> > or whether the notebooks made in Windows having CRLF is a problem for 
> other operating systems.
> > I'm not sure if these problems are really a matter or not, but I would 
> need more clear investigation for the structure of jupyter notebooks
> > such that we can normalize some of the sensitive or unnecessary data 
> stored in the notebook.
> >
> > On Friday, April 16, 2021 at 3:07:19 AM UTC+9 asme...@gmail.com wrote:
> >>
> >> I think notebooks in general should be in a separate repo. This will
> >> make it easier to include many notebooks, and to include them with
> >> outputs included, without having to worry about them increasing the
> >> size of the main repo.
> >>
> >> Aaron Meurer
> >>
> >> On Thu, Apr 15, 2021 at 11:27 AM Nicolas Guarin <nicog...@gmail.com> 
> wrote:
> >> >
> >> > So, the main idea is to keep it in the main repo or migrate it to the 
> notebooks' one?
> >> >
> >> > I think that we the bare minimum is to test that the notebooks run 
> without errors within CI.
> >> >
> >> > On Thursday, April 8, 2021 at 3:52:59 AM UTC-5 moore...@gmail.com 
> wrote:
> >> >>
> >> >> Some CI to ensure the notebooks run is rather important, otherwise 
> we'll end up with a bunch of broken notebooks over time.
> >> >>
> >> >> That's what happened with the pydy/examples folder. Lots of stuff 
> was dumped in there over the years, but no CI to double check it actually 
> runs. Setting up at least CI in the sympy-notebooks repo would make it a 
> relevant, sustained, and useful resource.
> >> >>
> >> >> Jason
> >> >> moorepants.info
> >> >> +01 530-601-9791 <(530)%20601-9791>
> >> >>
> >> >>
> >> >> On Thu, Apr 8, 2021 at 10:27 AM Aaron Meurer <asme...@gmail.com> 
> wrote:
> >> >>>
> >> >>> One of the benefits of having sympy-notebooks as a separate 
> repository
> >> >>> is that we don't necessarily need to worry about those things. I 
> would
> >> >>> be in favor of just merging things into sympy-notebooks as long as
> >> >>> they look OK. We don't need to apply the same standards as the main
> >> >>> repo, or at least that shouldn't block things being merged 
> presently..
> >> >>>
> >> >>> Aaron Meurer
> >> >>>
> >> >>> On Thu, Apr 8, 2021 at 1:10 AM S.Y. Lee <syle...@gmail.com> wrote:
> >> >>> >
> >> >>> > I don't think that we can utilize sympy-notebooks repository 
> properly unless we figure out how to test out the notebook outputs, 
> integrate with sympy releases, matching version compatibility, and link 
> with documentations.
> >> >>> > Setting up this workflow is important, and once this workflow is 
> set, I think that we should have a place to allow many people to 
> collaborate tutorials.
> >> >>> > On Wednesday, April 7, 2021 at 6:02:03 AM UTC+9 
> nicog...@gmail.com wrote:
> >> >>> >>
> >> >>> >> > If anyone wants to take on the work of improving the 
> sympy-notebooks
> >> >>> >> repo or adding notebooks to it, please do so.
> >> >>> >>
> >> >>> >> I started this with the notebook that I mentioned before. I also 
> created a CSS
> >> >>> >> style file.
> >> >>> >>
> >> >>> >> You can check the static version here: 
> https://nbviewer.jupyter.org/github/nicoguaro/sympy-notebooks/blob/master/beginner/sympy_in_10_minutes.ipynb
> >> >>> >>
> >> >>> >> And the Binder version here: 
> https://mybinder.org/v2/gh/nicoguaro/sympy-notebooks/HEAD?filepath=beginner%2Fsympy_in_10_minutes.ipynb
> >> >>> >>
> >> >>> >> Right now the updated version is in my fork, but I could make a 
> PR and start adding the other
> >> >>> >> notebooks mentioned in the thread.
> >> >>> >>
> >> >>> >> Nicolás
> >> >>> >>
> >> >>> >> On Thursday, July 2, 2020 at 2:55:52 PM UTC-5 asme...@gmail.com 
> wrote:
> >> >>> >>>
> >> >>> >>> There's also https://github.com/sympy/quantum_notebooks. Those 
> should
> >> >>> >>> perhaps be moved to the sympy-notebooks repo so that we have
> >> >>> >>> everything in one place.
> >> >>> >>>
> >> >>> >>> We might also consider moving the example notebooks in the 
> sympy repo
> >> >>> >>> over to sympy-notebooks. That would let us include the outputs 
> as I
> >> >>> >>> described, and to have them in a more standard place. We can 
> also set
> >> >>> >>> up CI on that repo so that the outputs are tested. I had 
> thought that
> >> >>> >>> the example notebooks were included with the release tarball, 
> but
> >> >>> >>> apparently they are not, so there is not a big issue with 
> moving them,
> >> >>> >>> I think.
> >> >>> >>>
> >> >>> >>> If anyone wants to take on the work of improving the 
> sympy-notebooks
> >> >>> >>> repo or adding notebooks to it, please do so.
> >> >>> >>>
> >> >>> >>> Aaron Meurer
> >> >>> >>>
> >> >>> >>> On Thu, Jul 2, 2020 at 1:14 PM Aaron Meurer <asme...@gmail.com> 
> wrote:
> >> >>> >>> >
> >> >>> >>> > We also have https://github.com/sympy/sympy-notebooks, which 
> has never
> >> >>> >>> > really been used, but it would be nice to set it up as an 
> example repo
> >> >>> >>> > with notebooks, a binder link, and so on. Having it in a 
> separate repo
> >> >>> >>> > also means we can have notebooks that have the outputs 
> included
> >> >>> >>> > without having to worry about taking up a bunch of space in 
> the main
> >> >>> >>> > repo.
> >> >>> >>> >
> >> >>> >>> > Aaron Meurer
> >> >>> >>> >
> >> >>> >>> > On Wed, Jul 1, 2020 at 3:23 AM Oscar Benjamin
> >> >>> >>> > <oscar.j....@gmail.com> wrote:
> >> >>> >>> > >
> >> >>> >>> > > Hi Nicolás,
> >> >>> >>> > >
> >> >>> >>> > > This looks nice. Maybe it should go in the example 
> notebooks:
> >> >>> >>> > > 
> https://github.com/sympy/sympy/tree/master/examples/notebooks
> >> >>> >>> > >
> >> >>> >>> > > I don't know if those are hosted on the website rather than 
> just github.
> >> >>> >>> > >
> >> >>> >>> > > Oscar
> >> >>> >>> > >
> >> >>> >>> > > On Tue, 30 Jun 2020 at 22:11, Nicolas Guarin <
> nicog...@gmail.com> wrote:
> >> >>> >>> > > >
> >> >>> >>> > > > I adapted Maxima's tutorial "Maxima in 10 minutes" to 
> SymPy for one of my courses. I would like to know if you consider useful to 
> share it somewhere. This is an nbviewer link:
> >> >>> >>> > > >
> >> >>> >>> > > > 
> https://nbviewer.jupyter.org/github/nicoguaro/AdvancedMath/blob/master/notebooks/sympy/sympy_in_10_minutes.ipynb
> >> >>> >>> > > >
> >> >>> >>> > > > Best,
> >> >>> >>> > > > Nicolás
> >> >>> >>> > > >
> >> >>> >>> > > > --
> >> >>> >>> > > > You received this message because you are subscribed to 
> the Google Groups "sympy" group.
> >> >>> >>> > > > To unsubscribe from this group and stop receiving emails 
> from it, send an email to sympy+un...@googlegroups.com.
> >> >>> >>> > > > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/6a311d80-b7f6-4f70-a601-091e7b3a3aa5o%40googlegroups.com
> .
> >> >>> >>> > >
> >> >>> >>> > > --
> >> >>> >>> > > You received this message because you are subscribed to the 
> Google Groups "sympy" group.
> >> >>> >>> > > To unsubscribe from this group and stop receiving emails 
> from it, send an email to sympy+un...@googlegroups.com.
> >> >>> >>> > > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/CAHVvXxT808Gp0yWFrmZwPgneETJC%2BSo57aAi1x2cc4SpEiR6-Q%40mail.gmail.com
> .
> >> >>> >
> >> >>> > --
> >> >>> > You received this message because you are subscribed to the 
> Google Groups "sympy" group.
> >> >>> > To unsubscribe from this group and stop receiving emails from it, 
> send an email to sympy+un...@googlegroups.com.
> >> >>> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/514d6e1d-e270-4dff-979b-b1e6effc4296n%40googlegroups.com
> .
> >> >>>
> >> >>> --
> >> >>> You received this message because you are subscribed to the Google 
> Groups "sympy" group.
> >> >>> To unsubscribe from this group and stop receiving emails from it, 
> send an email to sympy+un...@googlegroups.com.
> >> >>>
> >> >>> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/CAKgW%3D6JwP%3Dm3Kc0DGhx7uf__0oQJ9Y8toeSqhwkX2V-aTvXFqA%40mail.gmail.com
> .
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google 
> Groups "sympy" group.
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send an email to sympy+un...@googlegroups.com.
> >> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/c497fc2b-9a7c-4569-8ed7-d3bc63807e20n%40googlegroups.com
> .
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "sympy" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sympy+un...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/31118ed7-f234-4c3f-98ed-3efb52282ae0n%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/fb00c60d-ca4b-41af-88cd-ad318ed518den%40googlegroups.com.

Reply via email to