Re: [sympy] Unable to solve the following set of equations

[Shishir Kushwaha]

I'm sorry , I meant to write x1=0, x2=10. It gives 

Eq(Piecewise(((5 + b/(4*a))*sqrt(400*a**2 + 40*a*b + b**2 + 1) - log(4*a*b 
+ 4*sqrt(b**2 + 1)*sqrt(a**2))/(4*sqrt(a**2)) + log(80*a**2 + 4*a*b + 
4*sqrt(400*a**2 + 40*a*b + b**2 + 1)*sqrt(a**2))/(4*sqrt(a**2)) - 
b*sqrt(b**2 + 1)/(4*a), ((a > -oo) & (a < oo) & Ne(a, 0)) | (Ne(a**2, 0) & 
Ne(a*b, 0))), (-(b**2 + 1)**(3/2)/(6*a*b) + (40*a*b + b**2 + 
1)**(3/2)/(6*a*b), Ne(a*b, 0)), (10*sqrt(b**2 + 1), True)), 20)  

but the solution I got is empty i.e. [ ]

Thanks
Shishir Kushwaha

On Sunday 26 May 2024 at 06:58:37 UTC+5:30 asme...@gmail.com wrote:

> With x1 = x2 = 0, arc_length_expr is equal to 0, meaning your eq3 is
> invalid. You can see this if you print eq3. It gets set to False,
> because it is 0 = 10.
>
> Aaron Meurer
>
> On Sat, May 25, 2024 at 5:26 PM Shishir Kushwaha
>  wrote:
> >
> > In the following piece of code I am unable to get the values of a,b and 
> c after solving them.
> > Is there a different way to solve it and what am i doing wrong. Take x1 
> = 0 , y1=10, x2=0, y2=10, length = 20.
> >
> > def get_lowest_point(self):
> > a, b, c, x = symbols('a b c x')
> >
> > x1, y1 = self._left_support
> > x2, y2 = self._right_support
> > length = self._length
> >
> > eq1 = Eq(a * x1**2 + b * x1 + c, y1)
> > eq2 = Eq(a * x2**2 + b * x2 + c, y2)
> > arc_length_expr = integrate(sqrt(1 + (2 * a * x + b)**2),
> > (x, x1, x2))
> > eq3 = Eq(arc_length_expr, length)
> > solution = solve((eq1, eq2, eq3), (a, b, c))
> >
> > # Print the solution to debug
> > print("Solution:", solution)
> >
> > return solution
> >
> > --
> > 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+un...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/6f9f85cf-e010-443a-9a5c-b03a359e1132n%40googlegroups.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/2fafa12f-c2f2-423e-b6ae-d59ff772dad1n%40googlegroups.com.

[sympy] Unable to solve the following set of equations

[Shishir Kushwaha]

In the following piece of code I am  unable to get the values of a,b and c 
after solving them.
Is there a different way to solve it and what am i doing wrong. Take x1 = 0 
, y1=10, x2=0, y2=10, length = 20. 

def get_lowest_point(self):
a, b, c, x = symbols('a b c x')

x1, y1 = self._left_support
x2, y2 = self._right_support
length = self._length

eq1 = Eq(a * x1**2 + b * x1 + c, y1)
eq2 = Eq(a * x2**2 + b * x2 + c, y2)
arc_length_expr = integrate(sqrt(1 + (2 * a * x + b)**2),
(x, x1, x2))
eq3 = Eq(arc_length_expr, length)
solution = solve((eq1, eq2, eq3), (a, b, c))

# Print the solution to debug
print("Solution:", solution)

return solution

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/6f9f85cf-e010-443a-9a5c-b03a359e1132n%40googlegroups.com.

Re: [sympy] GSoC 2024 Contributors Announced

[Shishir Kushwaha]

Respected members,

I would like to express my gratitude for being given the opportunity to 
work on a project in GSoC. 
I have been helped on multiple occasions on this group and on GitHub and 
would like to thank everyone
for being so supportive and hope I would be able to do the same for 
others.  
I look forward to working with you.

Thanks
Shishir Kushwaha
On Friday 3 May 2024 at 23:55:57 UTC+5:30 peter.st...@gmail.com wrote:

> Dear Aaron,
>
> I am happy to join in congratulating the guys selected for GSoC!
>
> I am a retired salesman (studied engineering 45+ years ago) and I play 
> around with sympy.phyiscs.mechanics to pass time. VERY enjoyable!
> I have never made a PR, and the equation: me + GitHub / computers = 
> complete mess holds true.
>
> These two projects look interesting to me:
>
> Hwayeon Kang, Implementing Specific Forces and Torques: Jason Moore, Timo 
> Stienstra
> Riccardo Di Girolamo, Sympy for Classical Mechanics: Developing and 
> Benchmarking Equations of Motion Generation Methods: Jason Moore, Timo 
> Stienstra
>
> Is there a way, I can 'see' what will be done there?
>
> Thanks & take care!
>
> Peter
>
> -Original Message-
> From: sy...@googlegroups.com  On Behalf Of Aaron 
> Meurer
> Sent: Donnerstag, 2. Mai 2024 21:36
> To: sympy 
> Subject: [sympy] GSoC 2024 Contributors Announced
>
> Hi everyone. As many of you may have noticed, Google has announced the 
> results for Google Summer of Code. I am proud to announce that 5 people 
> have been accepted to work on SymPy this year. The following projects have 
> been
> accepted:
>
> Abhishek Kumar, Improving and Expanding the functionalities of the SymPy's 
> Control Module.: Nikhil Maan
>
> Arnab Nandi, Improving Series Expansions and Limit Computations:
> Anutosh Surendra Bhat, Oscar Benjamin
>
> Hwayeon Kang, Implementing Specific Forces and Torques: Jason Moore, Timo 
> Stienstra
>
> Riccardo Di Girolamo, Sympy for Classical Mechanics: Developing and 
> Benchmarking Equations of Motion Generation Methods: Jason Moore, Timo 
> Stienstra
>
> Shishir Kushwaha, Extending Continuum Mechanics Module: Advait Pote, Ishan 
> Pandhare
>
> Join me in congratulating them on their acceptance.
>
> To everyone who was accepted, you should be receiving an email from your 
> mentors soon to discuss how you will be communicating over the summer about 
> your project. You should meet with your mentors once a week during the 
> summer to go over your progress. Most people choose to use video calls for 
> these meetings, but you may use another method, such as a public chatroom, 
> if you prefer.
>
> Note that in many cases you may interact with some mentors as your primary 
> mentors, and other mentors will be backup mentors. Please contact the 
> backup mentors if you are not able to get ahold of your primary mentor(s). 
> If you cannot get ahold of either, please let me and Oscar Benjamin
> (oscar.j@gmail.com) know immediately.
>
> I would like all of us to strongly encourage students to submit pull 
> requests early and often. This will go a long ways towards making sure that 
> you don't end the summer with a ton of code written that never gets merged. 
> Students should help review pull requests by other students, so that we 
> don't get bogged down reviewing so much code.
>
> We also require that all students keep a weekly blog of their work over 
> the summer. If you don't already have a blog, you should start one. I 
> recommend using either Wordpress, Blogger, or creating your own blog on 
> GitHub pages. If you are savvy enough to set it up, I recommend GitHub 
> pages, but if you aren't, both Wordpress and Blogger are good enough.
>
> The GSoC coding period officially starts May 27 (
> https://developers.google.com/open-source/gsoc/timeline).
>
> I would like to thank all the students who applied this year and everyone 
> who submitted a patch. I would also like to thank all the mentors for 
> helping review patches and proposals.
>
> This summer is looking to be another very productive one for SymPy, and I 
> look forward to it!
>
> Aaron Meurer
>
> --
> 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+un...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2B6r%2BxD_7DjRR60WuAhnsJkRw6SMWOpwTsnVN0D-JrjKw%40mail.gmail.com
> .
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/090be4ee-740e-4353-8bdc-00d232ead3aan%40googlegroups.com.

[sympy] Re: Gsoc Proposal review

[Shishir Kushwaha]

I made the access restricted so no one could edit your proposal but people 
won't be able to view the proposal as well. I would suggest you change the 
access to view only. I am sorry if your intentions were different with the 
access you had given .

On Monday 1 April 2024 at 22:46:30 UTC+5:30 Shishir Kushwaha wrote:

> Hey Arnab, the link is currently shared in editing mode, kindly change 
> that or someone might mess with your project accidentally. 
>
> ___
> Shishir 
>
> On Monday 1 April 2024 at 18:19:11 UTC+5:30 arnabna...@gmail.com wrote:
>
>> Hello everyone I am Arnab Nandi, I have been contributing to sympy since 
>> the past 5 moths , I want to apply for GSoC 2024 on the idea "improving 
>> series expansions and limit computations". I think my previous mails were 
>> not approved since I had attached a pdf of the same, I am now attaching a 
>> link to my proposal in docs as follows:
>> proposal 
>> <https://docs.google.com/document/d/1tjS_Zj9faK-wWWjjCipNsnzYzehyhejiI0PERcNJ2wY/edit?usp=sharing>
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/be830c97-b95b-4d13-854b-aa1b699c0a81n%40googlegroups.com.

[sympy] Re: Gsoc Proposal review

[Shishir Kushwaha]

I was able to make the access restricted so I did that. I am sorry if you 
had meant to have open access for some reason. 

On Monday 1 April 2024 at 22:46:30 UTC+5:30 Shishir Kushwaha wrote:

> Hey Arnab, the link is currently shared in editing mode, kindly change 
> that or someone might mess with your project accidentally. 
>
> ___
> Shishir 
>
> On Monday 1 April 2024 at 18:19:11 UTC+5:30 arnabna...@gmail.com wrote:
>
>> Hello everyone I am Arnab Nandi, I have been contributing to sympy since 
>> the past 5 moths , I want to apply for GSoC 2024 on the idea "improving 
>> series expansions and limit computations". I think my previous mails were 
>> not approved since I had attached a pdf of the same, I am now attaching a 
>> link to my proposal in docs as follows:
>> proposal 
>> <https://docs.google.com/document/d/1tjS_Zj9faK-wWWjjCipNsnzYzehyhejiI0PERcNJ2wY/edit?usp=sharing>
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/1a764bff-44fa-4f66-b12d-cf54e6571c3bn%40googlegroups.com.

Re: [sympy] Re: Project Idea and Expression of Interest

[Shishir Kushwaha]

Sir, I Have tried to make the changes suggested and would like to receive 
your thoughts if they were in the right direction. 
The Proposal 
<https://docs.google.com/document/d/14CC2xlc6uKbAhAkgILE8_HRDdl4nBC_MsO9JbE74y7Y/edit?usp=sharing>

Thanking You
Shishir Kushwaha
On Sunday 31 March 2024 at 02:47:11 UTC+5:30 Shishir Kushwaha wrote:

> The Proposal 
> <https://docs.google.com/document/d/1Ftza5bitPc_9L1Sscb0CMDnxSNLnqv9r9-3kXmWeRwM/edit?usp=sharing>
> Kindly take a look at the new Phases and the revised timeline ,I have set 
> aside some time for the extended goal which can be used to complete work of 
> other phases in case it was not possible earlier.
> I'd be happy to receive any reviews and changes before submission.
>
> Shishir
> On Sunday 31 March 2024 at 02:08:58 UTC+5:30 Shishir Kushwaha wrote:
>
>> Thank you for the review sir. 
>>
>> About the point on the time taken for Phase 2 , the current code included 
>> with the proposal was written with a very intuitive approach but I would 
>> like to follow similar approaches to the ones used in Beams and Trusses 
>> using various inbuilt functions like Singularity Function whose discussion 
>> and implementation might take some extra time.
>>
>> According to my current understanding , I might be able to cut out about 
>> 2 weeks from the entire duration of the project for the extended phase if 
>> the implementation goes smoothly however I wanted some extra time so I 
>> don't promise more things than I might be able to achieve.
>> I will be making the changes recommended and report as soon as possible.
>>
>>
>> Shishir
>>
>> On Sunday 31 March 2024 at 00:18:31 UTC+5:30 apot...@gmail.com wrote:
>>
>>> Your proposal seems very detailed and your contributions are good too. 
>>>
>>> One minor change I'd suggest is instead of adding screenshots of your 
>>> code from your editor, try using any add-ons on Google Docs that enable you 
>>> to write code. This is purely for presentation purposes though. 
>>> About the timeline, you should rename 'Phase 3' as 'Extended Phase' 
>>> because it isn't a part of your project and isn't included in your 
>>> timeline. 
>>> Finally, I don't think you should add the code for everything. Maybe a 
>>> few snippets showing the implementation here and there but not your entire 
>>> project. Try using pseudo code for some or maybe not even that. Also, if 
>>> you are already done with the code for a lot of the project, maybe you can 
>>> reduce the time for Phase II and try including the extended phase in your 
>>> timeline. Assigning 9 weeks for a Phase for which you are quite prepared 
>>> seems a little excessive and I think your project would look better with 3 
>>> phases rather than just 2.
>>>
>>> On Sat, Mar 30, 2024 at 1:50 AM Shishir Kushwaha  
>>> wrote:
>>>
>>>> The Proposal 
>>>> <https://docs.google.com/document/d/1Ftza5bitPc_9L1Sscb0CMDnxSNLnqv9r9-3kXmWeRwM/edit>
>>>> Can you please take a look at it and recommend any changes or 
>>>> suggestions that may be added. I am sorry for the delay, due to some 
>>>> unexpected circumstances I could not complete it earlier. 
>>>>
>>>> Shishir
>>>> On Wednesday 20 March 2024 at 01:37:55 UTC+5:30 apot...@gmail.com 
>>>> wrote:
>>>>
>>>>> I don't think there should be a problem with sending the draft in this 
>>>>> thread itself. Will be glad to look at it. 
>>>>>
>>>>> On Mon, Mar 18, 2024 at 12:09 PM Shishir Kushwaha <
>>>>> kushwahas...@gmail.com> wrote:
>>>>>
>>>>>> I have been working on my proposal for some time, can I please get 
>>>>>> some time from your schedule to get your thoughts and improve on it 
>>>>>> before 
>>>>>> the final submission? 
>>>>>> I would also like to know if there are some additional ideas I should 
>>>>>> add along with my current proposal. 
>>>>>> If possible where should I send my draft proposal?
>>>>>>
>>>>>> Sincerely
>>>>>> Shishir Kushwaha   
>>>>>>
>>>>>> On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> Your ideas seem good. The cable class doesn't have a draw method and 
>>>>>>> could use it considering how the other classes do. The

[sympy] Re: Gsoc Proposal review

[Shishir Kushwaha]

Hey Arnab, the link is currently shared in editing mode, kindly change that 
or someone might mess with your project accidentally. 

___
Shishir 

On Monday 1 April 2024 at 18:19:11 UTC+5:30 arnabna...@gmail.com wrote:

> Hello everyone I am Arnab Nandi, I have been contributing to sympy since 
> the past 5 moths , I want to apply for GSoC 2024 on the idea "improving 
> series expansions and limit computations". I think my previous mails were 
> not approved since I had attached a pdf of the same, I am now attaching a 
> link to my proposal in docs as follows:
> proposal 
> 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/b3e7bb05-007b-4950-8916-c2ce37b9f942n%40googlegroups.com.

Re: [sympy] Re: Project Idea and Expression of Interest

[Shishir Kushwaha]

The Proposal 
<https://docs.google.com/document/d/1Ftza5bitPc_9L1Sscb0CMDnxSNLnqv9r9-3kXmWeRwM/edit?usp=sharing>
Kindly take a look at the new Phases and the revised timeline ,I have set 
aside some time for the extended goal which can be used to complete work of 
other phases in case it was not possible earlier.
I'd be happy to receive any reviews and changes before submission.

Shishir
On Sunday 31 March 2024 at 02:08:58 UTC+5:30 Shishir Kushwaha wrote:

> Thank you for the review sir. 
>
> About the point on the time taken for Phase 2 , the current code included 
> with the proposal was written with a very intuitive approach but I would 
> like to follow similar approaches to the ones used in Beams and Trusses 
> using various inbuilt functions like Singularity Function whose discussion 
> and implementation might take some extra time.
>
> According to my current understanding , I might be able to cut out about 2 
> weeks from the entire duration of the project for the extended phase if the 
> implementation goes smoothly however I wanted some extra time so I don't 
> promise more things than I might be able to achieve.
> I will be making the changes recommended and report as soon as possible.
>
>
> Shishir
>
> On Sunday 31 March 2024 at 00:18:31 UTC+5:30 apot...@gmail.com wrote:
>
>> Your proposal seems very detailed and your contributions are good too. 
>>
>> One minor change I'd suggest is instead of adding screenshots of your 
>> code from your editor, try using any add-ons on Google Docs that enable you 
>> to write code. This is purely for presentation purposes though. 
>> About the timeline, you should rename 'Phase 3' as 'Extended Phase' 
>> because it isn't a part of your project and isn't included in your 
>> timeline. 
>> Finally, I don't think you should add the code for everything. Maybe a 
>> few snippets showing the implementation here and there but not your entire 
>> project. Try using pseudo code for some or maybe not even that. Also, if 
>> you are already done with the code for a lot of the project, maybe you can 
>> reduce the time for Phase II and try including the extended phase in your 
>> timeline. Assigning 9 weeks for a Phase for which you are quite prepared 
>> seems a little excessive and I think your project would look better with 3 
>> phases rather than just 2.
>>
>> On Sat, Mar 30, 2024 at 1:50 AM Shishir Kushwaha  
>> wrote:
>>
>>> The Proposal 
>>> <https://docs.google.com/document/d/1Ftza5bitPc_9L1Sscb0CMDnxSNLnqv9r9-3kXmWeRwM/edit>
>>> Can you please take a look at it and recommend any changes or 
>>> suggestions that may be added. I am sorry for the delay, due to some 
>>> unexpected circumstances I could not complete it earlier. 
>>>
>>> Shishir
>>> On Wednesday 20 March 2024 at 01:37:55 UTC+5:30 apot...@gmail.com wrote:
>>>
>>>> I don't think there should be a problem with sending the draft in this 
>>>> thread itself. Will be glad to look at it. 
>>>>
>>>> On Mon, Mar 18, 2024 at 12:09 PM Shishir Kushwaha <
>>>> kushwahas...@gmail.com> wrote:
>>>>
>>>>> I have been working on my proposal for some time, can I please get 
>>>>> some time from your schedule to get your thoughts and improve on it 
>>>>> before 
>>>>> the final submission? 
>>>>> I would also like to know if there are some additional ideas I should 
>>>>> add along with my current proposal. 
>>>>> If possible where should I send my draft proposal?
>>>>>
>>>>> Sincerely
>>>>> Shishir Kushwaha   
>>>>>
>>>>> On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Your ideas seem good. The cable class doesn't have a draw method and 
>>>>>> could use it considering how the other classes do. The ILD functionality 
>>>>>> does look promising too. 
>>>>>>
>>>>>> I haven't heard or read much about Arches as I believe they are 
>>>>>> inclined towards Civil Engineering and Architecture. I will be 
>>>>>> interested 
>>>>>> to see your approach & thoughts and how you structure them in your 
>>>>>> proposal. 
>>>>>>
>>>>>> On Tuesday, March 5, 2024 at 1:25:06 AM UTC+5:30 
>>>>>> kushwahas...@gmail.com wrote:
>>>>>>
>>>>>>> Respected Sympy community ,
>>&g

Re: [sympy] Re: Project Idea and Expression of Interest

[Shishir Kushwaha]

Thank you for the review sir. 

About the point on the time taken for Phase 2 , the current code included 
with the proposal was written with a very intuitive approach but I would 
like to follow similar approaches to the ones used in Beams and Trusses 
using various inbuilt functions like Singularity Function whose discussion 
and implementation might take some extra time.

According to my current understanding , I might be able to cut out about 2 
weeks from the entire duration of the project for the extended phase if the 
implementation goes smoothly however I wanted some extra time so I don't 
promise more things than I might be able to achieve.
I will be making the changes recommended and report as soon as possible.


Shishir

On Sunday 31 March 2024 at 00:18:31 UTC+5:30 apot...@gmail.com wrote:

> Your proposal seems very detailed and your contributions are good too. 
>
> One minor change I'd suggest is instead of adding screenshots of your code 
> from your editor, try using any add-ons on Google Docs that enable you to 
> write code. This is purely for presentation purposes though. 
> About the timeline, you should rename 'Phase 3' as 'Extended Phase' 
> because it isn't a part of your project and isn't included in your 
> timeline. 
> Finally, I don't think you should add the code for everything. Maybe a few 
> snippets showing the implementation here and there but not your entire 
> project. Try using pseudo code for some or maybe not even that. Also, if 
> you are already done with the code for a lot of the project, maybe you can 
> reduce the time for Phase II and try including the extended phase in your 
> timeline. Assigning 9 weeks for a Phase for which you are quite prepared 
> seems a little excessive and I think your project would look better with 3 
> phases rather than just 2.
>
> On Sat, Mar 30, 2024 at 1:50 AM Shishir Kushwaha  
> wrote:
>
>> The Proposal 
>> <https://docs.google.com/document/d/1Ftza5bitPc_9L1Sscb0CMDnxSNLnqv9r9-3kXmWeRwM/edit>
>> Can you please take a look at it and recommend any changes or suggestions 
>> that may be added. I am sorry for the delay, due to some unexpected 
>> circumstances I could not complete it earlier. 
>>
>> Shishir
>> On Wednesday 20 March 2024 at 01:37:55 UTC+5:30 apot...@gmail.com wrote:
>>
>>> I don't think there should be a problem with sending the draft in this 
>>> thread itself. Will be glad to look at it. 
>>>
>>> On Mon, Mar 18, 2024 at 12:09 PM Shishir Kushwaha <
>>> kushwahas...@gmail.com> wrote:
>>>
>>>> I have been working on my proposal for some time, can I please get some 
>>>> time from your schedule to get your thoughts and improve on it before the 
>>>> final submission? 
>>>> I would also like to know if there are some additional ideas I should 
>>>> add along with my current proposal. 
>>>> If possible where should I send my draft proposal?
>>>>
>>>> Sincerely
>>>> Shishir Kushwaha   
>>>>
>>>> On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com wrote:
>>>>
>>>>> Your ideas seem good. The cable class doesn't have a draw method and 
>>>>> could use it considering how the other classes do. The ILD functionality 
>>>>> does look promising too. 
>>>>>
>>>>> I haven't heard or read much about Arches as I believe they are 
>>>>> inclined towards Civil Engineering and Architecture. I will be interested 
>>>>> to see your approach & thoughts and how you structure them in your 
>>>>> proposal. 
>>>>>
>>>>> On Tuesday, March 5, 2024 at 1:25:06 AM UTC+5:30 
>>>>> kushwahas...@gmail.com wrote:
>>>>>
>>>>>> Respected Sympy community ,
>>>>>>
>>>>>>
>>>>>> My name is Shishir Kushwaha ,currently a sophomore at Indian 
>>>>>> Institute of Technology , BHU ,Varanasi , India . I am currently 
>>>>>> pursuing a 
>>>>>> degree in Mathematics and Computing and my interest lies in fields 
>>>>>> related 
>>>>>> to mathematics, physics and machine learning and have worked on honing 
>>>>>> my 
>>>>>> skills in the domains . Having used Sympy to help me through my projects 
>>>>>> related to Mechanical Engineering , I found it very useful and would 
>>>>>> like 
>>>>>> to help others in the same way by further improving its features in the 
>>>>>> same direction .  
>&

Re: [sympy] Re: Project Idea and Expression of Interest

[Shishir Kushwaha]

The Proposal 
<https://docs.google.com/document/d/1Ftza5bitPc_9L1Sscb0CMDnxSNLnqv9r9-3kXmWeRwM/edit>
Can you please take a look at it and recommend any changes or suggestions 
that may be added. I am sorry for the delay, due to some unexpected 
circumstances I could not complete it earlier. 

Shishir
On Wednesday 20 March 2024 at 01:37:55 UTC+5:30 apot...@gmail.com wrote:

> I don't think there should be a problem with sending the draft in this 
> thread itself. Will be glad to look at it. 
>
> On Mon, Mar 18, 2024 at 12:09 PM Shishir Kushwaha  
> wrote:
>
>> I have been working on my proposal for some time, can I please get some 
>> time from your schedule to get your thoughts and improve on it before the 
>> final submission? 
>> I would also like to know if there are some additional ideas I should add 
>> along with my current proposal. 
>> If possible where should I send my draft proposal?
>>
>> Sincerely
>> Shishir Kushwaha   
>>
>> On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com wrote:
>>
>>> Your ideas seem good. The cable class doesn't have a draw method and 
>>> could use it considering how the other classes do. The ILD functionality 
>>> does look promising too. 
>>>
>>> I haven't heard or read much about Arches as I believe they are inclined 
>>> towards Civil Engineering and Architecture. I will be interested to see 
>>> your approach & thoughts and how you structure them in your proposal. 
>>>
>>> On Tuesday, March 5, 2024 at 1:25:06 AM UTC+5:30 kushwahas...@gmail.com 
>>> wrote:
>>>
>>>> Respected Sympy community ,
>>>>
>>>>
>>>> My name is Shishir Kushwaha ,currently a sophomore at Indian Institute 
>>>> of Technology , BHU ,Varanasi , India . I am currently pursuing a degree 
>>>> in 
>>>> Mathematics and Computing and my interest lies in fields related to 
>>>> mathematics, physics and machine learning and have worked on honing my 
>>>> skills in the domains . Having used Sympy to help me through my projects 
>>>> related to Mechanical Engineering , I found it very useful and would like 
>>>> to help others in the same way by further improving its features in the 
>>>> same direction .  
>>>>
>>>>
>>>> I would like to express my interest in contributing to Sympy in the 
>>>> GSoC 2024 program . The ability to symbolically solve complex problems and 
>>>> ability to integrate well when needed due to it being coded in pure Python 
>>>> makes it an exciting project to anyone with a mathematical background . 
>>>>
>>>>
>>>> I looked through the ideas list page and liked a few projects I would 
>>>> like to work on . I would like to further the module on continuum 
>>>> mechanics 
>>>> by implementing plotting of draw and tension to the newer Cable Class 
>>>> along 
>>>> with an influence line diagram functionality . Along with this I hope to 
>>>> introduce and complete the implementation of structures like Arches 
>>>> allowing similar functionalities in Beams and Trusses . 
>>>>
>>>>
>>>> I would like to request the mentors Ishan Pandhare , Advait Pote , 
>>>> Prakhar Saxena to kindly take a look and check if it aligns with the goals 
>>>> of Sympy and is a suitable idea for GSoC 2024 .
>>>>
>>>>
>>>> I am familiar with Python , Pytorch and JavaScript stacks with 
>>>> experience in many relevant projects of web development and mathematical 
>>>> implementations of Digital Image Processing . 
>>>>
>>>> I hope my technical skills along with my dedication would allow me to 
>>>> successfully execute my duties .
>>>>
>>>>
>>>> Thank you for your time and consideration , I hope to work and learn 
>>>> with the amazing Sympy Community . 
>>>>
>>>>
>>>> Sincerely ,
>>>>
>>>> Shishir Kushwaha 
>>>>
>>>>
>>>> -- 
>> 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+un...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sympy/f29c6bfa-965e-4120-8518-b31acc390981n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sympy/f29c6bfa-965e-4120-8518-b31acc390981n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/aad61845-bbee-438b-9488-ef8f3887e6ebn%40googlegroups.com.

Re: [sympy] SymPy Wedge Product Question

[Shishir Kushwaha]

Can you please specify what purpose you are using it for. I do not know its 
use yet but would like to get back to you after researching on its usage .

_ _ _ _ _ _ _  
Shishir

On Tuesday 19 March 2024 at 22:54:42 UTC+5:30 giovanni...@gmail.com wrote:

> Can anyone help me with this, please?
>
> On Mon, Mar 11, 2024, 06:06 Giovanni Sutanto  
> wrote:
>
>> Hi SymPy Community,
>>
>> I am now trying to understand what happens when I perform WedgeProduct 
>> operations on SymPy.
>>
>> So, I understand how to use the SymPy's Wedge Product to some extent, 
>> i.e. I was the one who responded to the question on Stack Overflow: 
>> https://stackoverflow.com/questions/76981303/computing-the-wedge-product
>>
>> However, when I have:
>> '''
>> my_matrix = Matrix([[2, 0, 5], [0, 7, 0]])
>> r2_r_oneforms = R2_r.base_oneforms()
>> r2_r_vectors = R2_r.base_vectors()
>>
>> cols = [None] * 3
>> for j in range(3):
>>   cols[j] = 0
>>   for i in range(2):
>> cols[j] += my_matrix[i, j] * r2_r_vectors[i]
>>
>> cols_wedge_product = WedgeProduct(*r2_r_oneforms)(*cols)
>> print('cols_wedge_product = ', cols_wedge_product)
>> '''
>> What I get is:
>> cols_wedge_product = -42
>>
>> Where does the number -42 come from?
>>
>> On the other hand, if:
>> my_matrix = Matrix([[1, 0, 1], [0, 1, 0]])
>> I get:
>> cols_wedge_product = 0
>> What computation leads to 0 here?
>>
>> Can any of you please explain it, e.g. in the terms of the example in the 
>> video lecture https://youtu.be/xRf9-hdxB0w?feature=shared=2961 ?
>>
>> Thanks so much in advance for your time!
>>
>>
>> Best Regards,
>>
>> Giovanni
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "sympy" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/sympy/-MAK_y6-9Yc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> sympy+un...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sympy/b7fb6f7e-232d-4414-b938-1cdbab35cd76n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/e3c35021-3cf3-45ba-9378-56563b582a68n%40googlegroups.com.

[sympy] Re: GSoC prospect interest and a potential issue

[Shishir Kushwaha]

I don't think it is an issue with its consistency. This happens when you're 
using jupyter notebook or google colab. I am not sure if my wording is 
correct but only the last value returned in a code block is printed by the 
notebook. A print statement is treated differently as it prints the value 
and can be included multiple times to print multiple outputs.
__
Shishir Kushwaha
On Thursday 21 March 2024 at 18:28:27 UTC+5:30 sujayhu...@gmail.com wrote:

> Dear mentors,
> I hope this email finds you well. My name is Sujay C Hukkeri , currently 
> pursuing BTech in Chemical Engineering in IIT (BHU) Varanasi.I am reaching 
> out to express my interest in participating in GSoC 2024 and collaborating 
> on a project under your mentorship. 
>
> I have been programming in Python for the past 3 years and have a solid 
> understanding of SQL, C, and mathematics thanks to intensive preparation 
> for the JEE. I am currently learning more about computation libraries of 
> SymPy and exploring their applications.
>
> While exploring the codebase, I noticed some inconsistencies in the output 
> of the limit function compared to the integrate function.  Attaching  the 
> relevant code snippet below. Particularly in the limit function - it does 
> not return the final answer whereas integrate function does, Is this a 
> known issue, or is there a specific reason for this behavior? I'd be happy 
> to delve deeper and contribute to improving the code's consistency. 
>
> Thank you for your time and consideration. 
> Sincerely, 
> Sujay C Hukkeri
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/c9fdc272-c056-404c-ac72-515d86568f6en%40googlegroups.com.

[sympy] Re: Project Idea and Expression of Interest

[Shishir Kushwaha]

I have been working on my proposal for some time, can I please get some 
time from your schedule to get your thoughts and improve on it before the 
final submission? 
I would also like to know if there are some additional ideas I should add 
along with my current proposal. 
If possible where should I send my draft proposal?

Sincerely
Shishir Kushwaha   

On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com wrote:

> Your ideas seem good. The cable class doesn't have a draw method and could 
> use it considering how the other classes do. The ILD functionality does 
> look promising too. 
>
> I haven't heard or read much about Arches as I believe they are inclined 
> towards Civil Engineering and Architecture. I will be interested to see 
> your approach & thoughts and how you structure them in your proposal. 
>
> On Tuesday, March 5, 2024 at 1:25:06 AM UTC+5:30 kushwahas...@gmail.com 
> wrote:
>
>> Respected Sympy community ,
>>
>>
>> My name is Shishir Kushwaha ,currently a sophomore at Indian Institute of 
>> Technology , BHU ,Varanasi , India . I am currently pursuing a degree in 
>> Mathematics and Computing and my interest lies in fields related to 
>> mathematics, physics and machine learning and have worked on honing my 
>> skills in the domains . Having used Sympy to help me through my projects 
>> related to Mechanical Engineering , I found it very useful and would like 
>> to help others in the same way by further improving its features in the 
>> same direction .  
>>
>>
>> I would like to express my interest in contributing to Sympy in the GSoC 
>> 2024 program . The ability to symbolically solve complex problems and 
>> ability to integrate well when needed due to it being coded in pure Python 
>> makes it an exciting project to anyone with a mathematical background . 
>>
>>
>> I looked through the ideas list page and liked a few projects I would 
>> like to work on . I would like to further the module on continuum mechanics 
>> by implementing plotting of draw and tension to the newer Cable Class along 
>> with an influence line diagram functionality . Along with this I hope to 
>> introduce and complete the implementation of structures like Arches 
>> allowing similar functionalities in Beams and Trusses . 
>>
>>
>> I would like to request the mentors Ishan Pandhare , Advait Pote , 
>> Prakhar Saxena to kindly take a look and check if it aligns with the goals 
>> of Sympy and is a suitable idea for GSoC 2024 .
>>
>>
>> I am familiar with Python , Pytorch and JavaScript stacks with experience 
>> in many relevant projects of web development and mathematical 
>> implementations of Digital Image Processing . 
>>
>> I hope my technical skills along with my dedication would allow me to 
>> successfully execute my duties .
>>
>>
>> Thank you for your time and consideration , I hope to work and learn with 
>> the amazing Sympy Community . 
>>
>>
>> Sincerely ,
>>
>> Shishir Kushwaha 
>>
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/f29c6bfa-965e-4120-8518-b31acc390981n%40googlegroups.com.

[sympy] Quantum Physics module issues

[Shishir Kushwaha]

Recently while working through a few issues , I have found a few bugs in 
the code of the quantum module but there does not seem to be any active 
maintainer of that module . Is there any way to resolve those quickly or 
someone who can view the PRs on those changes .

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/32744e76-6fef-45b4-a63d-424f1c4adf80n%40googlegroups.com.

[sympy] Project Idea and Expression of Interest

[Shishir Kushwaha]

Respected Sympy community ,


My name is Shishir Kushwaha ,currently a sophomore at Indian Institute of 
Technology , BHU ,Varanasi , India . I am currently pursuing a degree in 
Mathematics and Computing and my interest lies in fields related to 
mathematics, physics and machine learning and have worked on honing my 
skills in the domains . Having used Sympy to help me through my projects 
related to Mechanical Engineering , I found it very useful and would like 
to help others in the same way by further improving its features in the 
same direction .  


I would like to express my interest in contributing to Sympy in the GSoC 
2024 program . The ability to symbolically solve complex problems and 
ability to integrate well when needed due to it being coded in pure Python 
makes it an exciting project to anyone with a mathematical background . 


I looked through the ideas list page and liked a few projects I would like 
to work on . I would like to further the module on continuum mechanics by 
implementing plotting of draw and tension to the newer Cable Class along 
with an influence line diagram functionality . Along with this I hope to 
introduce and complete the implementation of structures like Arches 
allowing similar functionalities in Beams and Trusses . 


I would like to request the mentors Ishan Pandhare , Advait Pote , Prakhar 
Saxena to kindly take a look and check if it aligns with the goals of Sympy 
and is a suitable idea for GSoC 2024 .


I am familiar with Python , Pytorch and JavaScript stacks with experience 
in many relevant projects of web development and mathematical 
implementations of Digital Image Processing . 

I hope my technical skills along with my dedication would allow me to 
successfully execute my duties .


Thank you for your time and consideration , I hope to work and learn with 
the amazing Sympy Community . 


Sincerely ,

Shishir Kushwaha 


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/4d469512-7bf5-4868-b18e-7b3e3de47276n%40googlegroups.com.

Re: [sympy] Re: ModuleNotFoundError: No module named 'sympy.plotting.series'

[Shishir Kushwaha]

ce(initial_omega, final_omega, 1)
>
> #mag_func = lambdify(_w, mag)
> #phase_func = lambdify(_w, phase)
> hz, mag_points  = LineOver1DRangeSeries(mag, x).get_points()
> rad, phase_points = LineOver1DRangeSeries(phase, x).get_points()
> mag_points = mag_points[0: len(phase_points)] #cut some of the last 
> data of magnitude because len(phase_data) = len(magnitude_data)
>
> return phase_points, mag_points
>
> def nichols_plot(system, initial_omega=0.01, final_omega=100,
>  color='b', grid=False, show=True,**kwargs):
> r"""
> Returns the nichols plot of a continuous-time system.
> Nichols Plot is a plot used in signal processing and control system 
> design
> to determine the stability of a feedback system
> Parameters
> ==
> system : SISOLinearTimeInvariant type
> The LTI SISO system for which the Ramp Response is to be computed.
> initial_omega : Number, optional
> The initial value of frequency. Defaults to 0.01.
> final_omega : Number, optional
> The final value of frequency. Defaults to 100.
> show : boolean, optional
> If ``True``, the plot will be displayed otherwise
> the equivalent matplotlib ``plot`` object will be returned.
> Defaults to True.
> show_axes : boolean, optional
> If ``True``, the coordinate axes will be shown. Defaults to False.
> grid : boolean, optional
> If ``True``, the plot will have a grid. Defaults to False.
> Examples
> 
> .. plot::
> :context: close-figs
> :format: doctest
> :include-source: True
> >>> from sympy.abc import s
> >>> from sympy.physics.control.lti import TransferFunction
> >>> from sympy.physics.control.control_plots import nichols_plot
> >>> tf1 = TransferFunction(-(0.1)*s**3 - (2.4)*s**2 - 181*s - 
> 1950, s**3 + (3.3)*s**2 + 990*s + 2600, s)
> >>> nichols_plot(tf1, 1, 100)   # doctest: +SKIP
> See Also
> 
> bode_magnitude_plot, bode_phase_plot
> References
> ======
> .. [1] https://en.wikipedia.org/wiki/Nichols_plot
> """
> x, y = nichols_numerical_data(system, initial_omega=initial_omega,
>   final_omega=final_omega)
>
> plt.plot(x, y, color=color, **kwargs)
> plt.xlabel('Open Loop Gain (dB)')
> plt.ylabel('Open Loop Phase (deg)')
> plt.title(f'Nichols Plot (Phase) of ${latex(system)}$', pad=20)
> plt.axhline(y=0, color='black', linestyle='dotted', linewidth=1)
>
> if grid:
> plt.grid(True)
>
> if show:
> plt.show()
> return
>
> return plt
>
> nichols_plot(tf1)
>
> Στις Κυρ 3 Μαρ 2024 στις 10:12 μ.μ., ο/η Shishir Kushwaha <
> kushwahas...@gmail.com> έγραψε:
>
>>
>> It is working fine for me in both jupyter notebook and intreactive sympy 
>> shell . Do you mind sharing the full code snippet where you were using it 
>> to cause the error .
>>
>> On Monday 4 March 2024 at 01:34:51 UTC+5:30 tsioupr...@gmail.com wrote:
>>
>>> Author: Spiros Tsioupros
>>> Github: https://github.com/Spiros7bit
>>> email: tsioupr...@gmail.com <https://groups.google.com/>
>>>
>>> Hallo, community, while I was trying to run a program this error popped 
>>> up:
>>>
>>> *from sympy.plotting.series import 
>>> LineOver1DRangeSeriesModuleNotFoundError: No module named 
>>> 'sympy.plotting.series'*
>>>
>>> More specifically, the error is in the line:
>>> from sympy.plotting.series import LineOver1DRangeSeries
>>> ...
>>>
>>> From a small search I did I think the error has to do with the 
>>> interpreter. Any information would be useful.
>>>
>>> More information:
>>> IDE: VSCode
>>> Interpreter: Python Default
>>> OS: Windows 11
>>> sympy 1.12
>>> mpmath 1.3.0
>>> Python 3.10.11
>>>
>>> Yours sincerely.
>>>
>> -- 
>> 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+un...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sympy/38088022-078c-423c-b22c-219705bf03e8n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sympy/38088022-078c-423c-b22c-219705bf03e8n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/4aa8338d-823a-43d3-840a-7e5283793b32n%40googlegroups.com.

[sympy] Re: ModuleNotFoundError: No module named 'sympy.plotting.series'

[Shishir Kushwaha]

It is working fine for me in both jupyter notebook and intreactive sympy 
shell . Do you mind sharing the full code snippet where you were using it 
to cause the error .

On Monday 4 March 2024 at 01:34:51 UTC+5:30 tsioupr...@gmail.com wrote:

> Author: Spiros Tsioupros
> Github: https://github.com/Spiros7bit
> email: tsioupr...@gmail.com 
>
> Hallo, community, while I was trying to run a program this error popped up:
>
> *from sympy.plotting.series import 
> LineOver1DRangeSeriesModuleNotFoundError: No module named 
> 'sympy.plotting.series'*
>
> More specifically, the error is in the line:
> from sympy.plotting.series import LineOver1DRangeSeries
> ...
>
> From a small search I did I think the error has to do with the 
> interpreter. Any information would be useful.
>
> More information:
> IDE: VSCode
> Interpreter: Python Default
> OS: Windows 11
> sympy 1.12
> mpmath 1.3.0
> Python 3.10.11
>
> Yours sincerely.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/38088022-078c-423c-b22c-219705bf03e8n%40googlegroups.com.

Re: [sympy] Use of flake8 seperately when we have ruff enabled

[Shishir Kushwaha]

There is a PR open <https://github.com/sympy/sympy/pull/26225> for config 
files for ruff for the issue of slotchecks ,
Would you please take a look into it , it might be related to this thread 
as well .
Almost all the things mentioned in the .flake8 file is also present in the 
ruff section . Kindly check if something is missing or if flake8 checks are 
being covered by ruff.

Shishir

On Friday 16 February 2024 at 06:37:18 UTC+5:30 asme...@gmail.com wrote:

> I think maybe there were some checks that were done by flake8 that
> weren't yet implemented by ruff. I don't know if that's still the
> case. I agree we could probably just use ruff if it is doing
> everything flake8 does.
>
> Aaron Meurer
>
> On Thu, Feb 15, 2024 at 6:50 AM Shishir Kushwaha
>  wrote:
> >
> > I was going through the pyproject.toml file and learned that we are 
> using ruff which is also a test or part of a test that runs on github CLI . 
> In the documentation as well as github CLI we are using ruff which can be 
> used to replace flake8 from what I have read .
> > In that case why do we use both of them when the work could just be done 
> with ruff .
> >
> > _
> > Shishir Kushwaha
> >
> > --
> > 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+un...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/33ecc4b9-d500-4233-ad3b-2ff5df3e56dbn%40googlegroups.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/bb116728-d2a5-4da0-88cb-e1d27188dbecn%40googlegroups.com.

[sympy] Use of flake8 seperately when we have ruff enabled

[Shishir Kushwaha]

I was going through the pyproject.toml file and learned that we are using 
ruff which is also a test or part of a test that runs on github CLI . In 
the documentation as well as github CLI we are using ruff which can be used 
to replace flake8 from what I have read . 
In that case why do we use both of them when the work could just be done 
with ruff .

_
Shishir Kushwaha

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/33ecc4b9-d500-4233-ad3b-2ff5df3e56dbn%40googlegroups.com.

Re: [sympy] Code Quality test failing on github even though local tests doesn't give any error

[Shishir Kushwaha]

I have opened a PR which potentially fixes the issue , however the warnign 
about the deprecated modules remain kindly check it out . Do we need to fix 
that too by replacing them with correct modules for the required places .

Shishir

On Tuesday 13 February 2024 at 11:37:06 UTC+5:30 himat...@gmail.com wrote:

> So If I'm not wrong we have to create a new configuration file right?
>  
>
> On Tuesday 13 February 2024 at 03:36:24 UTC+5:30 asme...@gmail.com wrote:
>
>> The slotscheck command should be ran like 
>>
>> python -m slotscheck --exclude-modules 
>> "(sympy.parsing.autolev._antlr.*|sympy.parsing.latex._antlr.*|sympy.galgebra|sympy.plotting.pygletplot.*)"
>>  
>>
>> sympy 
>>
>> (see 
>> https://github.com/sympy/sympy/blob/680fb21363e1ea685d6fc868d15069d80ac0c97f/.github/workflows/runtests.yml#L47C14-L47C165).
>>  
>>
>> Otherwise it will try to import several submodules which should not be 
>> imported. 
>>
>> Really we should move this to a configuration file so that it will 
>> always work correctly if you just call "slotscheck". See 
>>
>> https://slotscheck.readthedocs.io/en/latest/configuration.html#configuration-file.
>>  
>>
>> This should be a straightforward thing to change if you want to make a 
>> PR. 
>>
>> Aaron Meurer 
>>
>> On Fri, Feb 9, 2024 at 3:51 PM Shishir Kushwaha 
>>  wrote: 
>> > 
>> > I am getting the same errors on the master branch as well . Has it got 
>> something to do with the dependencies ? I set up my repo again after 
>> clearing previous stuff so I might have forgotten something ? 
>> > 
>> > 
>> > 
>> > On Saturday 10 February 2024 at 04:18:48 UTC+5:30 Shishir Kushwaha 
>> wrote: 
>> >> 
>> >> Can you also please tell me why it is failing as well . The errors I 
>> get are mostly some warning about deprecation or failing to import some 
>> modules but I have made no changes to any of the related files and synced 
>> with the upstream repository about an hour ago . 
>> >> 
>> >> The output I get on running the test locally : 
>> >> 
>> >> The sympy.utilities.runtests submodule is deprecated. Use 
>> sympy.testing.runtests instead. 
>> >> 
>> >> See 
>> https://docs.sympy.org/latest/explanation/active-deprecations.html#deprecated-sympy-utilities-submodules
>>  
>> >> for details. 
>> >> 
>> >> This has been deprecated since SymPy version 1.6. It 
>> >> will be removed in a future version of SymPy. 
>> >> 
>> >> return _bootstrap._gcd_import(name[level:], package, level) 
>> >> ERROR: Failed to import 'sympy.galgebra'. 
>> >> ERROR: Failed to import 'sympy.parsing.autolev._antlr.autolevlexer'. 
>> >> ERROR: Failed to import 
>> 'sympy.parsing.autolev._antlr.autolevlistener'. 
>> >> ERROR: Failed to import 'sympy.parsing.autolev._antlr.autolevparser'. 
>> >> ERROR: Failed to import 'sympy.parsing.latex._antlr.latexlexer'. 
>> >> ERROR: Failed to import 'sympy.parsing.latex._antlr.latexparser'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.color_scheme'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.managed_window'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot_controller'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot_controller'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot_curve'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot_mode'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot_mode_base'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot_modes'. 
>> >> ERROR: Failed to import 
>> 'sympy.plotting.pygletplot.plot_rotation'.ERROR: Failed to import 
>> 'sympy.plotting.pygletplot.plot_surface'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.plot_window'. 
>> >> ERROR: Failed to import 'sympy.plotting.pygletplot.util'. 
>> >> Oh no, found some problems! 
>> >> Scanned 1501 module(s), 1923 class(es). 
>> >> On Saturday 10 February 2024 at 03:33:43 UTC+5:30 asme...@gmail.com 
>> wrote: 
>> >>> 
>> >>> The slotscheck test is run on CI but isn't included in the normal 
>> >>> local tests run. If you want to run it locally you will need to 
>> >>> install slotscheck and run 'sl

Re: [sympy] Code Quality test failing on github even though local tests doesn't give any error

[Shishir Kushwaha]

I am getting the same errors on the master branch as well . Has it got 
something to do with the dependencies ? I set up my repo again after 
clearing previous stuff so I might have forgotten something ?



On Saturday 10 February 2024 at 04:18:48 UTC+5:30 Shishir Kushwaha wrote:

> Can you also please tell me why it is failing as well . The errors I get 
> are mostly some warning about deprecation or failing to import some modules 
> but I have made no changes to any of the related files and synced with the 
> upstream repository about an hour ago .
>
> The output I get on running the test locally :
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *The sympy.utilities.runtests submodule is deprecated. Use 
> sympy.testing.runtests instead.See 
> https://docs.sympy.org/latest/explanation/active-deprecations.html#deprecated-sympy-utilities-submodules
>  
> <https://docs.sympy.org/latest/explanation/active-deprecations.html#deprecated-sympy-utilities-submodules>for
>  
> details.This has been deprecated since SymPy version 1.6. Itwill be removed 
> in a future version of SymPy.  return _bootstrap._gcd_import(name[level:], 
> package, level) ERROR: Failed to import 'sympy.galgebra'.ERROR: Failed 
> to import 'sympy.parsing.autolev._antlr.autolevlexer'.ERROR: Failed to 
> import 'sympy.parsing.autolev._antlr.autolevlistener'.ERROR: Failed to 
> import 'sympy.parsing.autolev._antlr.autolevparser'.ERROR: Failed to import 
> 'sympy.parsing.latex._antlr.latexlexer'.  ERROR: Failed to import 
> 'sympy.parsing.latex._antlr.latexparser'. ERROR: Failed to import 
> 'sympy.plotting.pygletplot.color_scheme'. ERROR: Failed to import 
> 'sympy.plotting.pygletplot.managed_window'.ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot'.ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_controller'.ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_controller'.  ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_curve'.   ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_mode'.ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_mode_base'.   ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_modes'.   ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_rotation'.ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_surface'.ERROR: Failed to import 
> 'sympy.plotting.pygletplot.plot_window'.  ERROR: Failed to import 
> 'sympy.plotting.pygletplot.util'.Oh no, found some problems!Scanned 1501 
> module(s), 1923 class(es).*
> On Saturday 10 February 2024 at 03:33:43 UTC+5:30 asme...@gmail.com wrote:
>
>> The slotscheck test is run on CI but isn't included in the normal 
>> local tests run. If you want to run it locally you will need to 
>> install slotscheck and run 'slotscheck sympy/' 
>>
>> Aaron Meurer 
>>
>> On Fri, Feb 9, 2024 at 2:02 PM Shishir Kushwaha 
>>  wrote: 
>> > 
>> > I am getting an error in 
>> > Check for incorrect use of "__slots__" using slotcheck . 
>> > Any Idea why ? 
>> > 
>> > -- 
>> > 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+un...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sympy/9ca60097-eb28-436e-9c29-79eae93edf83n%40googlegroups.com.
>>  
>>
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/cf63fea5-46f0-49cc-a0aa-aa9a0b2b9c75n%40googlegroups.com.

Re: [sympy] Code Quality test failing on github even though local tests doesn't give any error

[Shishir Kushwaha]

Can you also please tell me why it is failing as well . The errors I get 
are mostly some warning about deprecation or failing to import some modules 
but I have made no changes to any of the related files and synced with the 
upstream repository about an hour ago .

The output I get on running the test locally :





























*The sympy.utilities.runtests submodule is deprecated. Use 
sympy.testing.runtests instead.See 
https://docs.sympy.org/latest/explanation/active-deprecations.html#deprecated-sympy-utilities-submodulesfor
 
details.This has been deprecated since SymPy version 1.6. Itwill be removed 
in a future version of SymPy.  return _bootstrap._gcd_import(name[level:], 
package, level) ERROR: Failed to import 'sympy.galgebra'.ERROR: Failed 
to import 'sympy.parsing.autolev._antlr.autolevlexer'.ERROR: Failed to 
import 'sympy.parsing.autolev._antlr.autolevlistener'.ERROR: Failed to 
import 'sympy.parsing.autolev._antlr.autolevparser'.ERROR: Failed to import 
'sympy.parsing.latex._antlr.latexlexer'.  ERROR: Failed to import 
'sympy.parsing.latex._antlr.latexparser'. ERROR: Failed to import 
'sympy.plotting.pygletplot.color_scheme'. ERROR: Failed to import 
'sympy.plotting.pygletplot.managed_window'.ERROR: Failed to import 
'sympy.plotting.pygletplot.plot'.ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_controller'.ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_controller'.  ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_curve'.   ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_mode'.ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_mode_base'.   ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_modes'.   ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_rotation'.ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_surface'.ERROR: Failed to import 
'sympy.plotting.pygletplot.plot_window'.  ERROR: Failed to import 
'sympy.plotting.pygletplot.util'.Oh no, found some problems!Scanned 1501 
module(s), 1923 class(es).*
On Saturday 10 February 2024 at 03:33:43 UTC+5:30 asme...@gmail.com wrote:

> The slotscheck test is run on CI but isn't included in the normal
> local tests run. If you want to run it locally you will need to
> install slotscheck and run 'slotscheck sympy/'
>
> Aaron Meurer
>
> On Fri, Feb 9, 2024 at 2:02 PM Shishir Kushwaha
>  wrote:
> >
> > I am getting an error in
> > Check for incorrect use of "__slots__" using slotcheck .
> > Any Idea why ?
> >
> > --
> > 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+un...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/9ca60097-eb28-436e-9c29-79eae93edf83n%40googlegroups.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/c54fcc72-f543-4c5e-b087-529abafc5c9bn%40googlegroups.com.

[sympy] Code Quality test failing on github even though local tests doesn't give any error

[Shishir Kushwaha]

I am getting an error in 
Check for incorrect use of "__slots__" using slotcheck . 
Any Idea why ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/9ca60097-eb28-436e-9c29-79eae93edf83n%40googlegroups.com.

[sympy] What's the Meaning of S and X while running tests .

[Shishir Kushwaha]

S and X have been coming on a few test when I ran tests , they did even 
when I was setting sympy up , why is it happening . I tried reinstalling 
thee dependancies and checked the versions required . Althoough no test is 
failing with a F but I'm still getting 'skipped' and 'xfailed tests'.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/d500691b-1b97-4b7e-8b2f-fb5f74341958n%40googlegroups.com.

Re: [sympy] Closing Old Issues

[Shishir Kushwaha]

There are a few open issues where the solution to the problem of the author 
has been provided by a contributor or a member , those solutions maybe 
helpful to others in the future , so do they need to remain open or we make 
a comment to close them . Do you think it would be better if we added those 
solutions to a file like a guide ? 
On Tuesday 6 February 2024 at 17:43:22 UTC+5:30 Oscar wrote:

> On Tue, 6 Feb 2024 at 07:42, Shishir Kushwaha
>  wrote:
> >
> > I was going over the open issues i could potentially solve and I think 
> some of them are still open after their solution PR has been merged. What 
> do I do about those issues . Should I leave a comment on the issue on its 
> closing or ask what needs to be done ?
>
> Sometimes an issue that should have been closed gets forgotten when a
> PR is merged. Also sometimes there are several PRs for the same issue
> and once one is merged the others should be closed but this can also
> be missed. In either case it is useful to comment on the issue or PR
> pointing out that it could be closed.
>
> Please include information showing how to demonstrate that the problem
> is fixed and mention that the PR that was merged has a test for the
> issue or point to where the issue is tested in the codebase. Basically
> include enough information that it is easy for someone else to read
> your comment and then confirm that it should be closed.
>
> --
> Oscar
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/d3f66066-8741-4825-913b-0deba2168061n%40googlegroups.com.

Re: [sympy] Reviewing PRs and old SymPy issues

['Shishir Kushwaha 5-Yr IDD: Mathematical Sci.s, IIT(BHU)' via sympy]

Wouldn't creating another PR add to the problem of checking more PRs?

On Tue, 6 Feb 2024, 5:52 pm Mohit Kumar,  wrote:

> I have found some old opened issues that should be closed, so, is it a
> good idea to open a new PR (which has title like "CLOSED [issue]..." with a
> test, if similar tests do not exists) or creating a new conversation here,
> IMO PR is a better option. PRs with title like CLOSED [issue].. could be
> prioritized?
>
> On Tuesday 6 February 2024 at 17:37:13 UTC+5:30 kushwahas...@gmail.com
> wrote:
>
>> Do you have some guidelines you follow or just some general advice for
>> people who are willing to do that work . It will also help new contributors
>> like me understand what things need to be checked apart from the ones
>> mentioned in the developer documentation before I make a pull request .
>>
>> Shishir
>> On Tuesday 6 February 2024 at 17:30:01 UTC+5:30 Oscar wrote:
>>
>>> Perhaps other things should be mentioned in the GSOC application
>>> instructions. I do think that the PR requirement is reasonable as a
>>> baseline for GSOC though.
>>>
>>> To be clear opening pull requests is a good thing. Reviewing pull
>>> requests is a lot of work for maintainers though. If lots of people
>>> start opening PRs but not doing anything else to help by e.g.
>>> reviewing those PRs then we will just have lots of unreviewed PRs
>>> which is not so useful. Especially many of these PRs have very basic
>>> problems like "a test should be added" or "the test should be for what
>>> is actually fixed". These could easily be reviewed by many of the new
>>> contributors.
>>>
>>> This PR is a good example of the work problem that is created by
>>> opening PRs rather than reviewing them:
>>> https://github.com/sympy/sympy/pull/26117
>>>
>>> What is needed is for someone to verify that the definition of
>>> assoc_legendre as used in SymPy matches with the definition that is
>>> used in mpmath. This is partly about reading the docs and partly just
>>> a case of doing some numerical checks but it needs to be done
>>> systematically paying close attention to any special values and to
>>> what SymPy's symbolic evaluation handles. Writing the code and opening
>>> the PR without doing that checking leaves all of the work to the
>>> reviewer. Anyone else could review it though by doing that checking.
>>>
>>> --
>>> Oscar
>>>
>>> On Tue, 6 Feb 2024 at 07:59, Jason Moore  wrote:
>>> >
>>> > Note that we get lots of PRs at this time because we require GSoC
>>> applicants to have at least one merged PR. We could encourage the other
>>> activities if we allow those to fulfill the requirement for the GSoC
>>> application.
>>> >
>>> > Jason
>>> >
>>> >
>>> > On Tue, Feb 6, 2024 at 6:05 AM Aaron Meurer 
>>> wrote:
>>> >>
>>> >> I'll also add that if you want to, we'll give triage permissions to
>>> >> just about anyone so they can go through and label old issues (triage
>>> >> permissions give you permissions to label issues). Just ask me or
>>> >> Oscar.
>>> >>
>>> >> Aaron Meurer
>>> >>
>>> >> On Mon, Feb 5, 2024 at 2:25 PM Oscar Benjamin
>>> >>  wrote:
>>> >> >
>>> >> > Hi all,
>>> >> >
>>> >> > There are currently a large number of new contributors opening
>>> various
>>> >> > pull requests and commenting on issues in the SymPy repo. This is
>>> >> > great to see, and I want to thank everyone who has been
>>> contributing.
>>> >> >
>>> >> > I would like to highlight though that opening pull requests is not
>>> the
>>> >> > only way to contribute to SymPy. There are many other ways to
>>> >> > contribute. In fact more important than opening pull requests is
>>> >> > *reviewing* pull requests and issues. For example if you can see
>>> that
>>> >> > a pull request likely needs some changes, then it is helpful to
>>> >> > comment on the pull request and suggest what changes are needed
>>> until
>>> >> > it looks ready to merge. I am sure that some of the new
>>> contributors
>>> >> > could tell quite quickly what changes would be needed in many of
>>> the
>>> >> > recently opened pull requests.
>>> >> >
>>> >> > In fact one of the most useful things that a relatively new
>>> >> > contributor can do is to review old issues. The SymPy repo
>>> currently
>>> >> > has over 4000 open issues. Many of these are old and are no longer
>>> >> > relevant or already fixed. You can often review these issues just
>>> by
>>> >> > testing the code in them. If the issue seems to be fixed then a
>>> pull
>>> >> > request with a test could be opened to close the issue. If you do
>>> want
>>> >> > to review old issues then I suggest using the issue labels to focus
>>> on
>>> >> > a particular area of the code base like "integrals" or "solvers"
>>> etc.
>>> >> >
>>> >> > This sort of work is actually much more helpful to the project than
>>> >> > opening pull requests for "easy to fix" issues.
>>> >> >
>>> >> > --
>>> >> > Oscar
>>> >> >
>>> >> > --
>>> >> > You received this message because you are subscribed to the Google
>>> Groups 

Re: [sympy] Reviewing PRs and old SymPy issues

[Shishir Kushwaha]

Do you have some guidelines you follow or just some general advice for 
people who are willing to do that work . It will also help new contributors 
like me understand what things need to be checked apart from the ones 
mentioned in the developer documentation before I make a pull request .  

Shishir
On Tuesday 6 February 2024 at 17:30:01 UTC+5:30 Oscar wrote:

> Perhaps other things should be mentioned in the GSOC application
> instructions. I do think that the PR requirement is reasonable as a
> baseline for GSOC though.
>
> To be clear opening pull requests is a good thing. Reviewing pull
> requests is a lot of work for maintainers though. If lots of people
> start opening PRs but not doing anything else to help by e.g.
> reviewing those PRs then we will just have lots of unreviewed PRs
> which is not so useful. Especially many of these PRs have very basic
> problems like "a test should be added" or "the test should be for what
> is actually fixed". These could easily be reviewed by many of the new
> contributors.
>
> This PR is a good example of the work problem that is created by
> opening PRs rather than reviewing them:
> https://github.com/sympy/sympy/pull/26117
>
> What is needed is for someone to verify that the definition of
> assoc_legendre as used in SymPy matches with the definition that is
> used in mpmath. This is partly about reading the docs and partly just
> a case of doing some numerical checks but it needs to be done
> systematically paying close attention to any special values and to
> what SymPy's symbolic evaluation handles. Writing the code and opening
> the PR without doing that checking leaves all of the work to the
> reviewer. Anyone else could review it though by doing that checking.
>
> --
> Oscar
>
> On Tue, 6 Feb 2024 at 07:59, Jason Moore  wrote:
> >
> > Note that we get lots of PRs at this time because we require GSoC 
> applicants to have at least one merged PR. We could encourage the other 
> activities if we allow those to fulfill the requirement for the GSoC 
> application.
> >
> > Jason
> >
> >
> > On Tue, Feb 6, 2024 at 6:05 AM Aaron Meurer  wrote:
> >>
> >> I'll also add that if you want to, we'll give triage permissions to
> >> just about anyone so they can go through and label old issues (triage
> >> permissions give you permissions to label issues). Just ask me or
> >> Oscar.
> >>
> >> Aaron Meurer
> >>
> >> On Mon, Feb 5, 2024 at 2:25 PM Oscar Benjamin
> >>  wrote:
> >> >
> >> > Hi all,
> >> >
> >> > There are currently a large number of new contributors opening various
> >> > pull requests and commenting on issues in the SymPy repo. This is
> >> > great to see, and I want to thank everyone who has been contributing.
> >> >
> >> > I would like to highlight though that opening pull requests is not the
> >> > only way to contribute to SymPy. There are many other ways to
> >> > contribute. In fact more important than opening pull requests is
> >> > *reviewing* pull requests and issues. For example if you can see that
> >> > a pull request likely needs some changes, then it is helpful to
> >> > comment on the pull request and suggest what changes are needed until
> >> > it looks ready to merge. I am sure that some of the new contributors
> >> > could tell quite quickly what changes would be needed in many of the
> >> > recently opened pull requests.
> >> >
> >> > In fact one of the most useful things that a relatively new
> >> > contributor can do is to review old issues. The SymPy repo currently
> >> > has over 4000 open issues. Many of these are old and are no longer
> >> > relevant or already fixed. You can often review these issues just by
> >> > testing the code in them. If the issue seems to be fixed then a pull
> >> > request with a test could be opened to close the issue. If you do want
> >> > to review old issues then I suggest using the issue labels to focus on
> >> > a particular area of the code base like "integrals" or "solvers" etc.
> >> >
> >> > This sort of work is actually much more helpful to the project than
> >> > opening pull requests for "easy to fix" issues.
> >> >
> >> > --
> >> > Oscar
> >> >
> >> > --
> >> > 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+un...@googlegroups.com.
> >> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/CAHVvXxQFLH7L%3DjO8EosasVETJn1fCmWaCvbYp%3DMbxvQmg1pB9Q%40mail.gmail.com
> .
> >>
> >> --
> >> 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+un...@googlegroups.com.
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2B8WUQJa_d%2BATjAekCbRgi4D6XCevJqiCmf0EsieSf8gQ%40mail.gmail.com
> .
> >
> > --
> > You received this message because you are 

[sympy] Closing Old Issues

[Shishir Kushwaha]

I was going over the open issues i could potentially solve and I think some 
of them are still open after their solution PR has been merged. What do I 
do about those issues . Should I leave a comment on the issue on its 
closing or ask what needs to be done ?

Shishir Kushwaha

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/0b55b753-f324-46d4-aea9-da993c498ab6n%40googlegroups.com.

Re: [sympy] Reviewing PRs and old SymPy issues

[Shishir Kushwaha]

Sir , I'd like to review and test pull request,  kindly give me the triage
access for labelling . Github ID - shishir-11

On Tue, 6 Feb, 2024, 10:35 Aaron Meurer,  wrote:

> I'll also add that if you want to, we'll give triage permissions to
> just about anyone so they can go through and label old issues (triage
> permissions give you permissions to label issues). Just ask me or
> Oscar.
>
> Aaron Meurer
>
> On Mon, Feb 5, 2024 at 2:25 PM Oscar Benjamin
>  wrote:
> >
> > Hi all,
> >
> > There are currently a large number of new contributors opening various
> > pull requests and commenting on issues in the SymPy repo. This is
> > great to see, and I want to thank everyone who has been contributing.
> >
> > I would like to highlight though that opening pull requests is not the
> > only way to contribute to SymPy. There are many other ways to
> > contribute. In fact more important than opening pull requests is
> > *reviewing* pull requests and issues. For example if you can see that
> > a pull request likely needs some changes, then it is helpful to
> > comment on the pull request and suggest what changes are needed until
> > it looks ready to merge. I am sure that some of the new contributors
> > could tell quite quickly what changes would be needed in many of the
> > recently opened pull requests.
> >
> > In fact one of the most useful things that a relatively new
> > contributor can do is to review old issues. The SymPy repo currently
> > has over 4000 open issues. Many of these are old and are no longer
> > relevant or already fixed. You can often review these issues just by
> > testing the code in them. If the issue seems to be fixed then a pull
> > request with a test could be opened to close the issue. If you do want
> > to review old issues then I suggest using the issue labels to focus on
> > a particular area of the code base like "integrals" or "solvers" etc.
> >
> > This sort of work is actually much more helpful to the project than
> > opening pull requests for "easy to fix" issues.
> >
> > --
> > Oscar
> >
> > --
> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/CAHVvXxQFLH7L%3DjO8EosasVETJn1fCmWaCvbYp%3DMbxvQmg1pB9Q%40mail.gmail.com
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2B8WUQJa_d%2BATjAekCbRgi4D6XCevJqiCmf0EsieSf8gQ%40mail.gmail.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAMK%3DAf2a8W9q%3DKjF5V99Z4Mh-78ttnuS4%2BmBabZojPANnMnmQA%40mail.gmail.com.

Re: [sympy] Doubt Regarding .mailmap file

[Shishir Kushwaha]

Yes i forgot to sync with the upstream before creating the changes , It is 
solved now . Thank you for your time and help .

On Saturday 3 February 2024 at 04:01:06 UTC+5:30 Oscar wrote:

> It's hard to tell from a screenshot. Do you have a link to the PR?
>
> On Fri, 2 Feb 2024 at 17:36, Shishir Kushwaha
>  wrote:
> >
> > Do I need to add my details everytime to thee .mailmap file when making 
> a PR , I did it in my first PR as mentioned in the documentation but when 
> creating a new comitt on another issue , the authro test was failing even 
> though my name is there in the file already . Any idea why this could 
> happen?
> >
> >
> > --
> > 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+un...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/d9705b06-6ca2-49af-9648-e0f23499a6b7n%40googlegroups.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/807b7561-5834-4aa5-ab66-5d9cdb5ba8e2n%40googlegroups.com.

[sympy] Doubt Regarding .mailmap file

[Shishir Kushwaha]

Do I need to add my details everytime to thee .mailmap file when making a 
PR , I did it in my first PR as mentioned in the documentation but when 
creating a new comitt on another issue , the authro test was failing even 
though my name is there in the file already . Any idea why this could 
happen?
 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/d9705b06-6ca2-49af-9648-e0f23499a6b7n%40googlegroups.com.

Re: [sympy] Please help me setup documentation

[Shishir Kushwaha]

Yes that's what I did , I followed the steps mentioned in the documentation 
and got this error . 
However trying to build the docs with sphinx with a seperate command was 
successfull , I'm trying to figure out what to do next .
On Thursday 1 February 2024 at 00:53:11 UTC+5:30 asme...@gmail.com wrote:

> How are you running the docker container? You need to run
>
> docker run --rm -v /absolute/path/to/SYMPY_ROOT:/sympy sympy_htmldoc
>
> where you replace /absolute/path/to/SYMPY_ROOT with the path to your
> sympy git clone directory.
>
> Or alternatively, you can just install the docs dependencies directly
> to your local environment and build without using docker.
>
> Aaron Meurer
>
> On Wed, Jan 31, 2024 at 1:43 AM Shishir Kushwaha
>  wrote:
> >
> > I was trying to build documentation using docker and on running the 
> commands mentioned in the documentation , I was getting this error .
> >
> > /usr/local/bin/makehtml.sh: line 7: cd: /sympy/doc: No such file or 
> directory
> > make: *** No rule to make target 'html'. Stop.
> >
> > --
> > 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+un...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/1a978660-0dd2-49d8-8478-185ad7175ed3n%40googlegroups.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/b4fd809f-fb9b-4213-8815-ea5a341dd906n%40googlegroups.com.

[sympy] Please help me setup documentation

[Shishir Kushwaha]

I was trying to build documentation using docker and on running the 
commands mentioned in the documentation , I was getting this error .

/usr/local/bin/makehtml.sh: line 7: cd: /sympy/doc: No such file or 
directory
make: *** No rule to make target 'html'.  Stop.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/1a978660-0dd2-49d8-8478-185ad7175ed3n%40googlegroups.com.

[sympy] Interest in Contributing to Sympy Projects

['Shishir Kushwaha 5-Yr IDD: Mathematical Sci.s, IIT(BHU)' via sympy]

My greetings to all the respected contributors and admins . 

I am Shishir Kushwaha , a sophomore at Indian Institute of Technology 
Varanasi pursuing Mathematics and Computing Degree . I am familiar with the 
concepts in mathematics and am a new developer and wish to learn more and 
contribute to the organization.

I have gone through the developer docs once and understood the gist of most 
of the content . I would be grateful if someone could  give me some clear 
steps on what to do to contribute to the org after i have setup the 
repository.

Thank You

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/85c47005-8647-4305-ad72-007d9de834efn%40googlegroups.com.