Re: [sympy] Introduction and Idea for GSOC 2020 (Parsing)

[Souvik Mandal]

Thanks Nikhil. I will submit my research in proposal format in few days and 
will work on a patch as soon as possible.

-- 
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/65d61320-8356-4c6c-8479-c59b1e74cb32%40googlegroups.com.

Re: [sympy] Re: [Discussion] GSoC 2020: Improving and extending ODE

[Oscar Benjamin]

There are possibilities to go from nonlinear to linear e.g.:

In [6]: x, y = symbols('x, y', cls=Function)

In [7]: eqs = [x(t).diff(t)**2 - y(t)**2, y(t).diff(t)**2 - x(t)**2]

In [8]: eqs
Out[8]:
⎡2  2⎤
⎢   2  ⎛d   ⎞  2  ⎛d   ⎞ ⎥
⎢- y (t) + ⎜──(x(t))⎟ , - x (t) + ⎜──(y(t))⎟ ⎥
⎣  ⎝dt  ⎠ ⎝dt  ⎠ ⎦

In [9]: solve(eqs, [x(t).diff(t), y(t).diff(t)], dict=True)
Out[9]:
⎡⎧dd  ⎫  ⎧dd ⎫
 ⎧d   d  ⎫  ⎧d   d ⎫⎤
⎢⎨──(x(t)): -y(t), ──(y(t)): -x(t)⎬, ⎨──(x(t)): -y(t), ──(y(t)):
x(t)⎬, ⎨──(x(t)): y(t), ──(y(t)): -x(t)⎬, ⎨──(x(t)): y(t), ──(y(t)):
x(t)⎬⎥
⎣⎩dt   dt ⎭  ⎩dt   dt⎭
 ⎩dt  dt ⎭  ⎩dt  dt⎭⎦

On Mon, 16 Mar 2020 at 15:48, Milan Jolly  wrote:
>
> Thanks for the suggestion, I have started with the design for these solvers. 
> But I have one doubt, namely since now we are using linear_eq_to_matrix 
> function to check if the system of ODEs is linear or not, would we require 
> the canonical rearrangements part? Or rather are there other cases when we 
> can reduce non-linear ODEs into linear ODEs.
>
> On Monday, March 16, 2020 at 2:53:57 AM UTC+5:30, Oscar wrote:
>>
>> That seems reasonable to me. Since the plan is a total rewrite I think
>> that it would be good to put some time in at the beginning for
>> designing how all of these pieces would fit together. For example even
>> if the connected components part comes at the end it would be good to
>> think about how that code would fit in from the beginning and to
>> clearly document it both in issues and in the code.
>>
>> Getting a good design is actually more important than implementing all
>> of the pieces. If the groundwork is done then other contributors in
>> future can easily implement the remaining features one by one. Right
>> now it is not easy to improve the code for systems because of the way
>> that it is structured.
>>
>> On Sun, 15 Mar 2020 at 19:27, Milan Jolly  wrote:
>> >
>> > Thanks for your reply. I have planned a rough layout for the phases. I 
>> > took a lot of time this past month to understand all the mathematics that 
>> > will be involved and have grasped some part of it.
>> >
>> > If I am lucky and get selected for GSOC'20 for this organisation, then the 
>> > below is the rough plan. Please comment on suggestions if necessary.
>> >
>> > Community Bonding phase:
>> > 1. Using matrix exponential to solve first order linear constant 
>> > coefficient homogeneous systems(n equations).
>> > 2. Adding new test cases and/or updating old ones.
>> > 3. Removing and closing related issues if they are solved by the addition 
>> > of this general solver. Identifying and removing the special cases solvers 
>> > which are covered by this general solver.
>> >
>> > Phase I:
>> > 1. Adding technique to solve first order constant coefficient 
>> > non-homogeneous systems(n equations).
>> > 2. Adding the functionality that reduces higher order linear ODEs to first 
>> > order linear ODEs(if not done already, and if done, then incorporating it 
>> > to solve higher order ODEs).
>> > 3. Adding a special case solver when non-constant linear first order ODE 
>> > has symmetric coefficient matrix.
>> >
>> > Phase II:
>> > 1. Adding technique to solve non-constant non-homogeneous linear ODE based 
>> > off the solver added by the end of Phase I.
>> > 2. Evaluating and eliminating unnecessary solvers.
>> > 3. Closing related issues solved by the general solvers and identifying 
>> > and removing unwanted solvers.
>> > 4. Adding basic rearrangements to simplify the system of ODEs.
>> >
>> > Phase III:
>> > 1. Dividing the ODEs by evaluating which sub-systems are weakly and 
>> > strongly connected and handling both of these cases accordingly.
>> > 2. Adding a special case solver where the independent variable can be 
>> > eliminated and thus solving the system becomes easier.
>> > 3. Wrapping things up: adding test cases, eliminating unwanted solvers and 
>> > updating documentation.
>> >
>> > This is the rough layout and my plan for summer if I get selected. If this 
>> > plan seems ok then I would include this plan in my proposal.
>> >
>> > On Saturday, March 14, 2020 at 9:37:31 PM UTC+5:30, Oscar wrote:
>> >>
>> >> It's hard to say how much time each of these would take. The roadmap
>> >> aims to completely replace all of the existing code for systems of
>> >> ODEs. How much of that you think you would be able to do is up to you
>> >> if making a proposal.
>> >>
>> >> None of the other things described in the roadmap is implemented
>> >> anywhere as far as I know. Following the roadmap it should be possible
>> >> to close all of these issues I think:
>> >> https://github.com/sympy/sympy/issues?q=is%3Aopen+is%3Aissue+label%3Asolvers.dsolve.system
>> >>
>> >> On Fri, 13 Mar 2020 

