From 57a0adeaf0dabba0349fc0d5414686edaf241601 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A1ll=20Haraldsson?= Date: Tue, 19 Apr 2022 12:26:59 +0000 Subject: [PATCH] Not support EOLed 3.6 or older I'm unclear which version you download by default, I suggest latest 3.10.x. Recent versions of all versions down to 3.7, and likely way far back have security issue, see: https://github.com/JuliaPy/PyCall.jl/pull/986 Not stating support is mostly a service to your users, and yourself so they and you indirectly may not get into trouble. You could amend to has been tested down to 3.5, worked at some point, not recommended. [skip ci] --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fb0b69c5..324ed3ae 100644 --- a/README.md +++ b/README.md @@ -44,4 +44,4 @@ The existing package [PyCall](https://github.com/JuliaPy/PyCall.jl) is another s - PythonCall by default never copies mutable objects when converting, but instead directly wraps the mutable object. This means that modifying the converted object modifies the original, and conversion is faster. - PythonCall does not usually automatically convert results to Julia values, but leaves them as Python objects. This makes it easier to do Pythonic things with these objects (e.g. accessing methods) and is type-stable. - PythonCall installs dependencies into a separate conda environment for each Julia project. This means each Julia project can have an isolated set of Python dependencies. -- PythonCall supports Julia 1.4+ and Python 3.5+ whereas PyCall supports Julia 0.7+ and Python 2.7+. +- PythonCall supports Julia 1.4+ and Python 3.7+ whereas PyCall supports Julia 0.7+ and Python 2.7+.