SLICOT C11 Translation with Python Bindings - Now Available on PyPI

[jamestjsp]

I'm excited to share that I've completed a full translation of the SLICOT library from Fortran to C11, along with Python bindings. The package is now published on PyPI.

Project Overview

• Repository: https://github.com/jamestjsp/slicot
• PyPI Package: https://pypi.org/project/slicot/
• Version: 1.0.0

What's Included

• 624 C source files translated from the original Fortran routines
• 160+ Python-wrapped functions with NumPy integration
• Coverage across all major SLICOT categories:
  • AB, AG (Analysis)
  • BB, BD (Benchmark/Data)
  • DE, DF, DG, DK (Descriptor systems)
  • FB, FD (Factorizations)
  • MA, MB, MC, MD (Matrix operations)
  • NF (Numerical functions)
  • SB, SG (State-space)
  • TB, TC, TD, TF, TG (Transformations)
  • UD, UE (Utilities)

Installation

pip install slicot

Pre-built wheels available for:

• Linux (x86_64, manylinux2014)
• macOS (ARM64)
• Windows (x86_64)
• Python 3.11, 3.12, 3.13

OpenBLAS is bundled - no external BLAS/LAPACK installation required.

Quick Example

  import numpy as np                                                                                                                                                                                                                                                         
  from slicot import ab01md                                                                                                                                                                                                                                                  
                                                                                                                                                                                                                                                                             
  A = np.array([[1, 2], [3, 4]], dtype=float, order='F')                                                                                                                                                                                                                     
  b = np.array([1, 0], dtype=float, order='F')                                                                                                                                                                                                                               
  result = ab01md('I', A, b, 0.0)                                                                                                                                                                                                                                            
  print('Controllable states:', result[2])                                                                                                                                                                                                                                   

Build System

• Meson build system with meson-python for packaging
• Automatic BLAS/LAPACK detection (OpenBLAS, scipy-openblas, Accelerate)
• Static linking for portable wheels

License

BSD-3-Clause (same as original SLICOT)

---

I'd like to thank the SLICOT team for creating such a comprehensive and well-documented library. This translation aims to make SLICOT more accessible to the Python scientific computing community while maintaining numerical accuracy and performance.

Feedback, bug reports, and contributions are welcome!

[grisuthedragon]

Since the python-control guys seem to you a bunch of issues. People should stick to the Fortran based slicot.

[jamestjsp]

What issue, except ego🤭 Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Martin Köhler ***@***.***> Sent: Wednesday, February 11, 2026 12:44:48 AM To: SLICOT/SLICOT-Reference ***@***.***> Cc: jamestjsp ***@***.***>; Author ***@***.***> Subject: Re: [SLICOT/SLICOT-Reference] SLICOT C11 Translation with Python Bindings - Now Available on PyPI (Discussion #38) Since the python-control guys seem to you a bunch of issues. People should stick to the Fortran based slicot. — Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYNODOOLGHSUY5NF3X4AJD4LLFWBAVCNFSM6AAAAACSYNYRMCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZWGQ4TEOI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ilayn]

Let's not go overboard with accusations. We are all trying to use SLICOT in a more convenient fashion. This is all open-source. If somebody needs it, they now know where to find the C translations. The more the better. We don't need exclusivity.

[grisuthedragon]

See python-control/python-control#1200 . We still can discuss about a C interface but not an AI based translation.

[jamestjsp]

What’s wrong with the AI based translation, are you worried about the accuracy? It has been tested well including ASAN. If required we can add more test coverage currently it has ~6700 tests Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Martin Köhler ***@***.***> Sent: Wednesday, February 11, 2026 8:00:11 AM To: SLICOT/SLICOT-Reference ***@***.***> Cc: jamestjsp ***@***.***>; Author ***@***.***> Subject: Re: [SLICOT/SLICOT-Reference] SLICOT C11 Translation with Python Bindings - Now Available on PyPI (Discussion #38) See python-control/python-control#1200<python-control/python-control#1200> . We still can discuss about a C interface but not an AI based translation. — Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYNODINFQJQEUUI6A54VJL4LMYWXAVCNFSM6AAAAACSYNYRMCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZWHE4DQMY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[jamestjat]

The last pending issue in the PR 1200 is an API disagreement jamestjsp/ctrlsys#12 (comment)
After all it was not meant to merge but a teaser and bug hunting effort, There was one real bug that was caught by myself. jamestjsp/ctrlsys#10

[grisuthedragon]

It is imperative that you refrain from using the same name as the original software project, especially on PyPI and for your GitHub project. Some people may assume that the original SLICOT was installed, but that your product was actually installed instead. It is evident that this will cause significant issues. The next issue to consider is that you began with version 1.0.0 once more. Consequently, this undermines the integrity of semantic versioning, which can cause issues with version comparison and software version identification. In order to reach a mutually acceptable solution that allows for the coexistence of both parties, it is necessary to

1. You have to rename your project. It is imperative that the name clearly identifies the product as a translation and not a wrapper. This includes platforms such as Pypi and GitHub.
2. Ensure that this message is prominently featured in your README, ideally directly under the headline: 'This project is an AI-based translation of the original SLICOT source (see https://github.com/SLICOT/SLICOT-Reference), which is not authorised by the SLICOT team. All all included algorithms (in their current design) are copyrighted by the SLICOT team.'
3. Refrain from promoting this project in any locations where SLICOT is currently in use. If people find it themselves, there is no problem.
4. The license have to stay the same as SLICOT.

If you accept this, including an acceptable name, everything is fine.

[jamestjsp]

The package has renamed to ctrlsys You gys need to reduce the friction by either distributing precompiled binaries and add C wrappers, else the C11 package will eventually win.

[jamestjat]

The project was not even targeting human users it was focused on agentic development. It is clearly mentioned in the readme. I will rename the public repo. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Martin Köhler ***@***.***> Sent: Thursday, February 12, 2026 12:47:02 AM To: SLICOT/SLICOT-Reference ***@***.***> Cc: James J ***@***.***>; Comment ***@***.***> Subject: [EXTERNAL] Re: [SLICOT/SLICOT-Reference] SLICOT C11 Translation with Python Bindings - Now Available on PyPI (Discussion #38) It is imperative that you refrain from using the same name as the original software project, especially on PyPI and for your GitHub project. Some people may assume that the original SLICOT was installed, but that your product was actually installed instead. It is evident that this will cause significant issues. The next issue to consider is that you began with version 1.0.0 once more. Consequently, this undermines the integrity of semantic versioning, which can cause issues with version comparison and software version identification. In order to reach a mutually acceptable solution that allows for the coexistence of both parties, it is necessary to 1. You have to rename your project. It is imperative that the name clearly identifies the product as a translation and not a wrapper. This includes platforms such as Pypi and GitHub. 2. Ensure that this message is prominently featured in your README, ideally directly under the headline: 'This project is an AI-based translation of the original SLICOT source (see https://github.com/SLICOT/SLICOT-Reference [github.com]<https://urldefense.com/v3/__https://github.com/SLICOT/SLICOT-Reference__;!!OkyjEqkqqe9UhNQ!yMdljlF903GtENnKt-5yXZ2_XXrfUkdOkGsSkHWnP_qsG7mE89LDaGz7I_to9mgjBxN8M7AkMokXWd2OOWoDeiJHqGDVdg$>), which is not authorised by the SLICOT team. All all included algorithms (in their current design) are copyrighted by the SLICOT team.' 3. Refrain from promoting this project in any locations where SLICOT is currently in use. If people find it themselves, there is no problem. 4. The license have to stay the same as SLICOT. If you accept this, including an acceptable name, everything is fine. — Reply to this email directly, view it on GitHub [github.com]<https://urldefense.com/v3/__https://github.com/SLICOT/SLICOT-Reference/discussions/38*discussioncomment-15778455__;Iw!!OkyjEqkqqe9UhNQ!yMdljlF903GtENnKt-5yXZ2_XXrfUkdOkGsSkHWnP_qsG7mE89LDaGz7I_to9mgjBxN8M7AkMokXWd2OOWoDeiKI04uc6g$>, or unsubscribe [github.com]<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BI76CRD55P6UKKLGDWPDW6D4LQOWNAVCNFSM6AAAAACSYNYRMCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZXHA2DKNI__;!!OkyjEqkqqe9UhNQ!yMdljlF903GtENnKt-5yXZ2_XXrfUkdOkGsSkHWnP_qsG7mE89LDaGz7I_to9mgjBxN8M7AkMokXWd2OOWoDeiJpIqc_nw$>. You are receiving this because you commented.Message ID: ***@***.***>