[sympy] GSOC project ideas

[Basilis Kalos]

 

 Hi all


  The first project that i’m most interested to work on is the “Optimize 
floating point expressions”. I am familiar with Herbie and I have started 
reading its source code with the purpose of adapting ideas and even code 
(after re-writing it in python). How does that sound?


  I also would be really excited to work on the “Probability” project. Are 
any of those project ideas available? Should i look for projects that 
no-one else is working on?  


Thank you!

-- 
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/0e580f98-f87e-4183-b078-b1fdaa2a2376%40googlegroups.com.

Re: [sympy] Re: [Discussion] [GSoC] Creating a Java Parser

[Gajjar Smit]

I will surely look into the commonalities in those modules if they exist
and will raise relevant issue!

On Tue 17 Mar, 2020, 12:46 AM Aaron Meurer,  wrote:

> Another thing to consider, since this would be the third such language
> to be supported in SymPy (after C and Fortran), is if there are
> commonalities in the parsing code for each that should be factored out
> into a helper submodule.
>
> Aaron Meurer
>
> On Mon, Mar 16, 2020 at 1:12 PM Gajjar Smit 
> wrote:
> >
> > Thanks Aaron and Nikhil for suggestions.
> >
> > I have gone through javalang package and tried out few examples. AST
> nodes can be traversed in javalang and children can be accessed. Here,
> every relevant bunch of tokens are represented as an object of superclass
> CompilationUnit(somewhat similar to TranslationUnit in clang) which is
> again a subclass of generalized Node class. (Link to the javalang repo)
> > A basic example of tree traversal is attached as image.
> >
> >
> > I went through AST hierarchy in sympy ast module. I am also trying to
> understand generic sympy_expr module.
> > Should I start working on my proposal in this direction?
> >
> > --
> > 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/f3d1221b-e731-49e0-9c01-09671f7fbb02%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/CAKgW%3D6%2Bh2H33AehhfmsPgFBD0fkz7-X4cTEx4tOy3w4N2XUuPA%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CA%2B%2BiR_zBGH3Pnxqab6zNNFV_TAPUTDWqS6C%2BdxGutJJ%3DOKCN0g%40mail.gmail.com.

Re: [sympy] Re: [Discussion] [GSoC] Creating a Java Parser

[Aaron Meurer]

Another thing to consider, since this would be the third such language
to be supported in SymPy (after C and Fortran), is if there are
commonalities in the parsing code for each that should be factored out
into a helper submodule.

Aaron Meurer

On Mon, Mar 16, 2020 at 1:12 PM Gajjar Smit  wrote:
>
> Thanks Aaron and Nikhil for suggestions.
>
> I have gone through javalang package and tried out few examples. AST nodes 
> can be traversed in javalang and children can be accessed. Here, every 
> relevant bunch of tokens are represented as an object of superclass 
> CompilationUnit(somewhat similar to TranslationUnit in clang) which is again 
> a subclass of generalized Node class. (Link to the javalang repo)
> A basic example of tree traversal is attached as image.
>
>
> I went through AST hierarchy in sympy ast module. I am also trying to 
> understand generic sympy_expr module.
> Should I start working on my proposal in this direction?
>
> --
> 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/f3d1221b-e731-49e0-9c01-09671f7fbb02%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/CAKgW%3D6%2Bh2H33AehhfmsPgFBD0fkz7-X4cTEx4tOy3w4N2XUuPA%40mail.gmail.com.

