Hi Amaury,
On Tue, Nov 12, 2013 at 10:56 PM, Amaury Forgeot d'Arc
wrote:
>> -Include a prebuilt TkInter???
>
> Not only DLLs, but also header files and .lib.
> cffi need a development environment.
Actually, why? Does tkinter really need more than sqlite3? It seems
that in both cases the buildb
Hi Matti.
On Thu, Nov 14, 2013 at 11:40 AM, matti picus wrote:
> I would suggest that we ship pypy2.2 without a functioning Tkinter
> module, to be consistent with all previous pypy versions :)
Ok, so I believe I can take this:
http://buildbot.pypy.org/nightly/release-2.2.x/pypy-c-jit-67978-2ce
The main problem with Tkinter on windows is that it requires shipping the
tk/tcl runtime It ends up in the /tcl directory. So I need
to figure out a reliable way to do this in package.py, like python does in
http://hg.python.org/cpython/file/c27237d57231/Tools/msi/msi.py (lines 1024
or so) . I woul
Hi Matti,
On Wed, Nov 13, 2013 at 1:01 AM, Matti Picus wrote:
> The sqlite3 issue was easy, we can simply replace the one on the buildbot
> with the 3.6.21 version.
I saw the fix. Thanks!
> I have opened a branch for the tkinter changes, since they require a bit
> more work.
What is the statu
Hi Matti,
Thanks for doing all this work! Fwiw I plan to do the release
tomorrow, but being a few days late on Windows wouldn't be new.
Armin
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
The sqlite3 issue was easy, we can simply replace the one on the
buildbot with the 3.6.21 version.
I have asked the buildbot manager to do the replacement.
I have opened a branch for the tkinter changes, since they require a bit
more work. Those scripts are definitely helpful, thanks.
It seems w
2013/11/12 Ryan Gonzalez
> Ok, just to make sure, this is what is needed:
>
> -Include a prebuilt TkInter???
>
Not only DLLs, but also header files and .lib.
cffi need a development environment.
The instructions in
http://hg.python.org/cpython/file/v2.7.5/Tools/buildbot/external-common.bat
and
h
Hi Tobias,
On Tue, Nov 12, 2013 at 6:20 PM, Tobias Oberstein
wrote:
> And I hope you wouldn't require a commitment by me to fix all issues as a
> prerequisite for being allowed to contribute a buildslave;)
Sure :-) No worry. I'm not doubting (any more) that you have a
chance of actually helpi
Ok, just to make sure, this is what is needed:
-Include a prebuilt TkInter???
-Fix the erratic sqlite versions
Correct me if I'm wrong. Two more questions:
-What version of sqlite is needed
-How the heck do I upload this stuff or something?
On Tue, Nov 12, 2013 at 1:42 PM, Matti Picus wrote:
I have been commenting in the bug reports. The general strategy we
recommend on the windows build page
http://doc.pypy.org/en/latest/windows.html#abridged-method-for-ojit-builds-using-visual-studio-2008
is to download a zip file with all the recommended dependencies, and
build after adding the a
I could probably do the Windows DLL fixes, if someone told me how to upload
the changes...
On Mon, Nov 11, 2013 at 5:53 AM, Armin Rigo wrote:
> Hi all,
>
> Preparing for the next release. The Linux binaries of PyPy 2.2,
> release candidate, are here:
>
> http://buildbot.pypy.org/nightly/releas
On 12.11.2013, at 17:26, Armin Rigo wrote:
> Hi David,
>
> Any reason why the buildbot page
> http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raring
> is the only one missing the section "Force build"? It prevents us
> from asking for a build on the release-2.2.x branch.
>
>
>
> On Tue, Nov 12, 2013 at 10:57 AM, Tobias Oberstein
> wrote:
> > Sure. And yes: we'll be maintaining that slave. We do that for Twisted also
> > ..
>
> I meant not the slave, but the project itself: it's a bit useless to know
> that 42
> tests are failing on *BSD is no-one bothers to do anythi
Hi David,
Any reason why the buildbot page
http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raring
is the only one missing the section "Force build"? It prevents us
from asking for a build on the release-2.2.x branch.
A bientôt,
Armin.
Hi Tobias,
On Tue, Nov 12, 2013 at 10:57 AM, Tobias Oberstein
wrote:
> Sure. And yes: we'll be maintaining that slave. We do that for Twisted also ..
I meant not the slave, but the project itself: it's a bit useless to
know that 42 tests are failing on *BSD is no-one bothers to do
anything about
> Hi Tobias,
>
> On Tue, Nov 12, 2013 at 2:36 AM, Tobias Oberstein
> wrote:
> > Firstly, I could offer to operate a FreeBSD buildslave for PyPy.
>
> That would be nice, if it also comes with occasional fixes (having a
> buildslave
> that nobody looks at is a bit pointless). Can we do this afte
Hi Tobias,
On Tue, Nov 12, 2013 at 2:36 AM, Tobias Oberstein
wrote:
> Firstly, I could offer to operate a FreeBSD buildslave for PyPy.
That would be nice, if it also comes with occasional fixes (having a
buildslave that nobody looks at is a bit pointless). Can we do this
after the release?
A
Hi Armin,
> manpower: we would need someone involved with Windows, OS/X, or the BSDs.
Firstly, I could offer to operate a FreeBSD buildslave for PyPy.
The current one fails ("libssl" missing) and seems very old (FreeBSD 7).
We (Tavendo) operate 2 slaves for the Twisted project (buildbot based).
Re-hi,
The OS/X release candidate (thanks Alex!):
http://cobra.cs.uni-duesseldorf.de/~buildmaster/misc/pypy-2.2-osx.tar.bz2
Armin
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
Hi all,
Preparing for the next release. The Linux binaries of PyPy 2.2,
release candidate, are here:
http://buildbot.pypy.org/nightly/release-2.2.x/
This corresponds to the "release-2.2.x" branch in the repo.
There are a few bug reports that will likely *not* get fixed for lack
of manpower: we
20 matches
Mail list logo
