00:39
derpydoo has joined #pypy
02:19
jcea has quit [Ping timeout: 255 seconds]
02:52
derpydoo has quit [Quit: derpydoo]
05:52
epony has quit [Ping timeout: 272 seconds]
05:57
otisolsen70 has joined #pypy
07:01
epony has joined #pypy
07:04
epony has quit [Max SendQ exceeded]
07:05
epony has joined #pypy
07:17
epony has quit [Remote host closed the connection]
07:19
epony has joined #pypy
08:07
<
tumbleweed >
mattip: great :)
10:14
Dejan has joined #pypy
10:31
lesshaste has joined #pypy
10:32
lesshaste has quit [Client Quit]
10:32
lesshaste has joined #pypy
10:35
<
mattip >
right, we still have not figured out why creating a virtual environment with "python -m venv" does not properly symlink tkinter
10:35
<
mattip >
please try
10:35
<
mattip >
sudo apt install virtualenv
10:35
<
mattip >
virtualenv -p <path/to/pypy3/bin/pypy> /tmp/venv
10:37
<
lesshaste >
trying it with the new env
10:37
<
tumbleweed >
does it
*need* to symlink virtualenv?
10:37
<
lesshaste >
mattip, that works
10:37
<
tumbleweed >
virtualenv doesn't seem to
10:38
<
lesshaste >
it creates a lot of things in lib
10:39
<
lesshaste >
which python -m venv doesn't creat
10:39
<
tumbleweed >
doesn't for me
10:39
<
tumbleweed >
I assume you're using a pypy.org distributed pypy3, with bundled libs
10:39
<
lesshaste >
virtualenv --version
10:39
<
lesshaste >
virtualenv 20.13.0+ds from /usr/lib/python3/dist-packages/virtualenv/__init__.py
10:40
<
tumbleweed >
which would explain why you need that symlink
10:40
<
lesshaste >
tumbleweed, I am using the pypy3 linked from the pypy website
10:40
<
tumbleweed >
yeah, I understand your issue now
10:40
<
lesshaste >
python --version
10:40
<
lesshaste >
Python 3.8.13 (4b1398fe9d76ad762155d03684c2a153d230b2ef, Mar 29 2022, 07:08:24)
10:40
<
lesshaste >
[PyPy 7.3.9 with GCC 10.2.1 20210130 (Red Hat 10.2.1-11)]
10:41
<
lesshaste >
if there was some way to pip install pypy that would be so much better of course!
10:50
<
mattip >
it seems like a bug in stdlib venv, that we should fix in the pypy we distribute
10:51
<
mattip >
since we call that a "portable pypy"
10:54
<
lesshaste >
that would be great
11:11
jinsun has joined #pypy
12:25
jcea has joined #pypy
12:45
derpydoo has joined #pypy
13:21
lesshaste has quit [Ping timeout: 248 seconds]
13:30
lesshaste has joined #pypy
13:41
sam_ has joined #pypy
14:07
derpydoo has quit [Quit: derpydoo]
14:20
derpydoo has joined #pypy
14:49
otisolsen70 has quit [Quit: Leaving]
15:44
lesshaste has quit [Ping timeout: 272 seconds]
16:22
derpydoo has quit [Ping timeout: 246 seconds]
16:45
derpydoo has joined #pypy
18:56
derpydoo has quit [Quit: derpydoo]
19:17
derpydoo has joined #pypy
19:57
<
hexology >
how does pypy work with traditional cpython c extensions? does it implement a compatibility interface of some kind?
20:07
<
Hodgestar >
hexology: Yes. The compatibility layer is called cpyext.
20:08
<
hexology >
Hodgestar: thanks! and pypy
*also* implements hpy?
20:08
<
hexology >
or is that still WIP?
20:10
<
hexology >
also, i am wondering what are the chances of successfully building a cython library that wraps a c++ library. i don't think there are additional complicated dependencies, but does cython mostly work with cpyext?
20:10
<
hexology >
*successfully building for pypy
22:04
derpydoo has quit [Ping timeout: 255 seconds]
22:10
lesshaste has joined #pypy
23:02
lesshaste has quit [Ping timeout: 248 seconds]
23:19
jinsun has quit [Killed (osmium.libera.chat (Nickname regained by services))]
23:19
jinsun has joined #pypy
23:30
jinsun has quit [Read error: Connection reset by peer]