#flit — Public Fediverse posts

@mgorny The good news is that was merged in 2024 but never actually released, so this change only affects those using unreleased source directly? And it's been archived on PyPI, so perhaps find a replacement.
#Python #flit

@mgorny The good news is that was merged in 2024 but never actually released, so this change only affects those using unreleased source directly? And it's been archived on PyPI, so perhaps find a replacement.
#Python #flit

Today in things that couldn't have aged well:

"Unpin flit-core dependency" 2 years ago without actually updating the metadata to use the newer pyproject.toml format.

https://github.com/sethmlarson/socksio/commit/b326406915fd98a8185c1c160165c5b8963b30c1

#Python #flit

Today in things that couldn't have aged well:

"Unpin flit-core dependency" 2 years ago without actually updating the metadata to use the newer pyproject.toml format.

https://github.com/sethmlarson/socksio/commit/b326406915fd98a8185c1c160165c5b8963b30c1

#Python #flit

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

Porównajmy backendy #PEP517 dla paczek napisanych w samym Pythonie:

#flit-core: 51 KiB archiwum źródłowe, bez zależności, instaluje się 0,05 s, ~150 KiB po zainstalowaniu, działa wszedzie
#UvBuild: 300 KiB archiwum, wymaga ~250 zależności crate (54 MiB pobierania, ~600 MiB w .cargo), buduje się 1 min 20 s (na 12-wątkowym procesorze), 4,2 MiB po zainstalowaniu, wspiera kilkanaście platform

I oczywiście, że flit-core ma szerszą funkcjonalność. Ale jestem przekonany, że gdzieś ktoś potrzebuje zaoszczędzić te kilka milisekund budowania paczek Pythona.

#Python #RustLang #uv

Let's compare #PEP517 backends for pure #Python packages:

#flit-core: 51 KiB sdist, no dependencies, 0.05 s to install, ~150 KiB after installing, works everywhere
#UvBuild: 300 KiB sdist, requires ~250 crates (54 MiB download, ~600 MiB .cargo directory), 1 min 20 s to install (on a 12-thread system), 4.2 MiB after installing, supports a dozen platforms

And yes, you guessed right, flit-core has more functionality. But I'm sure that there are performance-critical wheel building workflows that will benefit from these few milliseconds shaved off wheel building time.

#RustLang #uv

Let's compare #PEP517 backends for pure #Python packages:

#flit-core: 51 KiB sdist, no dependencies, 0.05 s to install, ~150 KiB after installing, works everywhere
#UvBuild: 300 KiB sdist, requires ~250 crates (54 MiB download, ~600 MiB .cargo directory), 1 min 20 s to install (on a 12-thread system), 4.2 MiB after installing, supports a dozen platforms

And yes, you guessed right, flit-core has more functionality. But I'm sure that there are performance-critical wheel building workflows that will benefit from these few milliseconds shaved off wheel building time.

#RustLang #uv

#Gentoo powinno być już gotowe na testowanie przypadkowych paczek w języku #Python.

Obok #tox i #nox, mamy już: #flit, #hatch, #pdm, #pixi, #PythonPoetry i #uv. Coś przeoczyłem?

/me porównuje z https://www.xkcd.com/1987/

#Gentoo powinno być już gotowe na testowanie przypadkowych paczek w języku #Python.

Obok #tox i #nox, mamy już: #flit, #hatch, #pdm, #pixi, #PythonPoetry i #uv. Coś przeoczyłem?

/me porównuje z https://www.xkcd.com/1987/

#Gentoo should be prepared for testing random #Python packages now.

In addition to #tox and #nox, we have #flit, #hatch, #pdm, #pixi, #PythonPoetry and #uv. Did I miss anything?

/me compares with https://www.xkcd.com/1987/

#packaging

#Gentoo should be prepared for testing random #Python packages now.

In addition to #tox and #nox, we have #flit, #hatch, #pdm, #pixi, #PythonPoetry and #uv. Did I miss anything?

/me compares with https://www.xkcd.com/1987/

#packaging

#historical #medical #dataviz with a bonus side of #drseuss https://circulatingnow.nlm.nih.gov/2023/07/13/revealing-data-visualizations-in-historical-collections/ #flit

#historical #medical #dataviz with a bonus side of #drseuss https://circulatingnow.nlm.nih.gov/2023/07/13/revealing-data-visualizations-in-historical-collections/ #flit

@mgorny You can use #flit to produce sdist distributions with autogenerated setup.py:

https://flit.pypa.io/en/stable/cmdline.html#cmdoption-flit-build-setup-py

#python

@mgorny You can use #flit to produce sdist distributions with autogenerated setup.py:

https://flit.pypa.io/en/stable/cmdline.html#cmdoption-flit-build-setup-py

#python

@m_cadek I found #Flit to be relatively easy when I started using it recently. The only thing that stumped me initially was that I had a single-file module, but I wanted some data files to get packaged with it. Flit handles that automatically, but you need to structure your code as a package (directory w/ an __init__.py file) instead of just a module. Once I got that straightened out, it was smooth sailing.

https://flit.pypa.io/en/stable/index.html

@m_cadek I found #Flit to be relatively easy when I started using it recently. The only thing that stumped me initially was that I had a single-file module, but I wanted some data files to get packaged with it. Flit handles that automatically, but you need to structure your code as a package (directory w/ an __init__.py file) instead of just a module. Once I got that straightened out, it was smooth sailing.

https://flit.pypa.io/en/stable/index.html

Solved! After banging my head on this some more I found it's related to the distinction between a module (a single .py file) and a package (a directory with a __init__.py file in it, along with other stuff).

The #Flit docs say 'Data files within a package directory are automatically included.' This is 100% technically correct, but easy for a beginner (like me, in this case!) to misunderstand and think that anything in their project directory will be included.

#TIL #python #packaging

Solved! After banging my head on this some more I found it's related to the distinction between a module (a single .py file) and a package (a directory with a __init__.py file in it, along with other stuff).

The #Flit docs say 'Data files within a package directory are automatically included.' This is 100% technically correct, but easy for a beginner (like me, in this case!) to misunderstand and think that anything in their project directory will be included.

#TIL #python #packaging