Finally got a few moments to put the implicit subs syntax code
together and get it ready to submit. Here it is.
-Lance
# HG changeset patch
# User [EMAIL PROTECTED]
# Date 1228878177 25200
# Node ID dc86dcc8d059f0a2cd3eb498b595c8a45775aa92
# Parent d1019a5c66d12d524fe64359c1bd8054cab0cfa9
I think it worth sending to the main mailing list one way or another.
There has been a lot of discussion on the sympy-patches list which
probably doesn't have the visibility of the sympy list. I think the
problems with the different approaches have been covered here, so it
is worth hearing what
Sorry if I am being a pain in the #%%, I just want to make sure that
we get the desig of this right as someone else said you only get to
implement __call__ once.
No worries. I appreciate you clarifying your viewpoint. You may not
like what you get if you don't give your opinion.
The patch
Which patch was applied in the main repo?
I did a pull from the main line and it looked like one of my original
patches was included in my repository. If this wasn't from the main
repo (and it sounds like it wasn't), I must have committed the hg
patch locally when I was experimenting with hg
The only reason to not support this is if we thought that subs
might later need to grow keyword arguments that control how subs
itself works. We used to use **kwargs in this exact manner in
IPython's parallel stuff. It ended up *killing* us because we
eventually needed to have keyword
A new patch was submitted which includes suggestions from this
thread.
http://groups.google.com/group/sympy-patches/browse_thread/thread/83c33c0aa8560475
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sympy-patches
