ゼロから作る自作Python Package Manager入門 【M3 Tech Talk 第241回】「金曜日に開催している社内LT会「M3 Tech Talk」の模様をお届けします！」 テックトーク(社内LT会)への参加、カジュアル面談の応募はこちら！ https://jobs.m3.com/product/ 【エムスリーテックブログ】 https://www.m3tech.blog/ 【エムスリー エンジニア公式Twitter】 https://twitter.com/m3_engineering #エムスリー #Tech
Rye and uv: August is Harvest Season for Python Packaging
Rye and uv: August is Harvest Season for Python Packaging written on Wednesday, August 21, 2024 It has been a few months since I wrote about Rye here last. You might remember that in February I passed over stewardship of my Rye packaging too to Astral. The folks over there have been super busy in building a lot of amazing tooling for Python packaging in the last few months. If you have been using
uv: Unified Python packaging
TL;DR: uv is an extremely fast Python package manager, written in Rust. We first released uv in February as a drop-in replacement for common pip workflows. Today, we're announcing a series of features that extend uv beyond a pip alternative, and into an end-to-end solution for managing Python projects, command-line tools, single-file scripts, and even Python itself. It's Cargo, for Python: a unifi
Rye
Welcome User Guide Community Changelog Philosophy Rye is a comprehensive project and package management solution for Python. Born from its creator's desire to establish a one-stop-shop for all Python users, Rye provides a unified experience to install and manages Python installations, pyproject.toml based projects, dependencies and virtualenvs seamlessly. It's designed to accommodate complex proje
The new APT 3.0 solver
APT 2.9.3 introduces the first iteration of the new solver codenamed solver3, and now available with the –solver 3.0 option. The new solver works fundamentally different from the old one. How does it work? Solver3 is a fully backtracking dependency solving algorithm that defers choices to as late as possible. It starts with an empty set of packages, then adds the manually installed packages, and t
Rye Grows With UV
Rye Grows With UV written on Thursday, February 15, 2024 Two weeks ago I asked the question again about What Rye should be. There has been one thing that I have not publicly shared before and that is that ever since Rye exists I have also been talking to Charlie Marsh about Python packaging and Python tooling. It turns out that we had some shared ideas of what an ideal Python tooling landscape wou
uv: Python packaging in Rust
TL;DR: uv is an extremely fast Python package installer and resolver, written in Rust, and designed as a drop-in replacement for pip and pip-tools workflows. uv represents a milestone in our pursuit of a "Cargo for Python": a comprehensive Python project and package manager that's fast, reliable, and easy to use. As part of this release, we're also taking stewardship of Rye, an experimental Python
Do not use requirements.txt
Are you developing a backend service in Python? I have two pieces of advice for you: Do not use pip and requirements.txt to manage Python dependencies. They lack crucial features that should be built-in. Use Poetry instead. To me, the first one is a no-brainer. The second one is more tentative: Poetry is a great option, but it’s hardly the only option worth considering. I’ll explain below. pip’s m
Bramble: A Purely Functional Build System and Package Manager
Bramble: A Purely Functional Build System and Package Manager About a year and a half ago I decided to start working on a build system inspired by Nix called Bramble. Andrew Chambers had launched hermes and I was messing around with starlark-go a bit and it seemed like writing a Nix-inspired functional build system with Starlark would be a nice way to better understand how they work. Bramble is no
PackagingCon 2023
PackagingCon 2023 was an amazing hybrid and in-person (first time) gathering, October 26-28th, in Berlin, one of the most open source friendly cities of the world. PackagingCon’s mission is to bring different ecosystems together: from Python’s pip to Rust’s cargo to Julia’s Pkg, from Debian apt over Nix to conda and mamba, and from vcpkg to Spack. We highlight many different approaches to package
WebBundle によるコンテンツの結合と WebPackaging | blog.jxck.io
Intro 依存コンテンツを 1 つにまとめて配信する WebBundle の仕様策定と実装が進んでいる。 これは Signed HTTP Exchange と合わせて WebPackaging を実現するための仕様であり、組み合わせれば WebBundle に対して署名することでコンテンツの配信を通信と分けて考えることができる。 Signed HTTP Exchange に比べると格段に簡単な仕様なので、現状のフォーマットと挙動について解説する。 draft-yasskin-wpack-bundled-exchanges-latest WebBundle かつて Bundled HTTP Exchanges と呼ばれていた仕様であり、複数のコンテンツを 1 つにまとめ、配信することができる。 例えば index.html とそれが依存する css/js/favicon etc を 1 つ
Uploading to PyPI
I found myself within a forest dark, For the straightforward pathway had been lost… Edit: I have been kindly informed that there is, in fact, an official guide for uploading packages to PyPI, located here. I’m a research assistant in a Speech Informatics lab at the University of Minnesota. One of my tasks recently has been to take a Python script written by a former student, make it more flexible
Packaging a python library - Thoughts on packaging python libraries
Packaging a python library 25 May 2014 (updated 30 September 2019) Note This is about packaging libraries, not applications. ⸻ All the advice here is implemented in a project template (with full support for C extensions): cookiecutter-pylibrary (introduction). I think the packaging best practices should be revisited, there are lots of good tools now-days that are either unused or underused. It's g
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - pkgxdev/pkgx: the last thing you’ll install
Python dependency management difficulty is an unhelpful meme
GitHub - popey/unsnap: Quickly migrate from using snap packages to flatpaks
PackagingCon 2021
Improving Linux Packaging: rinstall
Reddit - Dive into anything
(Soon)