Hello, I needed to make a small change to the backend Docker for our orchestration system: https://github.com/DAGWorks-Inc/hamilton/pull/1065 let me know if I should change anything to get it merged. Thanks!

I've just created a (draft) PR for adding a

pyproject.toml

. Will appreciate any feedback, especially with regard to testing this.

Are you guys particularly attached to flake8, or can we switch to ruff?

Re import sorting - do we want

hamilton_sdk

to be its own section, or 1st party (i.e. grouped with

hamilton

) or 3rd party (grouped with

pytest

etc)? There's some inconsistency in the files with that regard.

I created another PR to enable ruff. The sdk unit tests are failing, but I'm not sure why.

I've been looking at

parameterize_extract_columns

and saw that it requires

ParameterizedExtract

objects. Suggestion: have it accept some sort of named/ordered fields (e.g. list of dicts, or list of tuples) then wrap them internally in

ParameterizedExtract

. It saves an import and is a tiny bit more elegant imho. wdyt?

This message was deleted.

I installed the new pre-commit hooks and keep running into a weird ruff error. I'm not familiar with ruff, any ideas?

ruff.....................................................................Failed
- hook id: ruff
- exit code: 2

error: TOML parse error at line 176, column 1
    |
176 | [tool.ruff.format]
    | ^^^^^^^^^^^^^^^^^^
wanted exactly 1 element, more than 1 element

black....................................................................Passed
trim trailing whitespace.................................................Passed
fix end of files.........................................................Passed
fix requirements.txt.................................(no files to check)Skipped
check python ast.........................................................Passed

Custom CA cert support for [Async]HamiltonTracker: https://github.com/DAGWorks-Inc/hamilton/pull/1105 I wonder if we should share a single session object across all the functions in both these...reusing the session object generally improves performance. Also wonder if we can switch to modern-style Type Hints by using:

from __future__ import annotations

The AsyncDriver currently just works with the AsyncGraphAdapter. I would like it to work with a RayGraphAdapter. I am aware that Ray Tasks cannot themselves be async (if they wish to benefit from this then they need to start an async event loop inside the task) However I can see some benefit (not yet measurable, so I may be wrong!) in having all the coordination be async: HamiltonTracker, MLFlow, Ray task submission. Is this something that you are already considering? I am happy to take a look if not. Would your guidance be to extend the RayGraphAdapter to auto-detect when it is running in an Event loop or to subclass as AsyncRayGraphAdapter?

Added the ability to override nodes from later imported modules: https://github.com/DAGWorks-Inc/hamilton/pull/1134 The only part I am unsure about is how to update docs.

Quick question - why do we have

"sqlalchemy==1.4.49; python_version == '3.7.*'",

in pyproject.toml, if the minimum supported python version is 3.8?

Second question - regarding python 3.13 support - what are your plans for adding that (to CI + docs)? According to the python website, the released RC2 "is expected to become the final 3.13.0 release" - so any tests can already be done with that version.

Call to action

We strongly encourage maintainers of Python projects to prepare their projects for 3.13 compatibilities during this phase

I have found this collection with Python DE resources. They are yet missing Hamilton. This may be a good spot to be featured for free. There's 10 Forks and 73 Stars on it. https://github.com/vajol/python-data-engineering-resources/blob/main/resources/orchestration-tools.md

Hi guys, can you please fix this very minor issue (this is a warning raised by pytest):

hamilton\function_modifiers\macros.py:1522: SyntaxWarning: invalid escape sequence '\*'

What needs to be done is add a

r

to the beginning of the docstring (i.e.

"""

->

r"""

) and change

\*\*

on the aforementioned line to

**

.

Hey, quick question: is there a guide somewhere how to add google colab and github badges to example notebooks?

Just noticed that PR 1455 added exactly 1455 new lines of code. I swear it's a complete coincidence 😅

@Stefan Krawczyk nice progress on that mega PR!

Would it be possible to modify the docs deployment job to not fail in PRs by non-maintainers?

Can you guys please look into the github repo settings and enable the "update with rebase" feature on PRs?

Hi everyone, I’m new to contributing to Hamilton. I recently opened a PR and would love to work on more beginner friendly issues. Could someone point me to good first issues or areas where help is needed? Happy to take up documentation or small code tasks.

@Stefan Krawczyk Several notes after trying to follow https://github.com/apache/hamilton/tree/main/scripts#verification-script: 1. How do deal with this?

$ gpg --verify apache-hamilton-1.90.0-incubating-src.tar.gz.asc apache-hamilton-1.90.0-incubating-src.tar.gz
gpg: Signature made Sat 04 Apr 2026 08:10:01 IDT
gpg:                using RSA key FE668E857E89A11C5E5C000CA8D3D15600545C61
gpg: Good signature from "Stefan Krawczyk (1 year key for Hamilton project) <stefank@cs.stanford.edu>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: FE66 8E85 7E89 A11C 5E5C  000C A8D3 D156 0054 5C61

2. incorrect arg name to uv

$ uv venv --python 3.11 --clean
error: unexpected argument '--clean' found

  tip: a similar argument exists: '--clear'

3. re

scripts/verify_apache_artifacts.py

docstring - IMHO we should set it up to work as

uv run verify-... <args> <kwargs>

and do the mapping to the actual repo scripts internally

@Stefan Krawczyk I would like to work on this issue: https://github.com/apache/hamilton/issues/1550, can you assign this to me or is there someone I should reach out?

@Stefan Krawczyk I would like to work on this issue:https://github.com/apache/hamilton/issues/1486. Please assign it to me.

@Stefan Krawczyk What are your thoughts on adding a hamilton provider to airflow? I don't have a clear view of what it should include yet, but for start - we can have an operator (HamiltonOperator) that sets up a builder and produces a file on disk or a serializable object

@Stefan Krawczyk are you sure we don't want to push the top-level uv.lock? Perhaps we don't want it as part of #1563? uv docs say that the lock file should be in the VCS. I included it in the PR to prove that the linked issue (uv sync fail) is indeed resolved.

@Elijah Ben Izzy @Elijah Ben Izzy what do you say we create a milestone/project in hamilton dedicated to the 2.0 work, then start creating issues/specs according to Elijah's document?

Hey guys, can you please take a look at Switch the fingerprint algo to xxh3_128 by Dev-iL · Pull Request #1630 · apache/hamilton when time permits?

Hi everyone! I am new to the project and was looking to contribute to github.com/apache/hamilton/issues/1150, if someone can have a chance to look at the issue and answer my question when time permits that would be great!

Hey guys, do we have periodic CI jobs that install the latest (allowed) versions of dependencies and ensure CI is green? Asking because I created a couple of PRs today and they failed on preëxisting issues (mostly deprecation warnings). Related to that, there's a prek github action we can use instead of calling it manually