New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Python 3.8 #3299
Comments
can this be done also using the jupyter notebook ? |
How would that be useful? |
Plenty of complaints coming from Python 3.8alpha on unclosed files. Targeted those areas which intersect with PyPy failures - this changeset reduces the PyPy fails by 17 on the local test environment. So this affects both Issue SCons#3299 and the PyPy support project. Signed-off-by: Mats Wichmann <mats@linux.com>
@bdbaddog hey the installation guide for jupyter is on my profile. I created a native game in python called Tic-Tac-Toe and the intsllation guide for jupyter is there |
That's interesting. But again why would we use it for this? |
In Jupyter you can investigate a new perspective with each new cell you create while the data and it's transformed copies remain ready, and the former investigations remain visible.
In Jupyter you can investigate a new perspective with each new cell you create while the data and it's transformed copies remain ready, and the former investigations remain visible. |
@thecraftman That's interesting, but you can't run scons inside jupyter without significant work and we can spend that time doing more productive work. If you want to participate in any scons development I suggest you bring your discussion to the scons-users mailing list. |
@bdbaddog alright thanks. |
Proposed fixes for items 2 and 3 are contained in PR #3327 |
@mwichmann - do we still need to resolve any of these issues for Python 3.8.*? Or has the remaining item been kicked down the road to Python 3.9? |
Current scons works fine on 3.8. The imp/importlib thing is still just a warning. The only "problem" I'm seeing is that with 3.8, Python reports the line number differently in certain error situations, at the moment only one test fails because of this. It should be find to close (esp. if you merge #3552!) Notes: ff a statement has multiple lines, Python now reports on the first line. From the test that fails:
Test expectation is based on behavior of past Pythons, so we see this from running the test. Probably the test should be adjusted to not be looking for a specific line number.
|
So barring the unresolved item from the previous comment, I don't see any reason to leave this open, scons is working fine with 3.8. |
Closing per @mwichmann |
This is a work tracker issue to make sure scons works with Python 3.8.
The default warning filters have apparently changed, and now there are lots of warnings issued when running the test suite. As this issue is recorded, a run on Linux using Python 3.7.2 throws three warnings, all relating to the
.sconsign.dblite
file not being closed. With 3.8.0a1 the warning count goes up to about 13750. Since a large number of the tests capture stdout/stderr and judge success by whether they match expected text strings, if warnings appear in stderr those tests will fail. 871 test fails were recorded (up from two on my particular setup), they have not been examined for causes.Updated: using 3.8.0a2, local setup, 193 passes, 874 fail, 132 skip.The problems that jump out the most are warnings that appear everywhere and spill into the stderr of the test; if the test is trying to exactly match stderr (including stderr is empty) will fail. That comes down to these three:
(
cProfile
is one of the modules that gets this special handling)See also PR #3159, which proposes a solution to imp module usage.
.sconsign.dblite
is apparently not closed:SConstruct
, it is apparently never closed.The text was updated successfully, but these errors were encountered: