[sage-devel] Re: Outdated instructions in "git the hard way"
Also the title of that section, "Git the hard way", should be changed. It should rather be "Git the *standard* way" IMHO. Eric. Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : > On: > > https://doc.sagemath.org/html/en/developer/manual_git.html > > it is suggested to start with > > git clone https://gitlab.com/sagemath/dev/tracmirror.git > > however, the gitlab mirror is stuck at 9.3. The github mirror tracks the > development tree much better. Shouldn't we be pointing people to that > instead? Or perhaps straight to trac.sagemath.org ? > > Incidentally, on FC 33 and FC 34, the default settings are pretty strict > for cryptographic signatures, and "ssh g...@trac.sagemath.org info" fails > as a result. A way of making FC >=33 more accepting of outdated signature > schemes is by: > > sudo update-crypto-policies --set LEGACY > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/05352b6c-98d4-48fa-a6c1-7324dad0d9a8n%40googlegroups.com.
Re: [sage-devel] Re: Outdated instructions in "git the hard way"
+1 : Learning git is a useful skill. And a developer is likely to know git already. Le 09/09/2021 à 09:49, Eric Gourgoulhon a écrit : Also the title of that section, "Git the hard way", should be changed. It should rather be "Git the *standard* way" IMHO. Eric. Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : On: https://doc.sagemath.org/html/en/developer/manual_git.html it is suggested to start with git clone https://gitlab.com/sagemath/dev/tracmirror.git however, the gitlab mirror is stuck at 9.3. The github mirror tracks the development tree much better. Shouldn't we be pointing people to that instead? Or perhaps straight to trac.sagemath.org ? Incidentally, on FC 33 and FC 34, the default settings are pretty strict for cryptographic signatures, and "ssh g...@trac.sagemath.org info" fails as a result. A way of making FC >=33 more accepting of outdated signature schemes is by: sudo update-crypto-policies --set LEGACY -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/510102cf-26fc-f834-4d6c-d5865a1e5b8b%40gmail.com.
Re: [sage-devel] Re: Outdated instructions in "git the hard way"
I think that 'git trac' is mainly used by the release manager - I won't recommend it to newcomers. On Thu, Sep 9, 2021 at 9:36 AM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > +1 : Learning git is a useful skill. And a developer is likely to > know git already. > > Le 09/09/2021 à 09:49, Eric Gourgoulhon a écrit : > > Also the title of that section, "Git the hard way", should be changed. It > > should rather be "Git the *standard* way" IMHO. > > > > Eric. > > > > > > > > > > Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : > > > >> On: > >> > >> https://doc.sagemath.org/html/en/developer/manual_git.html > >> > >> it is suggested to start with > >> > >> git clone https://gitlab.com/sagemath/dev/tracmirror.git > >> > >> however, the gitlab mirror is stuck at 9.3. The github mirror tracks the > >> development tree much better. Shouldn't we be pointing people to that > >> instead? Or perhaps straight to trac.sagemath.org ? > >> > >> Incidentally, on FC 33 and FC 34, the default settings are pretty strict > >> for cryptographic signatures, and "ssh g...@trac.sagemath.org info" fails > >> as a result. A way of making FC >=33 more accepting of outdated signature > >> schemes is by: > >> > >> sudo update-crypto-policies --set LEGACY > >> > > > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/510102cf-26fc-f834-4d6c-d5865a1e5b8b%40gmail.com. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq0cD7eUpHYWGfomYyzW3JKN2p9dyVoMsjtGpOy03VYgHQ%40mail.gmail.com.
Re: [sage-devel] Re: Outdated instructions in "git the hard way"
Actually, I use "git trac" a lot. Mainly "git trac try", "git trac pull" and "git trac create". I find it very convenient to only pass the trac ticket number. Martin dim...@gmail.com schrieb am Donnerstag, 9. September 2021 um 10:43:58 UTC+2: > I think that 'git trac' is mainly used by the release manager - I > won't recommend it to newcomers. > > > On Thu, Sep 9, 2021 at 9:36 AM Vincent Delecroix > <20100.d...@gmail.com> wrote: > > > > +1 : Learning git is a useful skill. And a developer is likely to > > know git already. > > > > Le 09/09/2021 à 09:49, Eric Gourgoulhon a écrit : > > > Also the title of that section, "Git the hard way", should be changed. > It > > > should rather be "Git the *standard* way" IMHO. > > > > > > Eric. > > > > > > > > > > > > > > > Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : > > > > > >> On: > > >> > > >> https://doc.sagemath.org/html/en/developer/manual_git.html > > >> > > >> it is suggested to start with > > >> > > >> git clone https://gitlab.com/sagemath/dev/tracmirror.git > > >> > > >> however, the gitlab mirror is stuck at 9.3. The github mirror tracks > the > > >> development tree much better. Shouldn't we be pointing people to that > > >> instead? Or perhaps straight to trac.sagemath.org ? > > >> > > >> Incidentally, on FC 33 and FC 34, the default settings are pretty > strict > > >> for cryptographic signatures, and "ssh g...@trac.sagemath.org info" > fails > > >> as a result. A way of making FC >=33 more accepting of outdated > signature > > >> schemes is by: > > >> > > >> sudo update-crypto-policies --set LEGACY > > >> > > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-devel+...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/510102cf-26fc-f834-4d6c-d5865a1e5b8b%40gmail.com > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/4eb2c412-2234-495f-a4b9-0e552a968eebn%40googlegroups.com.
Re: [sage-devel] Re: Outdated instructions in "git the hard way"
Hi, On Thu, Sep 09, 2021 at 03:04:37AM -0700, 'Martin R' via sage-devel wrote: > Actually, I use "git trac" a lot. Mainly "git trac try", "git trac pull" > and "git trac create". I find it very convenient to only pass the trac > ticket number. I use it a lot too. Let me also mention "git trac find" which, combined to "git blame" allows you to discover which ticket introduced some feature or bug, then you can add the participants in CC of a ticket corresponding to that feature or bug. Ciao, Thierry > Martin > > dim...@gmail.com schrieb am Donnerstag, 9. September 2021 um 10:43:58 UTC+2: > > > I think that 'git trac' is mainly used by the release manager - I > > won't recommend it to newcomers. > > > > > > On Thu, Sep 9, 2021 at 9:36 AM Vincent Delecroix > > <20100.d...@gmail.com> wrote: > > > > > > +1 : Learning git is a useful skill. And a developer is likely to > > > know git already. > > > > > > Le 09/09/2021 à 09:49, Eric Gourgoulhon a écrit : > > > > Also the title of that section, "Git the hard way", should be changed. > > It > > > > should rather be "Git the *standard* way" IMHO. > > > > > > > > Eric. > > > > > > > > > > > > > > > > > > > > Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : > > > > > > > >> On: > > > >> > > > >> https://doc.sagemath.org/html/en/developer/manual_git.html > > > >> > > > >> it is suggested to start with > > > >> > > > >> git clone https://gitlab.com/sagemath/dev/tracmirror.git > > > >> > > > >> however, the gitlab mirror is stuck at 9.3. The github mirror tracks > > the > > > >> development tree much better. Shouldn't we be pointing people to that > > > >> instead? Or perhaps straight to trac.sagemath.org ? > > > >> > > > >> Incidentally, on FC 33 and FC 34, the default settings are pretty > > strict > > > >> for cryptographic signatures, and "ssh g...@trac.sagemath.org info" > > fails > > > >> as a result. A way of making FC >=33 more accepting of outdated > > signature > > > >> schemes is by: > > > >> > > > >> sudo update-crypto-policies --set LEGACY > > > >> > > > > > > > > > > -- > > > You received this message because you are subscribed to the Google > > Groups "sage-devel" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > an email to sage-devel+...@googlegroups.com. > > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/sage-devel/510102cf-26fc-f834-4d6c-d5865a1e5b8b%40gmail.com > > . > > > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/4eb2c412-2234-495f-a4b9-0e552a968eebn%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/20210909142353.GA29967%40metelu.net.
Re: [sage-devel] Re: Outdated instructions in "git the hard way"
I use git-trac all the time, but I do agree that it is better for the developer's manual to begin with standard git instructions and only describe git-trac as an optional convenience tool. We should avoid the impression that project-specific special tooling is required if people want to contribute to the project. Matthias On Thursday, September 9, 2021 at 1:43:58 AM UTC-7 Dima Pasechnik wrote: > I think that 'git trac' is mainly used by the release manager - I > won't recommend it to newcomers. > > > On Thu, Sep 9, 2021 at 9:36 AM Vincent Delecroix > <20100.d...@gmail.com> wrote: > > > > +1 : Learning git is a useful skill. And a developer is likely to > > know git already. > > > > Le 09/09/2021 à 09:49, Eric Gourgoulhon a écrit : > > > Also the title of that section, "Git the hard way", should be changed. > It > > > should rather be "Git the *standard* way" IMHO. > > > > > > Eric. > > > > > > > > > > > > > > > Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : > > > > > >> On: > > >> > > >> https://doc.sagemath.org/html/en/developer/manual_git.html > > >> > > >> it is suggested to start with > > >> > > >> git clone https://gitlab.com/sagemath/dev/tracmirror.git > > >> > > >> however, the gitlab mirror is stuck at 9.3. The github mirror tracks > the > > >> development tree much better. Shouldn't we be pointing people to that > > >> instead? Or perhaps straight to trac.sagemath.org ? > > >> > > >> Incidentally, on FC 33 and FC 34, the default settings are pretty > strict > > >> for cryptographic signatures, and "ssh g...@trac.sagemath.org info" > fails > > >> as a result. A way of making FC >=33 more accepting of outdated > signature > > >> schemes is by: > > >> > > >> sudo update-crypto-policies --set LEGACY > > >> > > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-devel+...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/510102cf-26fc-f834-4d6c-d5865a1e5b8b%40gmail.com > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/2817e314-bea1-47c0-8814-0d7f6f26b86en%40googlegroups.com.
Re: [sage-devel] Re: Outdated instructions in "git the hard way"
On Thu, Sep 9, 2021 at 4:00 PM Matthias Koeppe wrote: > > I use git-trac all the time, but I do agree that it is better for the > developer's manual to begin with standard git instructions and only describe > git-trac as an optional convenience tool. > We should avoid the impression that project-specific special tooling is > required if people want to contribute to the project. Indeed. Also, we regularly get messages asking for help with "git trac", and the only way is usually to use "normal" git to fix these. Also a brief explanation of that "git trac" magic does in terms of plain git should be helpful. Dima > > Matthias > > On Thursday, September 9, 2021 at 1:43:58 AM UTC-7 Dima Pasechnik wrote: >> >> I think that 'git trac' is mainly used by the release manager - I >> won't recommend it to newcomers. >> >> >> On Thu, Sep 9, 2021 at 9:36 AM Vincent Delecroix >> <20100.d...@gmail.com> wrote: >> > >> > +1 : Learning git is a useful skill. And a developer is likely to >> > know git already. >> > >> > Le 09/09/2021 à 09:49, Eric Gourgoulhon a écrit : >> > > Also the title of that section, "Git the hard way", should be changed. It >> > > should rather be "Git the *standard* way" IMHO. >> > > >> > > Eric. >> > > >> > > >> > > >> > > >> > > Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : >> > > >> > >> On: >> > >> >> > >> https://doc.sagemath.org/html/en/developer/manual_git.html >> > >> >> > >> it is suggested to start with >> > >> >> > >> git clone https://gitlab.com/sagemath/dev/tracmirror.git >> > >> >> > >> however, the gitlab mirror is stuck at 9.3. The github mirror tracks the >> > >> development tree much better. Shouldn't we be pointing people to that >> > >> instead? Or perhaps straight to trac.sagemath.org ? >> > >> >> > >> Incidentally, on FC 33 and FC 34, the default settings are pretty strict >> > >> for cryptographic signatures, and "ssh g...@trac.sagemath.org info" >> > >> fails >> > >> as a result. A way of making FC >=33 more accepting of outdated >> > >> signature >> > >> schemes is by: >> > >> >> > >> sudo update-crypto-policies --set LEGACY >> > >> >> > > >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "sage-devel" group. >> > To unsubscribe from this group and stop receiving emails from it, send an >> > email to sage-devel+...@googlegroups.com. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/sage-devel/510102cf-26fc-f834-4d6c-d5865a1e5b8b%40gmail.com. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/2817e314-bea1-47c0-8814-0d7f6f26b86en%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq3Dh_Cp_3xQ00dbOsmBtzqExYfqYYV65QoCenAnRB2Gcw%40mail.gmail.com.
Re: [sage-devel] Re: Interface to Mathics
Wow, that's a fantastic email and great work that you're doing! If you haven't already, maybe you could turn this email into a "Status" link on the mathics website, since it's really good. -- William On Thu, Sep 9, 2021 at 4:17 AM Rocky Bernstein wrote: > > In the past year we have: > > Upgraded all packages and libraries that Mathics depends on > Broken up what was one single repository into several git repositories and > installable Python libraries/packages > Expanded and strengthened each of these components > Added about 150 Mathematica Built-in Functions, and enhanced or fixed bugs in > about 60 existing Built-in Functions > Expanded and Improved interactive online and printed documentation > Added a package for Networks and Graphs via networkx > Greatly expanded the command-line utility > Provide an up-to-date docker images for major releases which contains all of > the components and add-ons, and even the most recent LaTeX PDF (with a > program to read it) > Fixed numerous bugs and enhanced performance > > > This is the one minute summary. However in my opinion this doesn't do justice > to the huge amount of work behind some of these. So if you have more than a > minute here > is an elaboration of some of the bullet items above: > > Updated versions of software: > > Python: from 2.7 to 3.x up to 3.9 > Django from 1.6 .10 to 3.2.6 > MathJax 2.0 to 2.7.9 > three.js r49 to r132 > mpmath 0.17 to 1.2.1 > Sympy 0.7.3 to 1.8 > > > Significant split-off or new packages/repositories: > > mathics-scanner - extensive tables of Mathematica symbols and their > properties, also includes a scanner for Mathematica > mathics-pygments - lexer and highlighter using the pygments engine based on > rsmenon's pygments-mathematica. This uses the scanner tables above. > mathicsscript - command-line utility using the above and prompt toolkit which > has enhanced syntax coloring, command-completion and can display 2D and 3D > graphics (via matplotlib for 2D and asymptote for 3D) > mathics-threejs-backend - An implementation of Mathematica Graphics3D using > three.js > mathics-django - the Django-based Web front-end using the above minus > mathicsscript > pymathics-graph - Mathics Graph add-on functions using NetworkX and > Matplotlib > pymathics-natlang - Mathics Natural-Language Processing add-on > mathics-omnibus - a repository to bind them all into a single PyPI package > and provides the docker scripts that make up the mathics docker image. > mathics-development-guide - Sphinx documentation for developing Mathics. > Browsable developer docs are here. > > It is hoped that a number of the above can and will be used outside of > Mathics. Those of note are the Mathematica tables and scanner > mathics-scanner, the Graphics3D implementation in three.js, > mathics-threejs-backend, and the syntax highlighter mathics-pygments. In > fact, Symja which is interesting of its own right, uses or consults some of > these. > > And here, I should also mention that we are always looking for ways to > collaborate with Sage or other open-source projects. > > Although what we have now is pretty impressive (and I am amazed we have > gotten this far), we should not give the impression that Mathics is anywhere > complete. > > Here is what we are working on and what I hope to see accomplished over the > next year: > > Speeding up performance in the Mathics interpreter - we are working on this > right now. > FindMinimum - it was started but is not complete > Speeding up loading time - this is harder and can only come after the above > Being able to run more large Mathematica packages out of the box. Right now > we can handle Steven Skiena's Combinatorica v0.9. We would like to see, Rubi > and KnotTheory at least added to this. If you have suggestions and are > willing to help out contact us. Right now we are finding the performance the > biggest obstacle here. > Setting up some sort of registry of Mathematica packages that work on Mathics > Supporting Backward compatibility of older Mathematica versions > Jupyter integration. Right now the main obstacle is cleaning up the API > interaction between Mathics core and front ends > > We could use lots of help in just about every aspect. Please help out! If you > are not a Python programmer, that's okay. Here are some areas outside of > Python programming where you could help: > > Mathematica Programmers: Add missing Built in Function or functions which > bridge compatibility between Mathematica versions > Mathematicians: Make our online and printed documentation more usable and > informative. Find better examples for the functions, or describe the > functions better. > Literary types: Write or adapt your Mathematica Tutorial. As above, improve > our user (or developer) documentation > Asymptote and LaTeX gurus: our Asymptote library especially needs work. > > And of course if you are a Python programmer, especially with a facility for > Sympy, numpy, mpm
Re: [sage-devel] Re: Interface to Mathics
Thanks for the kind words and feedback. I'll add a section for Status over the weekend. We've been mostly crisis driven, so when it comes to stuff like this it just hasn't bubbled up. Also needed are updated screenshots and animated GIFs - things often look a little better than what's currently shown there. On Thursday, September 9, 2021 at 12:02:26 PM UTC-4 wst...@gmail.com wrote: > Wow, that's a fantastic email and great work that you're doing! > > If you haven't already, maybe you could turn this email into a > "Status" link on the mathics website, since it's really good. > > -- William > > On Thu, Sep 9, 2021 at 4:17 AM Rocky Bernstein > wrote: > > > > In the past year we have: > > > > Upgraded all packages and libraries that Mathics depends on > > Broken up what was one single repository into several git repositories > and installable Python libraries/packages > > Expanded and strengthened each of these components > > Added about 150 Mathematica Built-in Functions, and enhanced or fixed > bugs in about 60 existing Built-in Functions > > Expanded and Improved interactive online and printed documentation > > Added a package for Networks and Graphs via networkx > > Greatly expanded the command-line utility > > Provide an up-to-date docker images for major releases which contains > all of the components and add-ons, and even the most recent LaTeX PDF (with > a program to read it) > > Fixed numerous bugs and enhanced performance > > > > > > This is the one minute summary. However in my opinion this doesn't do > justice to the huge amount of work behind some of these. So if you have > more than a minute here > > is an elaboration of some of the bullet items above: > > > > Updated versions of software: > > > > Python: from 2.7 to 3.x up to 3.9 > > Django from 1.6 .10 to 3.2.6 > > MathJax 2.0 to 2.7.9 > > three.js r49 to r132 > > mpmath 0.17 to 1.2.1 > > Sympy 0.7.3 to 1.8 > > > > > > Significant split-off or new packages/repositories: > > > > mathics-scanner - extensive tables of Mathematica symbols and their > properties, also includes a scanner for Mathematica > > mathics-pygments - lexer and highlighter using the pygments engine based > on rsmenon's pygments-mathematica. This uses the scanner tables above. > > mathicsscript - command-line utility using the above and prompt toolkit > which has enhanced syntax coloring, command-completion and can display 2D > and 3D graphics (via matplotlib for 2D and asymptote for 3D) > > mathics-threejs-backend - An implementation of Mathematica Graphics3D > using three.js > > mathics-django - the Django-based Web front-end using the above minus > mathicsscript > > pymathics-graph - Mathics Graph add-on functions using NetworkX and > Matplotlib > > pymathics-natlang - Mathics Natural-Language Processing add-on > > mathics-omnibus - a repository to bind them all into a single PyPI > package and provides the docker scripts that make up the mathics docker > image. > > mathics-development-guide - Sphinx documentation for developing Mathics. > Browsable developer docs are here. > > > > It is hoped that a number of the above can and will be used outside of > Mathics. Those of note are the Mathematica tables and scanner > mathics-scanner, the Graphics3D implementation in three.js, > mathics-threejs-backend, and the syntax highlighter mathics-pygments. In > fact, Symja which is interesting of its own right, uses or consults some of > these. > > > > And here, I should also mention that we are always looking for ways to > collaborate with Sage or other open-source projects. > > > > Although what we have now is pretty impressive (and I am amazed we have > gotten this far), we should not give the impression that Mathics is > anywhere complete. > > > > Here is what we are working on and what I hope to see accomplished over > the next year: > > > > Speeding up performance in the Mathics interpreter - we are working on > this right now. > > FindMinimum - it was started but is not complete > > Speeding up loading time - this is harder and can only come after the > above > > Being able to run more large Mathematica packages out of the box. Right > now we can handle Steven Skiena's Combinatorica v0.9. We would like to see, > Rubi and KnotTheory at least added to this. If you have suggestions and are > willing to help out contact us. Right now we are finding the performance > the biggest obstacle here. > > Setting up some sort of registry of Mathematica packages that work on > Mathics > > Supporting Backward compatibility of older Mathematica versions > > Jupyter integration. Right now the main obstacle is cleaning up the API > interaction between Mathics core and front ends > > > > We could use lots of help in just about every aspect. Please help out! > If you are not a Python programmer, that's okay. Here are some areas > outside of Python programming where you could help: > > > > Mathematica Programmers: Add missing Built in Function or functi
