Hi, I'm beginning to work on a proposal for this project, and I just had a question about how I should approach it. Using a parser generator would probably make it easier to create a parser, but may introduce an external dependency. Would this be discouraged? Should I aim for everything to be custom-written and kept within SymPy?
I also reached out to the creator of latex2sympy to see if he's still planning to add it to SymPy. If not, I'll probably try to find a way to work LaTeX parsing into my proposal as well, since it would be quite useful. My question about introducing an external dependency would need to be discussed with regards to latex2sympy as well, since that uses a parser generator. Thanks, Jerry On Monday, February 29, 2016 at 8:47:27 PM UTC-5, Anthony Scopatz wrote: > > This would be great to have, though! > > On Mon, Feb 29, 2016 at 8:44 PM Jason Moore <[email protected] > <javascript:>> wrote: > >> Jerry, >> >> As far as I know there is no work to get that latex2sympy parser into >> sympy or coordinate anything further than what was said in that issue. It >> would be worth contacting the author. >> >> Jason >> >> >> Jason >> moorepants.info >> +01 530-601-9791 >> >> On Mon, Feb 29, 2016 at 5:12 PM, Jerry Li <[email protected] <javascript:> >> > wrote: >> >>> Hi, >>> >>> I'm currently a first-year undergraduate Engineering student at the >>> University of Toronto who is fairly experienced with Python, and I'm >>> interested in contributing to SymPy for GSOC 2016. After familiarizing >>> myself with the basics of SymPy and reading through GSOC Ideas page, I was >>> drawn to the idea of improving SymPy Gamma/Live's language recognition so >>> that it could interpret natural English and text-based math, like Wolfram >>> Alpha. I understand that the best way of doing this would be to include the >>> functionality in the SymPy library itself so that it could be called from >>> SymPy Gamma/Live. >>> >>> I've read through the Parsing page in the SymPy wiki >>> <https://github.com/sympy/sympy/wiki/Parsing>, as well as some related >>> threads in this mailing list. The thread linked on the wiki especially >>> seems to include lots of informative discussion, but not much of it was >>> followed up upon. I've been doing some preliminary research, and I believe >>> that, with time and a lot of learning, it should be within my scope to >>> implement a parser that would work for most common English/text inputs and >>> include some informative error messages to help the user. This perhaps >>> could involve using adapted code from external libraries and a parser >>> generator. I'd be willing to put a lot of time into learning new skills to >>> get the project done. >>> >>> I believe that this functionality could improve the user experience of >>> SymPy Live/Gamma, which would help people out and draw more attention/users >>> to SymPy. I was also interested in implementing a LaTeX parser, but it >>> seems like there's some work in progress in that area. >>> <https://github.com/augustt198/latex2sympy/issues/1> >>> >>> Anyways, I was mostly wondering if anyone had input on whether or not >>> this would be a suitable project to pursue for GSoC, and if there were any >>> suggestions on recommended approaches. If so, I'll do some more research >>> and start drafting up a proposal. If not, I'll look into other potential >>> things to contribute in for SymPy. In terms of the patch requirement for >>> GSoC, I've submitted one bug fix pull request which was merged so far, and >>> will be looking for more opportunities to do so in the next few weeks. >>> >>> Thanks, >>> Jerry >>> >>> -- >>> 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 [email protected] <javascript:>. >>> To post to this group, send email to [email protected] >>> <javascript:>. >>> Visit this group at https://groups.google.com/group/sympy. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/sympy/02716b63-2833-47d8-95ce-3fc6411615c8%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/sympy/02716b63-2833-47d8-95ce-3fc6411615c8%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] <javascript:> >> . >> Visit this group at https://groups.google.com/group/sympy. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/sympy/CAP7f1AjXNW4QXPV8NPVG_JjRwch2idm1CoQJo-A9KnYN%3Dpv6yQ%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/sympy/CAP7f1AjXNW4QXPV8NPVG_JjRwch2idm1CoQJo-A9KnYN%3Dpv6yQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > > Asst. Prof. Anthony Scopatz > Nuclear Engineering Program > Mechanical Engineering Dept. > University of South Carolina > Affiliated Professor of the University of Haifa > [email protected] <javascript:> > Office: (803) 777-7629 > Cell: (512) 827-8239 > Check my calendar > <https://www.google.com/calendar/embed?src=scopatz%40gmail.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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/8baaf0e5-ffe9-4d1c-89fa-05b9306af903%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
