[Bug]: Python: Update dill version to make pylint work

[davidreisbr]

What happened?

Problem: apache-beam because of it's archaic pinned dill version (0.3.1.1 from 2019) is only compatible with pylint 2.15.8 (from Dec 2022). That old version if pylint breaks on my apache-beam program, with this trace:

pylint_crash.txt

I'm assuming the a newer pylint version fixes the problem, since when I run an out-of-environment pylint I only get apache-beam import errors (beam must not be in that env, so that I can use the newer pylint).

From looking at the the bug on the dill version pin, it seem the breakage that motivated was a one off, so it's worth reconsidering the pin policy, specially considering the dep is getting older and older, and I assume it's becoming more problematic over time.

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[liferoad]

We are working on removing dill (#34903). cc @claudevdm

[claudevdm]

Dill is optional in 2.69