Hi all,
Right now the "pypy" executable looks for its lib-python/lib_pypy
directories by starting from the path of the "pypy" executable and
going up. That path is derived from the C-level argv[0], on which we
try once to call readlink() if it is a symlink. That logic is in
pypy.module.sys.initp
Hi Diana,
Answering you on the pypy-dev mailing list. The question is about
Win64 support
(http://doc.pypy.org/en/latest/windows.html#what-is-missing-for-a-full-64-bit-translation):
On 19 September 2016 at 14:34, Popa, Diana wrote:
> First of all, I started by translating PyPy on win64 with a
Le 17/09/16 à 10:02, Armin Rigo a écrit :
Hi Ronan, hi all,
Can we fix a date after which we stop needing to update pypy 3.3? It
is a (minor) mess that, whenever I find a bug or small missing feature
in pypy 3.5, I usually try first to see if it should be done in the
py3k (3.3) branch or direct
I added PyPy to the list of PyConZA sprint topics --
https://za.pycon.org/news/sprints/.
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
Hi Simon,
On 20 September 2016 at 18:08, Simon Cross wrote:
> I added PyPy to the list of PyConZA sprint topics --
> https://za.pycon.org/news/sprints/.
Thanks!
Armin
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listin
Hi Ronan,
On 20 September 2016 at 17:34, Ronan Lamy wrote:
> For all remaining linux64 test failures, we should either fix them or
> explicitly decide not to bother (e.g. in cpyext). This mostly means
> reviewing and stabilising the buffer interface. Some issues also need to be
> fixed, like #227
> On Sep 20, 2016, at 10:00 AM, Armin Rigo wrote:
>
> Hi Ronan,
>
> On 20 September 2016 at 17:34, Ronan Lamy wrote:
>> For all remaining linux64 test failures, we should either fix them or
>> explicitly decide not to bother (e.g. in cpyext). This mostly means
>> reviewing and stabilising the b
