cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | the secret reason for us trying to get PyPy users: to test the JIT well enough that we're somewhat confident about it
marky1991 has quit [Read error: Connection reset by peer]
adamholmberg has quit [Remote host closed the connection]
<lcollini>
Hi everybody, I'm not sure if this is a thing but I'll quickly introduce myself. I met Ronan at EuroScipy in Trento and did a sprint with him. I've set up my system to contribute to pypy, for now I'll try to fix the failed tests of the python 3.6 version.
<cfbolz>
lcollini: cool, welcome!
<cfbolz>
lcollini: please feel free to ask any questions if you run into trouble, and thanks for working on python 3.6 :-)
<lcollini>
I just ran the code on python 3.6.6 to check if it gave any warning and it's not giving me any warning. So should the test be changed since python 3.6.6 is not giving warnings with that code?
<cfbolz>
lcollini: those tests are from the standard library of CPython. so you're saying that the test fails on CPython?
<lcollini>
I'm saying that if I run the code of the test on cpython it does not give warnings, for what i understood the test fails because no warnings are triggered but that does not make sense to me, so i must have got something wrong
<cfbolz>
lcollini: could you check what the file looks like in CPython's standard library?
<cfbolz>
is the test in there the same?
<lcollini>
yes, it is the same
<cfbolz>
lcollini: so something is weird ;-)
<cfbolz>
if it's the same, it must pass under CPython
<lcollini>
that's what i thought. so it should raise a warning when run in CPython
<cfbolz>
yes. if you can't get the test to pass under CPython we are missing something
<cfbolz>
lcollini: eg what happens if you run python3 -m test.test_string_literals
<lcollini>
if i run that i get an error saying: /usr/bin/python3: No module named test.__main__; 'test' is a package and cannot be directly executed
<lcollini>
Earlier i was just executing the for loop that should have raised the warning. maybe i did that wrong
<cfbolz>
lcollini: just in the python console?
<cfbolz>
lcollini: note that DeprecationWarnings are ignored by default
<cfbolz>
so you should try to see whether you get a warning if you run with python3 -Wall