Conversation
024855a to
fcb2a22
Compare
bryanwweber
left a comment
There was a problem hiding this comment.
I think we should have a check at the top of SConstruct as well that the Python running SCons is >=3.7. But that can wait until after 2.6, I suppose, since it would preclude system Pythons from even running SCons and we're not using (nor will we add any, I bet) 3.7-specific features into the various SCons* files before 2.6 is released.
fcb2a22 to
4c13fe1
Compare
|
Done! |
|
I wonder if it wouldn't be preferable to error out for Python 3.6 if |
Point users to option python_package='none' in error message.
67945a8 to
9a16cff
Compare
|
As a result of #1158, the requirement of Python 3.7 or newer applies to the Python interpreter running I don't think you'll ever get to the error handling added here except in the somewhat unlikely case where The two options I see for providing a more helpful are either:
|
This would be my preference using |
Np. What I had worked well prior to merging #1158. I added the check as requested, but left the version decision separate from the pre-existing checks. |
1a2aaf5 to
790af21
Compare
Codecov Report
@@ Coverage Diff @@
## main #1222 +/- ##
==========================================
+ Coverage 65.44% 65.47% +0.03%
==========================================
Files 320 327 +7
Lines 46321 46349 +28
Branches 19688 19688
==========================================
+ Hits 30315 30349 +34
Misses 13475 13475
+ Partials 2531 2525 -6
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
790af21 to
1cc232e
Compare
Changes proposed in this pull request
If applicable, provide an example illustrating new features this pull request is introducing
Checklist
scons build&scons test) and unit tests address code coverage