00:10
lritter has quit [Ping timeout: 258 seconds]
00:11
lritter has joined #pypy
00:23
todda7 has quit [Ping timeout: 264 seconds]
00:35
lritter has quit [Quit: Leaving]
01:01
todda7 has joined #pypy
01:09
<
njs >
mattip: Python's 'atexit' is implemented by the interpreter, so the semantics are the same across platforms I think
01:33
jcea has quit [Quit: jcea]
01:43
jvesely has quit [Quit: jvesely]
01:43
todda7 has quit [Ping timeout: 246 seconds]
01:56
jvesely has joined #pypy
01:56
jvesely has quit [Remote host closed the connection]
01:58
jvesely has joined #pypy
01:58
inhahe has joined #pypy
02:13
jvesely has quit [Quit: jvesely]
02:33
mgedmin has joined #pypy
02:33
jvesely has joined #pypy
02:37
jvesely has quit [Client Quit]
02:51
jvesely has joined #pypy
02:57
jvesely has quit [Remote host closed the connection]
02:58
jvesely has joined #pypy
03:28
Rhy0lite has quit [Quit: This computer has gone to sleep]
04:23
mukundan314 has joined #pypy
04:24
epsilonKNOT has quit [Ping timeout: 258 seconds]
04:33
mukundan314 is now known as mukundan3141
04:33
mukundan3141 is now known as mukundan314
04:48
<
mattip >
njs: I mean the _exit() C function call which will immediately terminate the program on POSIX systems, maybe _Exit is an alternative spelling
05:10
_whitelogger has joined #pypy
05:37
epsilonKNOT has joined #pypy
05:39
<
mattip >
it seems wb_before_move in general gives a ~5% gain, but then there are benchmarks that are slower
05:40
<
mattip >
the permalink on the comparison page doesn't work properly, here is how I got a comparison to the latest linux64:
05:41
<
mattip >
then in executables use only pypy-jit-64 latest in branch 'wb_before_move' and pypy-jit-64 latest
05:41
<
mattip >
then at the top of the page "horizontal"
05:42
<
mattip >
and normalization (all the way at the bottom) pypy-jit-4-latest
05:45
<
mattip >
I think some of the benchmarks that show wb_before_move as slower are jittery, like sympy_sum
06:04
oberstet has joined #pypy
06:07
mukundan314 has quit [Remote host closed the connection]
06:56
dddddd has quit [Ping timeout: 260 seconds]
07:17
<
arigo >
mattip: I'm not up to digging much into these cases, I
*think* it's good enough that it doesn't seem to have massive negative effects (and it has massive positive effects in the issue's code)
07:18
<
mattip >
Once we sort out the macOS packaging issues I would like to do a 7.3.2
07:18
<
mattip >
so next week I think
07:19
* mattip
still dreaming of a python3.7 alpha
07:20
<
mattip >
I wonder what project's test suite would flush out important 3.7 problems that we should fix before an alpha
07:21
<
arigo >
nothing seems to have been done about 're' so far
07:24
todda7 has joined #pypy
07:31
<
mattip >
is 're' broken for normal use cases?
07:31
<
arigo >
I don't know
07:31
<
arigo >
people mentioned here that the re engine changed in 3.7
07:32
<
arigo >
I don't know more though
07:36
<
mattip >
we have that packaging script that runs against the top 1000 pypi packages, but there is no standard way to run test suites
07:36
<
mattip >
so it only checks if the package can be installed
07:38
todda7 has quit [Ping timeout: 240 seconds]
08:00
todda7 has joined #pypy
08:31
mwhudson has quit [Ping timeout: 244 seconds]
08:35
<
arigo >
it's c1aa5a9acd68 I am talking about
08:42
todda7 has quit [Ping timeout: 260 seconds]
08:49
marvin__ has quit [Remote host closed the connection]
08:49
marvin has joined #pypy
08:55
mwhudson has joined #pypy
08:55
mwhudson has quit [Changing host]
08:55
mwhudson has joined #pypy
09:02
todda7 has joined #pypy
09:07
<
mattip >
got it, but I wonder how many of the failures of test_re.py are used by packages/end-users
09:28
todda7 has quit [Read error: No route to host]
09:31
<
cfbolz >
I started looking into sre but then got distracted
09:32
<
cfbolz >
It's not superhard it's just that most of the bytecode numbers changed for not a lot of reasons
09:33
<
cfbolz >
There are also a couple of new ones but they don't seem hard to implement or are variants of ones that we already have
09:34
<
cfbolz >
Ist nobody else get to it, I will probably resume working on the problem from July on
09:52
otisolsen70 has joined #pypy
10:17
Dejan has joined #pypy
10:17
Dejan has quit [Changing host]
10:17
Dejan has joined #pypy
11:03
marky1991 has quit [Ping timeout: 264 seconds]
11:46
<
mattip >
both with py3.6 and py3.7, so I guess 3.7 is no worse than 3.6 ;/
11:59
<
Dejan >
NumPy will drop 3.6 support it seems
12:00
<
Dejan >
actually, mattip you mentioned that here yesterday, did you?
12:01
<
mattip >
numpy won't until December, but other packages in the scientific data stack might
12:02
<
mattip >
that is why I am trying to figure out if we are ready for a py3.7 release
12:02
<
mattip >
alpha release
12:12
dddddd has joined #pypy
12:16
YannickJadoul has joined #pypy
12:37
Rhy0lite has joined #pypy
13:12
marky1991 has joined #pypy
13:50
BPL has joined #pypy
14:01
marky1991 has quit [Remote host closed the connection]
14:01
marky1991 has joined #pypy
14:23
jacob22 has quit [Read error: Connection reset by peer]
14:23
jacob22 has joined #pypy
14:38
lritter has joined #pypy
15:46
marky1991 has quit [Remote host closed the connection]
15:47
marky1991 has joined #pypy
17:02
YannickJadoul has quit [Quit: Leaving]
17:13
marky1991 has quit [Remote host closed the connection]
17:14
marky1991 has joined #pypy
17:52
marky1991 has quit [Remote host closed the connection]
17:52
marky1991 has joined #pypy
18:12
marky1991 has quit [Remote host closed the connection]
18:13
marky1991 has joined #pypy
18:24
marky1991 has quit [Remote host closed the connection]
18:25
marky1991 has joined #pypy
18:29
marky1991 has quit [Ping timeout: 240 seconds]
18:47
Dejan has quit [Quit: Leaving]
20:16
marky1991 has joined #pypy
20:29
oberstet has quit [Quit: Leaving]
21:42
otisolsen70 has quit [Ping timeout: 240 seconds]
21:57
BPL has quit [Quit: Leaving]
23:39
Ninpo has quit [Ping timeout: 264 seconds]
23:44
Ninpo has joined #pypy