Hi team, Is this expected? or are there workarounds?

flytekit.core.type_engine.RestrictedTypeError: Transformer for type <class 'tuple'> is restricted currently

Yes tuples are restricted

this is a personal pain-point for me… also happens with NamedTuple

Aggh.. I just ran into this 😐

i used dataclasses to avoid this @little-cricket-84530 and they are cleaner than NamedTuples

Yeah.. I’m making the same switch now

I think we should support tuples in someway. The core team is thinking- community is welcome to propose and chime in

Curious why it’s “restricted”?

I believe it’s because we haven’t figured out a correct flyteidl/protobuf representation for tuples that’s completely compatible with python semantics:

tuple[int, int]  # two integers
tuple[int, ...]  # any number of integers

# more generally
tuple[T1, T2]  # 2-tuple of types T1 and T2 respectively
tuple[T1, T2, ..., Tn]  # etc...

I think at the very least we should have better support for

NamedTuple

so that it can be arbitrarily nested.

Ya, we do have list support, so we could pass tuples as lists

I have a dataclass… one of the fields I want to pass around is a pandas dataframe. Unfortunately this results in the following error getting pegged as seen here

f"Failed to extract schema for object {t}, (will run schemaless) error: {e}"
                f"If you have postponed annotations turned on (PEP 563) turn it off please. Postponed"
                f"evaluation doesn't work with json dataclasses"

Now 1 workaround would be to pass the dataframe around as a list of dictionary.. and then convert back to a dataframe but wondering if there’s a cleaner solution.. Should I define a marshmallow schema for it?

hmm @glamorous-carpet-83516 pandas dataframe in dataclasses are supported right?

only structured dataset

cool, @little-cricket-84530 can you use structured dataset?

Let me look into that