#5095 [Core feature] Revisit enabling FlyteDeck by default for Python tasks. Issue created by thomasjpfan ### Motivation: Why do you think this is important? With flyteorg/flytekit#2248 and flyteorg/flytekit#2264,

FlyteDecks

will show the source code and python dependencies for Python tasks. This makes

FlyteDecks

universally useful for Python tasks. ### Goal: What should the final outcome look like, ideally? At least for Python tasks, it'll be great if

enable_deck

is

True

is the default. ### Describe alternatives you've considered The alternative is to keep the current default. Historically, FlyteDecks were turned off because there was a large overhead for rending large dataframes in the Inputs or Outputs. We can mitigate this issue by trimming the source code being rendered and not show the inputs or outputs by default. I do not think there is a large use case for partially rendering inputs and outputs in the

FlyteDeck

. An extension to this proposal is to add a new

default_decks

parameter to `task`: @task(decks=["source_code", "dependencies"]) If a user wants to include the "input" deck, then can write:

decks=["source_code", "dependencies", "input"]

### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte