This message was deleted.
# hamilton-help
s
This message was deleted.
e
Hmm so this is the way hamilton inspect the types — it’s a different code path for the lowercase versus uppercase ones :/ I’m happy to see if I can fix tomorrow! For now I think you have a workaround?
Also you can always temporarily use
dict
as another workaround
Also, welcome!
a
Thanks @Elijah Ben Izzy. It would be handy to know if its feasible to use the
dict
version somehow as some of the code I'm interested in migrating relies upon
from ___future___ import annotations
at the moment. Kind of you to get back to me so fast.
e
Ahh yep! Current fix should be just lowercase
dict
(with no subscriptions) but I’ll see if I can do a fix first thing tomorrow AM — should hopefully be pretty straightforward. Using python 3.10 right?
❤️ 1
a
@Elijah Ben Izzy yes py310 for the moment, but i want to see if it's feasible to embed Hamilton in a generic pattern for a range of tabular inputs, so compatibility across multiple python versions will become an issue in due course.
e
Awesome! So yeah, Hamilton is meant to support 3.7 -> 3.11 now (the current “living” versions of python, and will be supporting new versions as they come online/deprecating them as they hit EOL. We will likely maintain some backwards compatibility even after EOL (we just deprecated 3.6) as migrating can take some time.
OK, fix should be there @Amos — see https://hamilton-opensource.slack.com/archives/C03AJNGDGQL/p1680540875461529. I didn’t test it out on your workflow (obviously), but I think it should get at your problem. Let me know if it works/you need anything else!