I see a Lets Encrypt cert there:
https://ismycertexpired.com/check?domain=www.pypy.org
m
On Mon, Sep 12, 2022 at 10:46:27PM -0400, matti picus wrote:
> Something changed over the last few days. I now get this message when trying
> to
> figure out what is wrong with the https://www.pypy.org:
>
On Wed, Apr 06, 2022 at 10:57:13AM +0300, Matti Picus wrote:
> On 6/4/22 00:59, Matt Billenstein via pypy-dev wrote:
>
> > Hi, python2 is really long in the tooth - when are we planning to upgrade
> > the
> > buildbot master? I cannot install python2 from homebrew on m
On Tue, Apr 05, 2022 at 09:59:24PM +, Matt Billenstein via pypy-dev wrote:
> Hi, python2 is really long in the tooth - when are we planning to upgrade the
> buildbot master? I cannot install python2 from homebrew on macos any longer,
> the system python2 is really really old...
N
Hi, python2 is really long in the tooth - when are we planning to upgrade the
buildbot master? I cannot install python2 from homebrew on macos any longer,
the system python2 is really really old...
thx
m
--
Matt Billenstein
m...@vazor.com
http://www.vazor.com/
__
Starting tomorrow morning PST, I'm moving, so it should be back sometime
Saturday evening or perhaps Monday if I have trouble with the internet
self-install.
thx
m
--
Matt Billenstein
m...@vazor.com
http://www.vazor.com/
___
pypy-dev mailing list
pypy
On Tue, Sep 01, 2020 at 03:58:13PM -0600, gyro funch wrote:
> Hi,
>
> I am interested in building pypy 3.6 on Ubuntu 20.04 LTS.
>
> ...
> $ pypy3 ../../rpython/bin/rpython --opt=jit
>
> This leads to a series of SyntaxErrors related to print. It appears that
> the build-related files in the bran
And we're back...
m
On Tue, Jul 07, 2020 at 09:04:55AM -0700, Matt Billenstein wrote:
> I won't have physical access to this machine until mid-August now, so it
> probably won't be available again until then.
>
> m
>
--
Matt Billenstein
m...@vazor.com
http://www.vazor.com/
___
On Wed, Jul 08, 2020 at 11:12:45AM +0300, Matti Picus wrote:
> I think 8GB is fine. Tell me when you would like to give it a shot. I have no
> idea what version of macOS is the minimum needed. You can set it up following
> https://foss.heptapod.net/pypy/buildbot/-/blob/branch/default/README_BUILDSL
I won't have physical access to this machine until mid-August now, so it
probably won't be available again until then.
m
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
On Mon, Jun 01, 2020 at 08:49:29AM +0300, Matti Picus wrote:
> I think porting the current make_portable to macOS would not be so
> terrible. Since most of the work has been done for linux64/linux32, it is
> "just" a matter of adjusting the workflow. I opened
> https://foss.heptapod.net/pypy/pypy/i
Attempting a custom build outside of the buildbot and I'm linking system
libffi, but it's not picking up gettext out of /usr/local - is there any way to
tell the toolchain to not link anything in /usr/local?
$ otool -L libpypy3-c.dylib
libpypy3-c.dylib:
@rpath/libpypy3-c.dylib (compatibility v
On Sun, May 31, 2020 at 11:39:31PM +0200, Yury V. Zaytsev wrote:
> On Sun, 31 May 2020, Matt Billenstein via pypy-dev wrote:
>
> > I think if you want to ship portable binary packages, they should be
> > self-contained - you can't really know what Apple is going to inc
On Sun, May 31, 2020 at 01:09:11AM +0300, Matti Picus wrote:
> It seems the pypy 7.3.1 tarball is broken on macOS since it links to an
> installation of libffi in the non-standard location
> `/usr/local/opt/libffi/lib/
> libffi.6.dylib`, see issue 3229[0].
I'm going to remove the homebrew ffi fro
On Tue, Apr 07, 2020 at 06:02:00PM +0300, Matti Picus wrote:
>
> On 7/4/20 5:44 pm, Guillaume Dubé wrote:
> >
> > Hi Matti,
> >
> > Thank you for the quick reply
> >
> > I’ve downloaded pypy-c-jit-latest-osx64.tar.bz2 and extracted in
> > /usr/local/pypy3-7.3.1
> >
> > I’m getting the followin
On Thu, Feb 27, 2020 at 11:54:45AM -0600, Jerry Spicklemire wrote:
> Thanks for all the replies.
> Dan, re:
>
> "I think you mostly don't want u'foo' in 3.x or b'foo' in 2.x"
>
> Actually, I don't want either, anywhere.
>
> If UTF8 is used internally, and ASCII is
> already UTF8, then it is all
On Wed, Feb 26, 2020 at 09:08:49AM -0600, Jerry Spicklemire wrote:
> In other words, within the range of ASCII characters, the UTF8 representation
> is identical to the ASCII representation. So, does that mean we can put the
> 'u'
> and 'b' prefix nightmares behind us? It would help some diehards
16 matches
Mail list logo
