#setuptools — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #setuptools, aggregated by home.social.
-
Es ist unfassbar, wie viele compatibility layers man installieren muss, um #Keras in #R zum laufen zu bringen.
Ich weiß schon, dass manche #Quants #Python nicht mögen, aber c'mon, ich habe gerade ein #JavaSDK installiert, um die #setuptools für den r-Keras-Wrapper aufsetzen zu können. Reeeeeaaaaaly?! 🧐
-
Es ist unfassbar, wie viele compatibility layers man installieren muss, um #Keras in #R zum laufen zu bringen.
Ich weiß schon, dass manche #Quants #Python nicht mögen, aber c'mon, ich habe gerade ein #JavaSDK installiert, um die #setuptools für den r-Keras-Wrapper aufsetzen zu können. Reeeeeaaaaaly?! 🧐
-
Es ist unfassbar, wie viele compatibility layers man installieren muss, um #Keras in #R zum laufen zu bringen.
Ich weiß schon, dass manche #Quants #Python nicht mögen, aber c'mon, ich habe gerade ein #JavaSDK installiert, um die #setuptools für den r-Keras-Wrapper aufsetzen zu können. Reeeeeaaaaaly?! 🧐
-
Es ist unfassbar, wie viele compatibility layers man installieren muss, um #Keras in #R zum laufen zu bringen.
Ich weiß schon, dass manche #Quants #Python nicht mögen, aber c'mon, ich habe gerade ein #JavaSDK installiert, um die #setuptools für den r-Keras-Wrapper aufsetzen zu können. Reeeeeaaaaaly?! 🧐
-
#Python is just doing great. We're not having impossible constraints, as some projects need old #setuptools for pkg_resources, and other projects are starting to require newer setuptools for some fancy new features. And ofc after promising to release pkg_resources standalone over a month ago, setuptools upstream didn't deliver.
-
Aaand we're seeing the first '#setuptools < 82' runtime dependencies in random packages because they are trying hard to workaround breakage due to pkg_resources removal.
-
El mismo síntoma, pero meses después. Ahora es una actualización de setuptools la que genera el error del módulo pkg_resource no encontrado. Si presentas este problema, debes fijar la versión de setuptools en 81 o anterior.
https://www.cosmoscalibur.com/es/blog/2025/modulo-pkg-resources-no-encontrado-en-ambientes-uv/
-
El mismo síntoma, pero meses después. Ahora es una actualización de setuptools la que genera el error del módulo pkg_resource no encontrado. Si presentas este problema, debes fijar la versión de setuptools en 81 o anterior.
https://www.cosmoscalibur.com/es/blog/2025/modulo-pkg-resources-no-encontrado-en-ambientes-uv/
-
El mismo síntoma, pero meses después. Ahora es una actualización de setuptools la que genera el error del módulo pkg_resource no encontrado. Si presentas este problema, debes fijar la versión de setuptools en 81 o anterior.
https://www.cosmoscalibur.com/es/blog/2025/modulo-pkg-resources-no-encontrado-en-ambientes-uv/
-
El mismo síntoma, pero meses después. Ahora es una actualización de setuptools la que genera el error del módulo pkg_resource no encontrado. Si presentas este problema, debes fijar la versión de setuptools en 81 o anterior.
https://www.cosmoscalibur.com/es/blog/2025/modulo-pkg-resources-no-encontrado-en-ambientes-uv/
-
Lessons from this week's removal of the #pkg_resources module:
- If you don't use the `--no-build-isolation` argument of `pip install`, then `--require-hashes` is only partly effective and your builds may break whenever incompatible changes are made to #setuptools or other build dependencies.
- If you use `--no-build-isolation`, you need multiple `pip install` calls: first for all the needed build dependencies (a.k.a. `setup_requires`), then for the packages you actually want.
-
Lessons from this week's removal of the #pkg_resources module:
- If you don't use the `--no-build-isolation` argument of `pip install`, then `--require-hashes` is only partly effective and your builds may break whenever incompatible changes are made to #setuptools or other build dependencies.
- If you use `--no-build-isolation`, you need multiple `pip install` calls: first for all the needed build dependencies (a.k.a. `setup_requires`), then for the packages you actually want.
-
Lessons from this week's removal of the #pkg_resources module:
- If you don't use the `--no-build-isolation` argument of `pip install`, then `--require-hashes` is only partly effective and your builds may break whenever incompatible changes are made to #setuptools or other build dependencies.
- If you use `--no-build-isolation`, you need multiple `pip install` calls: first for all the needed build dependencies (a.k.a. `setup_requires`), then for the packages you actually want.
-
Lessons from this week's removal of the #pkg_resources module:
- If you don't use the `--no-build-isolation` argument of `pip install`, then `--require-hashes` is only partly effective and your builds may break whenever incompatible changes are made to #setuptools or other build dependencies.
- If you use `--no-build-isolation`, you need multiple `pip install` calls: first for all the needed build dependencies (a.k.a. `setup_requires`), then for the packages you actually want.
-
Lessons from this week's removal of the #pkg_resources module:
- If you don't use the `--no-build-isolation` argument of `pip install`, then `--require-hashes` is only partly effective and your builds may break whenever incompatible changes are made to #setuptools or other build dependencies.
- If you use `--no-build-isolation`, you need multiple `pip install` calls: first for all the needed build dependencies (a.k.a. `setup_requires`), then for the packages you actually want.
-
Setuptools deprecated pkg_resources in docs for ~two years, then with a DeprecationWarning for ~two years, then a UserWarning for ~one year.
2021-04: Deprecate in docs (v56.0.0)
https://github.com/pypa/setuptools/commit/8fe85c22cee7fde5e6af571b30f864bad156a0102023-03: Officially deprecate with DeprecationWarning (v67.5.0)
https://github.com/pypa/setuptools/pull/38432025-05: Promote to UserWarning with earliest removal deadline of 2025-11-30 (v80.9.0)
https://github.com/pypa/setuptools/pull/50142026-02: Remove (v82.0.0)
https://github.com/pypa/setuptools/pull/5007 -
Setuptools deprecated pkg_resources in docs for ~two years, then with a DeprecationWarning for ~two years, then a UserWarning for ~one year.
2021-04: Deprecate in docs (v56.0.0)
https://github.com/pypa/setuptools/commit/8fe85c22cee7fde5e6af571b30f864bad156a0102023-03: Officially deprecate with DeprecationWarning (v67.5.0)
https://github.com/pypa/setuptools/pull/38432025-05: Promote to UserWarning with earliest removal deadline of 2025-11-30 (v80.9.0)
https://github.com/pypa/setuptools/pull/50142026-02: Remove (v82.0.0)
https://github.com/pypa/setuptools/pull/5007 -
Setuptools deprecated pkg_resources in docs for ~two years, then with a DeprecationWarning for ~two years, then a UserWarning for ~one year.
2021-04: Deprecate in docs (v56.0.0)
https://github.com/pypa/setuptools/commit/8fe85c22cee7fde5e6af571b30f864bad156a0102023-03: Officially deprecate with DeprecationWarning (v67.5.0)
https://github.com/pypa/setuptools/pull/38432025-05: Promote to UserWarning with earliest removal deadline of 2025-11-30 (v80.9.0)
https://github.com/pypa/setuptools/pull/50142026-02: Remove (v82.0.0)
https://github.com/pypa/setuptools/pull/5007 -
Setuptools deprecated pkg_resources in docs for ~two years, then with a DeprecationWarning for ~two years, then a UserWarning for ~one year.
2021-04: Deprecate in docs (v56.0.0)
https://github.com/pypa/setuptools/commit/8fe85c22cee7fde5e6af571b30f864bad156a0102023-03: Officially deprecate with DeprecationWarning (v67.5.0)
https://github.com/pypa/setuptools/pull/38432025-05: Promote to UserWarning with earliest removal deadline of 2025-11-30 (v80.9.0)
https://github.com/pypa/setuptools/pull/50142026-02: Remove (v82.0.0)
https://github.com/pypa/setuptools/pull/5007 -
Setuptools deprecated pkg_resources in docs for ~two years, then with a DeprecationWarning for ~two years, then a UserWarning for ~one year.
2021-04: Deprecate in docs (v56.0.0)
https://github.com/pypa/setuptools/commit/8fe85c22cee7fde5e6af571b30f864bad156a0102023-03: Officially deprecate with DeprecationWarning (v67.5.0)
https://github.com/pypa/setuptools/pull/38432025-05: Promote to UserWarning with earliest removal deadline of 2025-11-30 (v80.9.0)
https://github.com/pypa/setuptools/pull/50142026-02: Remove (v82.0.0)
https://github.com/pypa/setuptools/pull/5007 -
Accessing github from work is annoying.
I hope someone else in the world files a bug soon on flake8 not being compatible with a fresh python 3.12+ virtualenv, now that setuptools 82 is out and flake8 is still using the deprecated (now removed) pkg_resources.
-
happy `ModuleNotFoundError: No module named 'pkg_resources’` day to all who celebrate #setuptools
-
I hear that #Python folk are going to enjoy their Monday.
https://setuptools.pypa.io/en/stable/history.html#v82-0-0
Yep, #setuptools removed pkg_resources.
Thanks to Eli Schwartz for the advance warning. We're going to mask it in #Gentoo.
EDIT: I've started a DPO thread for this: https://discuss.python.org/t/pkg-resources-removal-how-to-go-from-there/106079
-
I need some help packaging a python module that I built. It references a few different python files, and .csv within the folder structure, and searching leads me to examples/tutorials that are either too simple, or way too complex. I can't find anything bridging the gap.
Any blogs, courses, tutorial, or even as a last resort youtube videos, that may help me out? #python #packaging #flit #setuptools #hatchling
The project that I'm trying to package is here - https://git.jmkengineering.com/JMK_Engineering_Inc/JEPL/src/branch/main/jepl
-
I need some help packaging a python module that I built. It references a few different python files, and .csv within the folder structure, and searching leads me to examples/tutorials that are either too simple, or way too complex. I can't find anything bridging the gap.
Any blogs, courses, tutorial, or even as a last resort youtube videos, that may help me out? #python #packaging #flit #setuptools #hatchling
The project that I'm trying to package is here - https://git.jmkengineering.com/JMK_Engineering_Inc/JEPL/src/branch/main/jepl
-
I need some help packaging a python module that I built. It references a few different python files, and .csv within the folder structure, and searching leads me to examples/tutorials that are either too simple, or way too complex. I can't find anything bridging the gap.
Any blogs, courses, tutorial, or even as a last resort youtube videos, that may help me out? #python #packaging #flit #setuptools #hatchling
The project that I'm trying to package is here - https://git.jmkengineering.com/JMK_Engineering_Inc/JEPL/src/branch/main/jepl
-
I need some help packaging a python module that I built. It references a few different python files, and .csv within the folder structure, and searching leads me to examples/tutorials that are either too simple, or way too complex. I can't find anything bridging the gap.
Any blogs, courses, tutorial, or even as a last resort youtube videos, that may help me out? #python #packaging #flit #setuptools #hatchling
The project that I'm trying to package is here - https://git.jmkengineering.com/JMK_Engineering_Inc/JEPL/src/branch/main/jepl
-
I need some help packaging a python module that I built. It references a few different python files, and .csv within the folder structure, and searching leads me to examples/tutorials that are either too simple, or way too complex. I can't find anything bridging the gap.
Any blogs, courses, tutorial, or even as a last resort youtube videos, that may help me out? #python #packaging #flit #setuptools #hatchling
The project that I'm trying to package is here - https://git.jmkengineering.com/JMK_Engineering_Inc/JEPL/src/branch/main/jepl
-
Last week I was a little annoyed about missing Microsoft C++ Build Tools #MSVC on a system without admin rights. I needed a compiler for building the #python C++ extension I developed a while ago. Annoyed not because I could not ask someone to install it for me, but annoyed because of the lack of compiler choices in this particular case. I have to use the MSVC instead of let's say #g++ which I could easily install via the #MinGW-w64 #conda package myself.
I found out that I can tell #setuptools (the backend build system) via #pip config settings to use a different compiler during build:
-
@stfn @cofiem @bkim If versioning via `pyproject.toml`is a concern then you might want to take a look at `setuptools_scm` which takes care of that via Git tags.
Workflow then becomes quite simple...
1. tag a commit
2. tag triggers CI to build and publish package (conditional on format of tag matching a pattern e.g. `v*`)https://setuptools-scm.readthedocs.io/en/latest/
GitHub example (should be adaptable to Woodpecker)
https://github.com/AFM-SPM/TopoStats/blob/main/.github/workflows/pypi.yaml
(check `pyproject.toml` in that repo too).
-
Some users reported that the #Dirsearch installer in bashcore-injector failed on #Debian 13.1.
The issue was a mix of packages: #pip from #APT vs #setuptools installed via pip, causing uninstall-no-record-file errors when pip tried to upgrade.
Fixed the script to handle this properly.
Updated bashcore-injector.tar.gz is now available at https://bashcore.org
-
Some users reported that the #Dirsearch installer in bashcore-injector failed on #Debian 13.1.
The issue was a mix of packages: #pip from #APT vs #setuptools installed via pip, causing uninstall-no-record-file errors when pip tried to upgrade.
Fixed the script to handle this properly.
Updated bashcore-injector.tar.gz is now available at https://bashcore.org
-
Some users reported that the #Dirsearch installer in bashcore-injector failed on #Debian 13.1.
The issue was a mix of packages: #pip from #APT vs #setuptools installed via pip, causing uninstall-no-record-file errors when pip tried to upgrade.
Fixed the script to handle this properly.
Updated bashcore-injector.tar.gz is now available at https://bashcore.org
-
Some users reported that the #Dirsearch installer in bashcore-injector failed on #Debian 13.1.
The issue was a mix of packages: #pip from #APT vs #setuptools installed via pip, causing uninstall-no-record-file errors when pip tried to upgrade.
Fixed the script to handle this properly.
Updated bashcore-injector.tar.gz is now available at https://bashcore.org
-
Some users reported that the #Dirsearch installer in bashcore-injector failed on #Debian 13.1.
The issue was a mix of packages: #pip from #APT vs #setuptools installed via pip, causing uninstall-no-record-file errors when pip tried to upgrade.
Fixed the script to handle this properly.
Updated bashcore-injector.tar.gz is now available at https://bashcore.org
-
Our August 2025 Debian Contributions report is out! We have updates on preparing for the setup.py install deprecation in setuptools, Salsa CI, the Debian 13 “trixie” release and more.
Full report here: https://www.freexian.com/blog/debian-contributions-08-2025/
We thank the organizations subscribing to our Long Term Support contracts (https://www.freexian.com/lts/) and consulting services (https://www.freexian.com/services/) for making this possible.
-
Our August 2025 Debian Contributions report is out! We have updates on preparing for the setup.py install deprecation in setuptools, Salsa CI, the Debian 13 “trixie” release and more.
Full report here: https://www.freexian.com/blog/debian-contributions-08-2025/
We thank the organizations subscribing to our Long Term Support contracts (https://www.freexian.com/lts/) and consulting services (https://www.freexian.com/services/) for making this possible.
-
Our August 2025 Debian Contributions report is out! We have updates on preparing for the setup.py install deprecation in setuptools, Salsa CI, the Debian 13 “trixie” release and more.
Full report here: https://www.freexian.com/blog/debian-contributions-08-2025/
We thank the organizations subscribing to our Long Term Support contracts (https://www.freexian.com/lts/) and consulting services (https://www.freexian.com/services/) for making this possible.
-
Our August 2025 Debian Contributions report is out! We have updates on preparing for the setup.py install deprecation in setuptools, Salsa CI, the Debian 13 “trixie” release and more.
Full report here: https://www.freexian.com/blog/debian-contributions-08-2025/
We thank the organizations subscribing to our Long Term Support contracts (https://www.freexian.com/lts/) and consulting services (https://www.freexian.com/services/) for making this possible.
-
Our August 2025 Debian Contributions report is out! We have updates on preparing for the setup.py install deprecation in setuptools, Salsa CI, the Debian 13 “trixie” release and more.
Full report here: https://www.freexian.com/blog/debian-contributions-08-2025/
We thank the organizations subscribing to our Long Term Support contracts (https://www.freexian.com/lts/) and consulting services (https://www.freexian.com/services/) for making this possible.
-
[Перевод] Что с Python? Меньше производительности, никакого сахара и больше багов
Python продолжает меняться, но не всегда так, как ждёт сообщество. Новый синтаксический сахар отклоняют, прирост производительности оказывается скромнее обещанного, а очередные депрекации в setuptools ломают проекты. При этом экосистема получает долгожданный стандартный lock-файл и поддержку uv в Dependabot. В статье разбираем, что это значит на практике и почему начинающим Python-разработчикам важно следить за этими изменениями.
https://habr.com/ru/companies/otus/articles/944160/
#python #Python_314 #производительность_Python #pep #синтаксический_сахар #зависимости #setuptools #Dependabot
-
Dziś ktoś pytał w temacie walki z ostrzeżeniami o "przestarzałej" funkcjonalności w #setuptools (w #Gentoo zbieramy je i wypisujemy ponownie, więc ludzie faktycznie mogą je zauważyć). Myślę, że moją najlepszą podpowiedzią było: użyj innego systemu budowania.
-
Dziś ktoś pytał w temacie walki z ostrzeżeniami o "przestarzałej" funkcjonalności w #setuptools (w #Gentoo zbieramy je i wypisujemy ponownie, więc ludzie faktycznie mogą je zauważyć). Myślę, że moją najlepszą podpowiedzią było: użyj innego systemu budowania.
-
Dziś ktoś pytał w temacie walki z ostrzeżeniami o "przestarzałej" funkcjonalności w #setuptools (w #Gentoo zbieramy je i wypisujemy ponownie, więc ludzie faktycznie mogą je zauważyć). Myślę, że moją najlepszą podpowiedzią było: użyj innego systemu budowania.
-
Dziś ktoś pytał w temacie walki z ostrzeżeniami o "przestarzałej" funkcjonalności w #setuptools (w #Gentoo zbieramy je i wypisujemy ponownie, więc ludzie faktycznie mogą je zauważyć). Myślę, że moją najlepszą podpowiedzią było: użyj innego systemu budowania.
-
Dziś ktoś pytał w temacie walki z ostrzeżeniami o "przestarzałej" funkcjonalności w #setuptools (w #Gentoo zbieramy je i wypisujemy ponownie, więc ludzie faktycznie mogą je zauważyć). Myślę, że moją najlepszą podpowiedzią było: użyj innego systemu budowania.
-
Someone asked about fixing #setuptools deprecation warnings today (#Gentoo collects and reprints them, so people actually notice). I think my best hint is: use another build system.
-
Someone asked about fixing #setuptools deprecation warnings today (#Gentoo collects and reprints them, so people actually notice). I think my best hint is: use another build system.
-
Someone asked about fixing #setuptools deprecation warnings today (#Gentoo collects and reprints them, so people actually notice). I think my best hint is: use another build system.
-
Someone asked about fixing #setuptools deprecation warnings today (#Gentoo collects and reprints them, so people actually notice). I think my best hint is: use another build system.