[sympy] Re: [Discussion] [GSoC] Creating a Java Parser

[Gajjar Smit]

Thanks Aaron and Nikhil for suggestions. 

I have gone through javalang package and tried out few examples. AST nodes 
can be traversed in javalang and children can be accessed. Here, every 
relevant bunch of tokens are represented as an object of superclass 
CompilationUnit(somewhat similar to TranslationUnit in clang) which is 
again a subclass of generalized Node class. (Link to the javalang repo) 

A basic example of tree traversal is attached as image.


I went through AST hierarchy in sympy ast module. I am also trying to 
understand generic sympy_expr module.
Should I start working on my proposal in this direction?

-- 
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/f3d1221b-e731-49e0-9c01-09671f7fbb02%40googlegroups.com.

[sympy] GSoC 2020

[Thanasis Kiatos]

Greetings everyone,,


I am Athanasios Kiatos from Greece. Currently, I am pursuing masters in 
Computer, Telecommunications and Network Engineering from the 

Department of Informatics and Telecommunications (DIT) of the National and 
Kapodistrian University of Athens (NKUA).

I have a bachelor’s degree in Computer Science and Engineering and I am 
interested in the topics of Machine Learning, Mathematics, Astronomy, 
Computer Science and engineering.

I find your ideas for the Google Summer of Code quite interesting and I 
want to participate in this event.

Any information regarding how to contribute, get more involved in this 
community and submit the GSoC 2020 proposal will be welcome. 


Best regards,

Athanasios Kiatos,

NKUA - University of Athens

-- 
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/d3d024f8-af11-491f-90d4-5b5945221bdc%40googlegroups.com.

[sympy] GSoC applications are now open

[Aaron Meurer]

To all interested GSoC students, applications are now open at
https://summerofcode.withgoogle.com/. Be mindful that the deadline is
March 31 at 1800 UTC. This is a hard deadline. Google does not accept
late applications under any circumstances. You will be able to edit
your application up to the deadline, so I suggest you submit as early
as possible. Submitting earlier will also give us a chance to give you
feedback on your application. Also be aware that we impose the same
deadline for submitting a pull request for your patch requirement, so
if you have not yet submitted one, get on that right away.

To all mentors, if you are not signed up as a mentor for SymPy at
https://summerofcode.withgoogle.com/dashboard/, please send me your
email. Aside from that, please help review student pull requests and
give feedback on their applications.

Aaron Meurer

-- 
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/CAKgW%3D6KRcUxOk-fOxe%2BF52WuoSoKu%3Dz1OQybw7nkDwjG6dnFDQ%40mail.gmail.com.

Re: [sympy] Introduction and Idea for GSOC 2020 (Parsing)

[Nikhil Maan]

Hey souvik, 

If you find something useful in your research, it'll be great if you can 
discuss it here. We can also provide our suggestions and feedback. You can 
also discuss the proposal here if you would like to before submitting,

Also, we do require you to submit at least one patch to SymPy along with 
your proposal. You can read more about it here. 


Regards, 
Nikhil Maan

On Sunday, February 16, 2020 at 2:35:10 PM UTC+5:30, Souvik Mandal wrote:
>
> Thanks, Aaron. I will research those. After I am done, should I discuss 
> those here or create a proposal and submit it somewhere (before actual 
> submission of proposal in GSoC website)? Also, do I need to contribute to 
> sympy before writing the proposal (I am new in this community)?
>
> On Sunday, February 16, 2020 at 1:43:52 PM UTC+5:30, Aaron Meurer wrote:
>>
>> The idea is somewhat open. There is already an existing LaTeX parser 
>> that uses ANTLR, but it could be improved. If you determine that 
>> another parser would be better, than we can switch. Also if you find 
>> something that already knows how to generate an AST for LaTeX we can 
>> look at using that as well. I don't know of anything out there, but I 
>> also haven't really researched it. 
>>
>> Basically, we haven't researched the problem enough ourselves yet to 
>> know what the best technological solution to it would be, so part of 
>> your proposal process would be doing that and discussing the options 
>> with us. 
>>
>> Aaron Meurer 
>>
>> On Sat, Feb 15, 2020 at 11:54 PM Souvik Mandal  
>> wrote: 
>> > 
>> > Hi, 
>> > I am Souvik Mandal. I am a fourth-year computer and engineering student 
>> from IIT Indore. I am interested in working in the Parsing project under 
>> Computer Science, Graphics, and Infrastructure Projects section. I have few 
>> doubts regarding the project - 
>> > 
>> > Do I need to design the AST, or will we be using AST for LaTeX that is 
>> already implemented? Also, will we be using ANTLR and python parser, or it 
>> needs to be implemented from scratch? It would be great if anyone can guide 
>> me. 
>> > 
>> > Thank you. 
>> > 
>> > -- 
>> > 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 sy...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sympy/5445b3ea-aa9f-4dcb-9564-70454ebd737e%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/398ab596-5049-48d6-ad70-6d5e1cdaed07%40googlegroups.com.

