I had trouble setting up the
smtp server for patchbomb on my machine, so I am sending this manually
via gmail using the patchbomb output. Hope it works. :)
-Lance Larsen
# HG changeset patch
# User Lance Larsen
# Date 1226946818 25200
# Node ID 35c17486e4205095a59d2bb8cd421f48925472a5
# P
> 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
# HG changeset patch
# User "Lance Larsen <[EMAIL PROTECTED]>"
# Date 1226946818 25200
# Node ID 060b92b72467a29a2d098e7ce0ee96cbf4c2395b
# Parent d1019a5c66d12d524fe64359c1bd8054cab0cfa9
Substitution syntax extension - implements f.subs(x=1,y=2) and
shorthand syntax f(x=
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
Submission of patch with changes suggested by Brian in post.
# HG changeset patch
# User "Lance Larsen <[EMAIL PROTECTED]>"
# Date 1226946818 25200
# Node ID 5699c540c62b31ddf3c96e07fae6fe64cf10eb1e
# Parent d1019a5c66d12d524fe64359c1bd8054cab0cfa9
Substitution syntax extens
> 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 pa
Guess I should proof read my posts more carefully - lots of
grammatical mistakes :) oh well. Thanks for the input Brian.
-Lance
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this g
I forgot to run the test cases against the second patch. It has
errors. Will correct an resubmit later today.
-Lance
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send
previously submitted patch. Don't know if this causes
problems. 'hg email' was complaining about my parent repository setup
and I didn't have time to debug this so I tried a workaround.
-Lance
# HG changeset patch
# User "Lance Larsen <[EMAIL PROTECTE
> 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 wi
I haven't used frames before, and I think Riccardo's trick is pretty
cool. I didn't have a problem with the simpler behavior of treating
the value as a string, but I do agree that it could lead to confusion
for people. I think good documentation and examples explaining the
originally suggested beh
Here is a corrected implicit subs patch. Note that there is another
__call__ syntax proposal that is being discussed at present on the
thread:
http://groups.google.com/group/sympy-patches/browse_thread/thread/628ebc799ee57ec1
# HG changeset patch
# User "Lance Larsen <[EMAIL PROTECTED]&
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 ot
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
Subst
14 matches
Mail list logo