Conversation
Codecov Report
@@ Coverage Diff @@
## master #512 +/- ##
=======================================
Coverage 65.55% 65.55%
=======================================
Files 19 19
Lines 1504 1504
=======================================
Hits 986 986
Misses 518 518Continue to review full report at Codecov.
|
|
I see you took my advice, Since you did, should Python 3.7 be preferred (and at least tested)? At least this feature: https://www.python.org/downloads/release/python-370/ I'm not sure, but I think this "forced UTF-8 runtime mode" may align better with Julia. At least if Python 3.7 is used, maybe it should be enabled by default? It may or may not (already) be backported to earlier versions: -- Should at least Windows also default to Python3? It usually has no Python installed, so if conda gets one for you it may as well be Python 3.7. |
|
MacOS and Windows default to using Conda, which now defaults to Python 3. |
|
It might be reasonable to set UTF-8 I/O in libpython, but not by an environment variable (which would affect child processes too). We need to find an API for this. (When pyjulia is used, we shouldn't change the I/O mode, however.) |
Now that Conda defaults to Python 3 (JuliaPy/Conda.jl#108), to be consistent PyCall should default to
python3on non-Mac Unices.Python 2 is still supported, you just need to configure PyCall with
ENV["PYTHON"]="python2"or similar. Existing installations will not be affected because PyCall remembers what Python you last configured with.See also #435.