Re: [pypy-dev] [pypy-commit] pypy refactor-translator: Remove fork_before option (unused).

2013-09-05 Thread Armin Rigo
Hi, On Wed, Sep 4, 2013 at 4:44 PM, Antonio Cuni wrote: > Hi Manuel, > > did you actually kill support for this feature? I find it occasionally > useful: e.g. when working on the JIT you can use --fork-before=pyjitpl and > avoid to annotate/rtype the whole pypy interp when you change something.

Re: [pypy-dev] Buildbot update

2013-09-05 Thread David Schneider
On 04.09.2013, at 10:08, Matti Picus wrote: > TL;DR : Do you have any hints/instructions as to how to test a new buildbot > task? > > Thanks for the update, it seems to have cleaned up much of the code base. > I would like to add a task that installs the python part of a numpy > installation

[pypy-dev] Specifying lib locations?

2013-09-05 Thread Skip Montanaro
Trying to build from source, I get the complaint, "failed to guess where ncurses is installed." On our systems they are in decidedly nonstandard locations. A bit of googling didn't turn up an obvious solution, and rpython --help didn't spew any lines that looked promising. How do I specify nonstand

Re: [pypy-dev] Specifying lib locations?

2013-09-05 Thread Armin Rigo
Hi Skip, On Thu, Sep 5, 2013 at 5:29 PM, Skip Montanaro wrote: > Trying to build from source, I get the complaint, "failed to guess > where ncurses is installed." The logic is spread on pages upon pages of pypy/module/_minimal_curses/fficurses.py, including trying with the "pkg-config" or "ncurs

Re: [pypy-dev] Specifying lib locations?

2013-09-05 Thread Davide Del Vento
Skip The way we solved this problem on our system is creating a compiler wrapper. This is a non-pypy-specific solution, which we believe is very effective and convenient. The "normal" gcc is installed in non-standard out-of-path location. A gcc shell script is installed instead. Such a scrip

Re: [pypy-dev] Specifying lib locations?

2013-09-05 Thread Skip Montanaro
> The way we solved this problem on our system is creating a compiler wrapper. > This is a non-pypy-specific solution, which we believe is very effective and > convenient. > > The "normal" gcc is installed in non-standard out-of-path location. A gcc > shell script is installed instead. Such a scrip

[pypy-dev] Free SSL certificate for https://bugs.pypy.org

2013-09-05 Thread anatoly techtonik
*.python.org uses free SSL certificate from http://www.startssl.com/?app=1 PyPy can use this too to get rid of annoying security exceptions for https://bugs.pypy.org and other parts. -- anatoly t. ___ pypy-dev mailing list pypy-dev@python.org https://mai

Re: [pypy-dev] Free SSL certificate for https://bugs.pypy.org

2013-09-05 Thread Armin Rigo
Hi Anatoly, On Thu, Sep 5, 2013 at 8:53 PM, anatoly techtonik wrote: > *.python.org uses free SSL certificate from http://www.startssl.com/?app=1 > > PyPy can use this too to get rid of annoying security exceptions for > https://bugs.pypy.org and other parts. Thanks ! Fwiw, we will soon move bu

Re: [pypy-dev] Free SSL certificate for https://bugs.pypy.org

2013-09-05 Thread anatoly techtonik
Cool. Any prospects on when it can happen (or a link to tracker issue)? Is it a move to pydotorg infrastructure? Btw, I found a bug about SSL issue - https://bugs.pypy.org/issue723 -- anatoly t. On Thu, Sep 5, 2013 at 10:45 PM, Armin Rigo wrote: > Hi Anatoly, > > On Thu, Sep 5, 2013 at 8:53 PM,

Re: [pypy-dev] Free SSL certificate for https://bugs.pypy.org

2013-09-05 Thread Alex Gaynor
Yes, we're in the process of moving bugs.pypy.org to be handled by the PSF infrastructure group Alex On Thu, Sep 5, 2013 at 12:51 PM, anatoly techtonik wrote: > Cool. Any prospects on when it can happen (or a link to tracker issue)? > Is it a move to pydotorg infrastructure? > > Btw, I found a