[sympy] I want to apply for gsoc for the first time and am good in c programing wat do I do
-- 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 sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/939bde8f-6945-4a38-b515-65b37351a7b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[sympy] brief introduction to the community
Hello everyone, I am Ruijian and want to apply for GSoC 2018. I am a second year student pursuing pure mathematics and computer science at University of Toronto. I have been programming in python for two years, including some projects like Huffman compression/decompression, face recognition using convolutional neural network... Also, I did a research project on parallel programming under a professor's supervision last summer. I hope I can make some contributions to the community! Best regards, Ruijian -- 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 sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/3f0afdda-5bd1-4ec0-be4e-c67eea42c29f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[sympy] GSOC 2018: Rubi
Hello, I am Ashish Kumar Gaurav . I will be a GSOC applicant this year. I have been contributing to sympy since november. I want to discuss on the Rubi Integrator idea as given on the Idea's page. What are the works left that must be done to get this integrator completed ? In the present rubi code which parts need to be improved? What are the works that sholud be done as gsoc project? -- 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 sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/abc88646-4067-43c3-a2ef-b77e82b36ce7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[sympy] Support for using Symbols as Pandas indexes
Hi, I ran into problems while trying to use Symbols as columns for a pandas.DataFrame *. This is probably not relevant to SymPy development itself, but rather just use. This seems to be a problem with both frameworks treating callable() objects specially: >>> import pandas as pd >>> from sympy.abc import x, y >>> gg = pd.DataFrame([[1,2],[3,3],[4,5]], columns=[x,y]) >>> print(gg[[x]]) # works fine, but returns a DataFrame x 0 1 1 3 2 4 >>> print(gg[x]) Traceback (most recent call last): File "", line 1, in File "...\pandas\core\frame.py", line 1941, in __getitem__ key = com._apply_if_callable(key, self) File "...\pandas\core\common.py", line 441, in _apply_if_callable return maybe_callable(obj, **kwargs) File "...sympy\core\symbol.py", line 158, in __call__ return Function(self.name)(*args) File "...\sympy\core\function.py", line 761, in __new__ obj = super(AppliedUndef, cls).__new__(cls, *args, **options) File "...\sympy\core\function.py", line 431, in __new__ pr = max(cls._should_evalf(a) for a in result.args) File "...\sympy\core\function.py", line 431, in pr = max(cls._should_evalf(a) for a in result.args) File "...\sympy\core\function.py", line 449, in _should_evalf if arg.is_Float: File "...\pandas\core\generic.py", line 3081, in __getattr__ return object.__getattribute__(self, name) AttributeError: 'DataFrame' object has no attribute 'is_Float' The way to get a pd.Series would be: >>> gg[[x]].iloc[:,0] # super uncomfortable... 01 13 24 Name: x, dtype: int64 Is there any reasonable way this interaction could be worked around? It seems like a problem on the Pandas end, or maybe even designed functionality, since functions work the same way (but fail faster): >>> fg = pd.DataFrame([[1,2],[3,3],[4,5]], columns=[f,g]) >>> fg[[f]] 0 1 1 3 2 4 >>> fg[f] Traceback (most recent call last): File "", line 1, in File "...\pandas\core\frame.py", line 1941, in __getitem__ key = com._apply_if_callable(key, self) File "...\pandas\core\common.py", line 441, in _apply_if_callable return maybe_callable(obj, **kwargs) TypeError: f() takes no arguments (1 given) But is there any way I can check whether the inputs are Symbols and "freeze" them so that they become uncallable? Maybe some other workaround? Thanks in advance. * Why am I doing this? Partially due to curiosity, and partially because my users might end up doing the same. It turns out that using Symbols as variable placeholders in a data science workflow might be useful. -- 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 sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/1f26bab1-a623-4054-b392-c1e78f0ac9a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [sympy] Support for using Symbols as Pandas indexes
Symbol objects being callable is something that we've wanted to remove
for some time, but I don't know if it will happen any time soon.
https://github.com/sympy/sympy/issues/3539
I don't know of any simple workarounds. My first thought was to use a
subclass, but I can't figure out how to make a subclass of a
callable() class not callable(). And you can't del Symbol.__call__
because it uses __slots__.
The only thing I can recommend is to use any other kind of expression
than Symbol. Even Function('f')(x) isn't callable.
It would be nice if pandas had some way to indicate that an object
shouldn't be considered callable. I looked at the source and it
doesn't like there is one (it just checks callable(),
https://github.com/pandas-dev/pandas/blob/6485a36483884fb817800a8380a4a4197d6df4ad/pandas/core/common.py#L470).
Perhaps you should open a pandas issue about it.
Aaron Meurer
On Fri, Feb 9, 2018 at 10:53 AM, 'Nowan Ilfideme' via sympy
wrote:
> Hi, I ran into problems while trying to use Symbols as columns for a
> pandas.DataFrame *.
> This is probably not relevant to SymPy development itself, but rather just
> use.
> This seems to be a problem with both frameworks treating callable() objects
> specially:
>
import pandas as pd
from sympy.abc import x, y
>
gg = pd.DataFrame([[1,2],[3,3],[4,5]], columns=[x,y])
>
print(gg[[x]]) # works fine, but returns a DataFrame
>x
> 0 1
> 1 3
> 2 4
print(gg[x])
> Traceback (most recent call last):
> File "", line 1, in
> File "...\pandas\core\frame.py", line 1941, in __getitem__
> key = com._apply_if_callable(key, self)
> File "...\pandas\core\common.py", line 441, in _apply_if_callable
> return maybe_callable(obj, **kwargs)
> File "...sympy\core\symbol.py", line 158, in __call__
> return Function(self.name)(*args)
> File "...\sympy\core\function.py", line 761, in __new__
> obj = super(AppliedUndef, cls).__new__(cls, *args, **options)
> File "...\sympy\core\function.py", line 431, in __new__
> pr = max(cls._should_evalf(a) for a in result.args)
> File "...\sympy\core\function.py", line 431, in
> pr = max(cls._should_evalf(a) for a in result.args)
> File "...\sympy\core\function.py", line 449, in _should_evalf
> if arg.is_Float:
> File "...\pandas\core\generic.py", line 3081, in __getattr__
> return object.__getattribute__(self, name)
> AttributeError: 'DataFrame' object has no attribute 'is_Float'
>
> The way to get a pd.Series would be:
gg[[x]].iloc[:,0] # super uncomfortable...
> 01
> 13
> 24
> Name: x, dtype: int64
>
>
> Is there any reasonable way this interaction could be worked around? It
> seems like a problem on the Pandas end, or maybe even designed
> functionality, since functions work the same way (but fail faster):
>
fg = pd.DataFrame([[1,2],[3,3],[4,5]], columns=[f,g])
fg[[f]]
>
> 0 1
> 1 3
> 2 4
fg[f]
> Traceback (most recent call last):
> File "", line 1, in
> File "...\pandas\core\frame.py", line 1941, in __getitem__
> key = com._apply_if_callable(key, self)
> File "...\pandas\core\common.py", line 441, in _apply_if_callable
> return maybe_callable(obj, **kwargs)
> TypeError: f() takes no arguments (1 given)
>
> But is there any way I can check whether the inputs are Symbols and "freeze"
> them so that they become uncallable? Maybe some other workaround? Thanks in
> advance.
>
>
>
> * Why am I doing this? Partially due to curiosity, and partially because my
> users might end up doing the same. It turns out that using Symbols as
> variable placeholders in a data science workflow might be useful.
>
> --
> 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 sympy+unsubscr...@googlegroups.com.
> To post to this group, send email to sympy@googlegroups.com.
> Visit this group at https://groups.google.com/group/sympy.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/1f26bab1-a623-4054-b392-c1e78f0ac9a7%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 sympy+unsubscr...@googlegroups.com.
To post to this group, send email to sympy@googlegroups.com.
Visit this group at https://groups.google.com/group/sympy.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sympy/CAKgW%3D6K2E8thqVHTCp%3DvAs_u44uGomv7Xpuy1KcFzKojPqTEyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
