Hi Sergey What I thought as of now, is to have some expression tree kind of thing which will expand one step and the printed, and this goes on. Using trace will tell us the workflow but will not tell the exact input and output and their position, if we use trace module then we have to manage for every different condition and that condition will change when code changes. So use of trace may become dependent. What are your suggestions?
Rajat On Monday, February 17, 2014 4:27:05 PM UTC+5:30, Sergey Kirpichev wrote: > > It doesn't seems to be a good idea to modify almost every function in the > SymPy. > > It's Python, it has a great introspection and debugging capabilities! > Please take look to something like trace module from stdlib. > > btw, if you are going to modify the SymPy sources - please fork and do > your modification on the branch. > > https://github.com/sympy/sympy/wiki/Development-workflow > > On Sunday, February 16, 2014 8:41:54 PM UTC+4, RAJAT AGGARWAL wrote: >> >> Hi Matheww >> You can look at the following link. I had just posted some methods of the >> classes so that you can have the idea of some modifications. >> https://github.com/rajat974/StepDerivation >> >> Rajat Aggarwal >> >> On Sunday, February 16, 2014 3:04:19 AM UTC+5:30, RAJAT AGGARWAL wrote: >>> >>> Based on suggestions given by Matheww for step-by-step implementation, I >>> tried implementing the step derivation first. Attached file is the output >>> of some basic derivations which show steps. It needs to be arranged yet. >>> Also, the printing may depend upon the certain requirements. Waiting for >>> the feedback. >>> >>> Thanks >>> >>> Rajat >>> >> -- 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. For more options, visit https://groups.google.com/groups/opt_out.
