That page is actually quite old (I am trying to remove it https://github.com/sympy/sympy/pull/2807).
My advice is that the core is the worst place to start if you are trying to understand the code in SymPy. It is by far the hardest to understand. I would start with one of the high-level modules that interested you (solvers, simplify, stats, sets, etc.), and only once you understand how to use SymPy in a high-level way, then start to try to understand how the core works. The best place to start is with the tutorial, as that will show you how to use SymPy as a user. Since SymPy uses itself, this is important even if you wish to develop on SymPy. Aaron Meurer On Fri, May 16, 2014 at 7:23 AM, Jason Moore <[email protected]> wrote: > This page in the documentation gives and intro to the architecture: > > http://docs.sympy.org/dev/guide.html#sympy-s-architecture > > > Jason > moorepants.info > +01 530-601-9791 > > > On Fri, May 16, 2014 at 12:27 AM, Abhishek K Das <[email protected]> > wrote: >> >> Hello everyone ! >> >> I am a newbie here . Please forgive me , if you find this question lame . >> As I asked a few days ago , that how can I contribute to sympy >> and Aaron replied by giving the links to easy-to-fix issue list and the >> development work-flow . >> Now what I am asking is that to write good code for issues or developing >> new stuff , one needs to understand all the **core classes and modules** >> ie how the things have been implemented internally , without the knowledge >> of that it is a bit difficult to straight away write code for patches/issues >> . >> >> I will make my question clear and straight . So my question is that which >> all modules are **essentially important** for one to get hold off , so that >> one can understand the main things working under the hood . I mean it >> would be very nice if one could pin-point the exact files/modules which one >> needs >> to understand to get a head-start in writing good code . >> >> Thanks in advance . >> >> -- >> 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 http://groups.google.com/group/sympy. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/sympy/5a0c65bb-bb92-4d17-8c55-e69875cb9271%40googlegroups.com. >> 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]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAP7f1AhxAfYxjw8p8eoNH66Ws34O151QDwQE7JMAy-6HUMFbvw%40mail.gmail.com. > > 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]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6LLzKGky8B1Te5BuPeS19C5R%3DZ31KrT%2BWTksXJKJH5%3DmA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
