Investigate interpreter segfault TODO comment for Python 3.6 vs 3.11

[korydraughn]

See comment in the following code.

python-irodsclient/irods/test/data_obj_test.py

Lines 741 to 744 in 86a8f11

	@classmethod
	def tearDownClass(cls):
	# TODO: Skipping this will result in an interpreter seg fault for Py3.6 but not 3.11; why?
	del cls.logins

This may apply to other tests (i.e. collection_test.py).

[alanking]

FWIW, I would recommend dropping support for 3.6 as part of #480 as it has been EOL since the end of 2021 (https://devguide.python.org/versions/#unsupported-versions), and so we won't need to worry about this.

[trel]

FWIW, I would recommend dropping support for 3.6 as part of #480 as it has been EOL since the end of 2021 (https://devguide.python.org/versions/#unsupported-versions), and so we won't need to worry about this.

Yes please. We currently advertise 3.4, 3.5, and 3.6. Let's drop all three for 2.1.0.

python-irodsclient/setup.py

Lines 32 to 34 in 0c9600e

	'Programming Language :: Python :: 3.4',
	'Programming Language :: Python :: 3.5',
	'Programming Language :: Python :: 3.6',

We'll keep 2.7 (and 3.7, also EOL) until we get to our 3.0.0 release.

[trel]

Hmm, that matrix of dropping support might be confusing to users.

[trel]

So perhaps we move this issue to 3.0.0 and take care of all EOL issues at once?

[alanking]

I was more thinking of dropping support in 3.0.0. If we drop support for anything that came after python 2.7, that would be kind of weird.

Yes, I think moving this to the 3.0.0 milestone makes sense.

[trel]

3.0.0 - done.

[trel]

We want to remove support for < Python 3.8 for PRC 3.0.0.

Aka, we'll support 3.8 and later.