Re: [sympy] Re: [Discussion] GSoC 2020: Improving and extending ODE

[Milan Jolly]

Thanks for the suggestion, I have started with the design for these 
solvers. But I have one doubt, namely since now we are using 
linear_eq_to_matrix function to check if the system of ODEs is linear or 
not, would we require the canonical rearrangements part? Or rather are 
there other cases when we can reduce non-linear ODEs into linear ODEs.

On Monday, March 16, 2020 at 2:53:57 AM UTC+5:30, Oscar wrote:
>
> That seems reasonable to me. Since the plan is a total rewrite I think 
> that it would be good to put some time in at the beginning for 
> designing how all of these pieces would fit together. For example even 
> if the connected components part comes at the end it would be good to 
> think about how that code would fit in from the beginning and to 
> clearly document it both in issues and in the code. 
>
> Getting a good design is actually more important than implementing all 
> of the pieces. If the groundwork is done then other contributors in 
> future can easily implement the remaining features one by one. Right 
> now it is not easy to improve the code for systems because of the way 
> that it is structured. 
>
> On Sun, 15 Mar 2020 at 19:27, Milan Jolly  > wrote: 
> > 
> > Thanks for your reply. I have planned a rough layout for the phases. I 
> took a lot of time this past month to understand all the mathematics that 
> will be involved and have grasped some part of it. 
> > 
> > If I am lucky and get selected for GSOC'20 for this organisation, then 
> the below is the rough plan. Please comment on suggestions if necessary. 
> > 
> > Community Bonding phase: 
> > 1. Using matrix exponential to solve first order linear constant 
> coefficient homogeneous systems(n equations). 
> > 2. Adding new test cases and/or updating old ones. 
> > 3. Removing and closing related issues if they are solved by the 
> addition of this general solver. Identifying and removing the special cases 
> solvers which are covered by this general solver. 
> > 
> > Phase I: 
> > 1. Adding technique to solve first order constant coefficient 
> non-homogeneous systems(n equations). 
> > 2. Adding the functionality that reduces higher order linear ODEs to 
> first order linear ODEs(if not done already, and if done, then 
> incorporating it to solve higher order ODEs). 
> > 3. Adding a special case solver when non-constant linear first order ODE 
> has symmetric coefficient matrix. 
> > 
> > Phase II: 
> > 1. Adding technique to solve non-constant non-homogeneous linear ODE 
> based off the solver added by the end of Phase I. 
> > 2. Evaluating and eliminating unnecessary solvers. 
> > 3. Closing related issues solved by the general solvers and identifying 
> and removing unwanted solvers. 
> > 4. Adding basic rearrangements to simplify the system of ODEs. 
> > 
> > Phase III: 
> > 1. Dividing the ODEs by evaluating which sub-systems are weakly and 
> strongly connected and handling both of these cases accordingly. 
> > 2. Adding a special case solver where the independent variable can be 
> eliminated and thus solving the system becomes easier. 
> > 3. Wrapping things up: adding test cases, eliminating unwanted solvers 
> and updating documentation. 
> > 
> > This is the rough layout and my plan for summer if I get selected. If 
> this plan seems ok then I would include this plan in my proposal. 
> > 
> > On Saturday, March 14, 2020 at 9:37:31 PM UTC+5:30, Oscar wrote: 
> >> 
> >> It's hard to say how much time each of these would take. The roadmap 
> >> aims to completely replace all of the existing code for systems of 
> >> ODEs. How much of that you think you would be able to do is up to you 
> >> if making a proposal. 
> >> 
> >> None of the other things described in the roadmap is implemented 
> >> anywhere as far as I know. Following the roadmap it should be possible 
> >> to close all of these issues I think: 
> >> 
> https://github.com/sympy/sympy/issues?q=is%3Aopen+is%3Aissue+label%3Asolvers.dsolve.system
>  
> >> 
> >> On Fri, 13 Mar 2020 at 22:30, Milan Jolly  wrote: 
> >> > 
> >> > I have  mostly read and understood matrix exponentials and Jordan 
> forms along with the ODE systems roadmap. But I am unclear as to what has 
> already been done when it comes to implementing the general solvers. For 
> example: The matrix exponentials part has already been implemented and now 
> I have a PR that has revived the matrix exponential code. 
> >> > 
> >> > I want to make a proposal and contribute to make these general 
> solvers during this summer if my proposal gets accepted. But I am unclear 
> what should be the parts I need to work during community bonding period, 
> phase 1, phase 2 and phase 3 as I am unaware how much time each part of the 
> general solvers would take. 
> >> > 
> >> > If someone can help me in this regard(helping me with these 2 
> questions) then it would be great. 
> >> > 
> >> > 
> >> > On Tue, Feb 25, 2020, 5:09 AM Milan Jolly  
> wrote: 
> >> >> 
> >> >> I will go through the roadmap. 

[sympy] Re: Introduction to the SymPy community

[Nikhil Maan]

Hey Shaurya, 

If you are familiar with R and Ocatve, would you be interested in helping 
with parsing R and Ocatve code to SymPy expressions? You can check out 
https://groups.google.com/forum/#!topic/sympy/d5Ipo90jkQc for further 
reference.

You can check out Introduction to contributing 
 and 
Development 
workflow  to get 
familiar with development. You can also check out Easy-to-fix issues on our 
Issue 
Tracker  to get started with 
contributing.

Regards, 
Nikhil Maan

On Sunday, February 23, 2020 at 10:47:03 AM UTC+5:30, Shaurya Shah wrote:
>
>  Hello everyone, 
>  My name is Shaurya Shah and I am currently in my second year puruing a 
> B.E. degree in Information Technology from Jadavpur University. I have more 
> than one year of experience working with python. I also have some 
> experience with machine learning and know other languages such as 
> C++,Java,R and Octave.  Any guidance on getting started with SymPy will be 
> appreciated and I intend to contribute to SymPy in the future as well. 
> Regards,
> Shaurya Shah.
>

-- 
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/d5265a84-e836-467e-af96-3dc91bd626c3%40googlegroups.com.

[sympy] Re: [Discussion] [GSoC] Creating a Java Parser

[Nikhil Maan]

I tested the package  for some basic syntax and it seems to provide a parse 
tree representation for the syntax.
But, does it provide any support for traversing the tree and accessing the 
children nodes, or would you need to implement that on your own? 

Also, you should check out the SymPyExpression class at sym_expr.py 
. I 
created it as a wrapper to act as a front-end for all the parsers so that 
the user doesn't have to learn about all the parsers and their APIs 
differently. The parser you create which will be in the parsing/java module 
should be called from the SymPyExpression class and the users shouldn't 
need to interact with the parser directly. 

You should also check out asy.py 
 to get 
familiar with SymPy's AST.

On Monday, March 16, 2020 at 7:46:57 AM UTC+5:30, Gajjar Smit wrote:
>
> Hello everyone,
> I am Smit Gajjar, a third year undergraduate student pursuing Computer 
> Engineering at LD College of Engineering, Ahmedabad, India.
>
> I have been exploring sympy since last year by reading codebase, trying 
> out examples as well as solving issues recently. I am looking forward to 
> contribute to sympy through a GSOC project, if I am lucky enough. I have 
> been using Python, C++ for 3 years in contests and projects as well as Java 
> for 4 years in school and college practicals and mini-projects.
>
> I am highly motivated to work towards *creating a Java language Parser*, 
> which would convert a Java code to corresponding Sympy code. I went through 
> the codebase of C and Fortran Parser under the parsing module(implemented 
> by Nikhil Maan last year). I thoroughly read it and tried to grasp how it 
> works.
>
> I believe, I can do the same for Java language, since I am quite 
> comfortable with Java. I am currently revising the concepts of parser and 
> lexer from our college curriculum of System Programming, Theory of 
> Computation and Compiler Design and also working on examples involving 
> *javalang* pip package and *antlr4,* which would make it possible.
>
> (Overview: C Parser converts C syntax to AST using Clang(external optional 
> dependency) and Fortran Parser converts Fortran syntax to ASR using 
> lfortran(external optional dependency). After that, Sympy's own Codegen is 
> responsible to generate Sympy syntax from AST or ASR. Similar will be case 
> for Java.)
>
> Lastly, my question is: Is it okay to carry this forward? If it is, then 
> is there any other documentation/codebase/issues I should go through to 
> better familiarize myself with the current status of parsing module?
>

-- 
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/d89ed1bf-f356-4360-9cbf-b0721e332451%40googlegroups.com.