[sympy] Re: Future plans for pattern matching

2010-05-03 Thread smichr
Sebastian wrote: (1) Implement a generic "Hint"s model which can be used to store values of different hints and also be used to find out interactively what hints are possible. (This is already done in the hints branch and might also be useful for other parts in sympy) I have a manage_hints routin

Re: [sympy] Re: track patches from other developers using github

2010-05-03 Thread Ondrej Certik
On Mon, May 3, 2010 at 8:29 AM, Christian Muise wrote: > So this is how the forking looks at the moment: > - http://github.com/certik/sympy/network/members > >  Should sympy/sympy be at the top of the chain or will that remain as > certik? Should we continue to pull changes from git.sympy.org, or

[sympy] Re: track patches from other developers using github

2010-05-03 Thread asmeurer
I have posted a question about this on the GitHub support page: http://support.github.com/discussions/site/1481-add-users-to-the-network And the response is basically that users who are not in the network would have to refork to become part of the network. Aaron Meurer On May 3, 9:35 am, "Aaron

Re: [sympy] Future plans for pattern matching

2010-05-03 Thread Ronan Lamy
Le lundi 03 mai 2010 à 14:12 -0600, Aaron S. Meurer a écrit : > On May 3, 2010, at 2:11 PM, Sebastian wrote: > > There will be a fallback matching function that will be called if two > > expressions are of the same type. They match only if all it's args are > > matching. Of course And, Or, Xor are

Re: [sympy] Future plans for pattern matching

2010-05-03 Thread Aaron S. Meurer
On May 3, 2010, at 2:11 PM, Sebastian wrote: > Thanks for all your comments, it's very helpful to get so thorough feedback. > > On 05/03/2010 06:21 PM, Ronan Lamy wrote: >> Le dimanche 02 mai 2010 à 09:46 -0700, basti a écrit : >> >>> The last few days I spent quite some time on understanding t

Re: [sympy] Future plans for pattern matching

2010-05-03 Thread Aaron S. Meurer
On May 3, 2010, at 10:21 AM, Ronan Lamy wrote: > Le dimanche 02 mai 2010 à 09:46 -0700, basti a écrit : >> The last few days I spent quite some time on understanding the pattern >> matching and substitution logic in sympy and trying out ideas to >> improve them. Now I feel able and willing to red

Re: [sympy] Future plans for pattern matching

2010-05-03 Thread Sebastian
Thanks for all your comments, it's very helpful to get so thorough feedback. On 05/03/2010 06:21 PM, Ronan Lamy wrote: > Le dimanche 02 mai 2010 à 09:46 -0700, basti a écrit : > >> The last few days I spent quite some time on understanding the pattern >> matching and substitution logic in sympy

Re: [sympy] Future plans for pattern matching

2010-05-03 Thread Ronan Lamy
Le dimanche 02 mai 2010 à 09:46 -0700, basti a écrit : > The last few days I spent quite some time on understanding the pattern > matching and substitution logic in sympy and trying out ideas to > improve them. Now I feel able and willing to redesign most of the > stuff and will in the following gi

Re: [sympy] Re: track patches from other developers using github

2010-05-03 Thread Aaron S. Meurer
On May 3, 2010, at 9:29 AM, Christian Muise wrote: > So this is how the forking looks at the moment: > - http://github.com/certik/sympy/network/members > > Should sympy/sympy be at the top of the chain or will that remain as > certik? I don' t think it really matters. The only way to make it

[sympy] Re: track patches from other developers using github

2010-05-03 Thread Christian Muise
So this is how the forking looks at the moment: - http://github.com/certik/sympy/network/members Should sympy/sympy be at the top of the chain or will that remain as certik? Should we continue to pull changes from git.sympy.org, or just the github sympy repo? Thanks. Cheers On May 3, 7:22 am

[sympy] Re: Future plans for pattern matching

2010-05-03 Thread Vinzent Steinberg
On 2 mai, 19:58, "Aaron S. Meurer" wrote: > For pattern matching where the result is not well defined, what do you plan > to do (e.g., (x + y).match(u + v), u and v are both Wild's)?  Will you just > have a disclaimer that if you do this, the result could be not what you > expect? We could add

[sympy] Re: track patches from other developers using github

2010-05-03 Thread Vinzent Steinberg
On May 1, 4:16 am, Ondrej Certik wrote: > > Should we now fork this repository and then push our private branches to > > the new fork? > > If you have a repository that was fork of my repository at github > (e.g. you can see your patches in the network graph), then you don't > have to. > > Otherwi

[sympy] Re: track patches from other developers using github

2010-05-03 Thread Vinzent Steinberg
On Apr 30, 7:31 pm, "Aaron S. Meurer" wrote: > I agree with Ondrej.  git am -3 fails for me a lot too, especially if the > patch wasn't made using git format-patch (regular diff, git diff, etc.) Thats indeed a problem, 'git am -3' works only for git patches. For other patches you should use 'git