symengine.py ABI3 wheels and 3.14t wheels are available

Hi, I just uploaded ABI3 wheels supporting python>=3.11 and also 3.14 free-threaded wheels to the

Access to SymEngine C++ object from the corresponding Python wrappers

Hello together, I have asked a question at stackoverflow and also wanted to post it here: https://

(De) Serializing a list a expressions and memory usage

Thank you so much. This PR solves the memory usage problem completely! I used the vec_basic version

Solving Condition Sets in C++

Hi Ramon, Go ahead and open up an issue with this feature request. Ondrej On Wed, Oct 16, 2024, at 10

De-serializing expressions with MPFR crashes

Hi Saleh, This should be fixed in https://github.com/symengine/symengine/pull/2013 Isuru On Mon, Apr

OCaml bindings?

Hello, Is there any way someone could tell me which languages are supported? I see a few but not a

Does SymEngine have an internal malloc function

Hi Anutosh, On Sat, Jul 15, 2023, at 12:34 AM, Anutosh Bhat wrote: > Hello all, > > I am

Hash collisions and SymEngine

Hi Saleh, Welcome to the symengine mailing list. Hash collisions are unavoidable and modifying the

SymEngine v0.10 released

Hi, I've just released symengine v0.10.1 and symengine.py v0.10.0. symengine v0.10.0 released on

[SymEngine.jl] method to parse string in SymEngine.jl

Hi Constantinos, We don't have dedicated developers for SymEngine.jl. The best way to proceed is

berkowitz method in symengine

Hi Sally, On Tue, Feb 7, 2023, at 12:47 PM, Sally Thu wrote: > Hi, > > I would like to

solve command in Symengine

Hello, I have such a code. I want to write this with symengine. How can I do it ? I will be glad if

Re: [sympy] Faster symbolics

Hi, I am CCing the symengine list also. Let me say a few words about the design and goals of

SymEngine v0.8 released

It is my pleasure to announce SymEngine release v0.8. After releasing v0.8.0, we found a compilation

Questions about SymEngine.jl

I am trying to use the package SymEngine.jl (running with julia 1.5.2 on a linux machine). Any

Security issue with symengine 0.7.0 macosx wheels fixed with 0.7.0.post3

symengine 0.7.0 macosx wheels had a security issue and if you have downloaded macosx wheels (x86_64

symengine.py v0.7.0 is released

It is my pleasure to announce that symengine.py v0.7.0 is released and is available through PyPI as a

SymEngine v0.7.0 released

On Sat, Mar 13, 2021, at 8:55 PM, Isuru Fernando wrote: > It is my pleasure to announce that

prebuilt wheel for ARM machines

Hi Daniel, On Wed, Mar 3, 2021, at 2:47 PM, Daniel R. Shapero wrote: > TL;DR: It would be great if

internal representation

Hi Daniel, On Tue, Dec 29, 2020, at 12:29 PM, Daniel R. Shapero wrote: > > Hi all -- I was

Status of RUBI integrator

Hi Ondrej, My vacation starts in about 2 weeks, so meanwhile I'll go through the code properly

GSoD Announcement

Hi Rohit, On Thu, Nov 12, 2020 at 10:19 AM Rohit Goswami <r95...@gmail.com> wrote: Hi Isuru, I

Q: current symengine and python-symengine versions on conda-forge

Hello, 'conda info' active environment : base active env location : /home/audrius/anaconda3

expanding trig function calls into radicals

On Thu, Jun 25, 2020 at 8:49 AM Joe Wezorek <jwez...@gmail.com> wrote: Looks like there

Getting STL container of variables in SymEngine::Expression

Excellent, thank you very much! On Tuesday, 26 May 2020 16:47:21 UTC-4, Isuru Fernando wrote: Hi, You

factorization of polynomials

Hi Aaron, Wow you were totally right. If I apply .as_numer_denom() & factor_terms() then it

ValueError: setting an array element with a sequence.

Hi, Looks like this is a problem with broadcasting one input. For example, the following works,

Installing symengine-0.1.0.gem fails

On Fri, May 1, 2020, at 2:02 AM, Valderane Potong wrote: > Thank you ondrej for replying. >

how to correctly use relational operators

This works. thanks. Joe On Monday, March 2, 2020 at 1:24:19 PM UTC-8, Isuru Fernando wrote: Try, se::

Fast code based on symbolic manipulations

On Mon, Feb 24, 2020, at 11:52 AM, Nathan Woods wrote: > Thanks for your response. > > I