I wouldn't call it 'stupid.' There is nothing sublime about 'symbols', it just involve string parsing and array handling compared to Symbol. Some programmers would rather argue that such stuff are adding unnecessary overheads. On Monday, June 23, 2025 at 5:56:35 PM UTC+2 [email protected] wrote:
> You're right that it can be confusing. The function symbols() does do > basically what you said, and it's the function we generally recommend > using. > > The reason there is also Symbol() is because Symbol is the class for > symbol objects, and you can create symbol objects directly with the > class constructor. But you only ever need to use the class name Symbol > if you're doing something that requires the class, like isinstance(). > > Aaron Meurer > > On Mon, Jun 23, 2025 at 9:52 AM Stephen Learmonth > <[email protected]> wrote: > > > > Why-oh-why are there these two functions for creating a single Sympy > symbol or mutliple Sympy symbols. > > > > This is so stupid and confusing! > > > > Why not just have ONE function called symbols(...) and let the function > definition figure out how many symbols you want to create! > > > > This is soooo confusing!!! > > > > -- > > 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 [email protected]. > > To view this discussion visit > https://groups.google.com/d/msgid/sympy/cd6d1ad8-4a21-4024-8f3f-86f480757e26n%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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sympy/3d4c8947-d56a-4656-a7ba-c75bf66aec2fn%40googlegroups.com.
