Stop showing `DeprecationWarning` related to tarfile

[jezdez]

Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

What happened?

When running an installer like miniconda I get:

Unpacking payload ...
entry_point.py:256: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior.
entry_point.py:256: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior.

Installing base environment...

We should prevent those DeprecationWarning to be shown.

On Slack @ifitchet suggested it's related to the deprecation notes in https://docs.python.org/3.11/library/tarfile.html#tarfile.TarFile.extraction_filter and the following blurb:

In Python 3.12+, leaving extraction_filter=None will emit a DeprecationWarning.

But I can't find a use of extraction_filter directly, other than

conda-standalone/src/conda_constructor/extract.py

Lines 93 to 94 in cc26814

	if hasattr(t, "extraction_filter"):
	tar_args["filter"] = "data"

I'm of course wondering if this is related to conda-package-streaming of course.

Additional Context

No response

[marcoesters]

Thanks for the report! Unfortunately, I cannot reproduce the problem on Silicon macOS or linux-aarch64.

Can you provide some more information on which Miniconda installer/conda-standalone version you used and what your platform is?

[Jrice1317]

The default is None which is why the deprecation warning is showing. So, it needs to be set using one of the following listed here.

[jezdez]

I was following https://www.anaconda.com/docs/getting-started/miniconda/install#macos-terminal-installer on macOS on ARM64.

[marcoesters]

In your installation directory, you will find a _conda binary. Can you call _conda --version and paste the output?

[Jrice1317]

In Python 3.14, the 'data' filter will become the default instead. It’s possible to switch earlier; see TarFile.extraction_filter.

It looks like data will be the new default, so it needs to be changed.

[marcoesters]

@Jrice1317, the filter is set:

conda-standalone/src/conda_constructor/extract.py

Lines 93 to 94 in cc26814

	if hasattr(t, "extraction_filter"):
	tar_args["filter"] = "data"

And we even test for it:

conda-standalone/tests/test_extract.py

Lines 30 to 44 in cc26814

	def test_extract_tarball_no_raise_deprecation_warning(tmp_path: Path):
	# See https://github.com/conda/conda-standalone/issues/143
	tarbytes = (HERE / "data" / "futures-compat-1.0-py3_0.tar.bz2").read_bytes()
	process = run_conda(
	"constructor",
	"--prefix",
	tmp_path,
	"--extract-tarball",
	input=tarbytes,
	capture_output=True,
	check=True,
	)
	assert b"DeprecationWarning: Python" not in process.stderr
	# warnings should be send to stderr but check stdout for completeness
	assert b"DeprecationWarning: Python" not in process.stdout

[Jrice1317]

Data will be the new default in 3.14. See list here.

[Callek]

At first glance, THAT conda standalone works but conda-package-streaming has stream_conda_info which seems to use the default TarfileNoSameOwner.open and not the conda-standalone piece, (via tar_generator) ... So we're missing the piece here.

A possible fix is for conda-package-streaming to set extraction_filter to the function in the Cpython Tarfile stuff (tarfile.data_filter) ala https://github.com/python/cpython/blob/1793b7291f4c360ccbbf13a110abbcdf89c65aec/Lib/tarfile.py#L2272 which would solve it for all conda calls on this codepath, if you don't pass in filter)