On 06/11/2015 09:41 PM, Flavio Percoco wrote:
On 11/06/15 16:08 +0100, Gordon Sim wrote:
On 06/11/2015 02:39 PM, Flavio Percoco wrote:
On 11/06/15 09:33 -0400, Ken Giusti wrote:
Yeah, jython's PYTHONPATH points to that directory - it has to in
order to pick up the python sources.
we really sh
On 11/06/15 16:08 +0100, Gordon Sim wrote:
On 06/11/2015 02:39 PM, Flavio Percoco wrote:
On 11/06/15 09:33 -0400, Ken Giusti wrote:
Yeah, jython's PYTHONPATH points to that directory - it has to in
order to pick up the python sources.
we really should clean that cproton.py up. In fact, we pro
On 06/11/2015 02:39 PM, Flavio Percoco wrote:
On 11/06/15 09:33 -0400, Ken Giusti wrote:
Yeah, jython's PYTHONPATH points to that directory - it has to in
order to pick up the python sources.
we really should clean that cproton.py up. In fact, we probably
shouldn't be writing generated files a
y able to replicate this issue.
- Original Message -
From: "Gordon Sim"
To: proton@qpid.apache.org
Cc: "Flavio Percoco" , flape...@gmail.com
Sent: Wednesday, June 10, 2015 12:56:51 PM
Subject: Re: something rotten in the state of... something or other
On 06/10/2015 03:24 P
here cmake is run.
- Original Message -
> From: "Gordon Sim"
> To: proton@qpid.apache.org
> Cc: "Flavio Percoco" , flape...@gmail.com
> Sent: Wednesday, June 10, 2015 12:56:51 PM
> Subject: Re: something rotten in the state of... something or other
>
apache.org
Sent: Tuesday, June 9, 2015 11:57:25 AM
Subject: something rotten in the state of... something or other
I've recently started seeing errors[1] when running tests due to left
over artefacts of previous builds. This happens even for a completely
clean build directory, as some of the
On Tue, 2015-06-09 at 17:38 +0100, Robbie Gemmell wrote:
> I'm not seeing that currently, but I have seen similar sort of things
> a couple of times in the past.
>
> As you mention, some files get created in the source tree (presumably
> by or due to use of Jython), outwith the normal build areas
7:25 AM
Subject: something rotten in the state of... something or other
I've recently started seeing errors[1] when running tests due to left
over artefacts of previous builds. This happens even for a completely
clean build directory, as some of the offending artefacts seem to be
created in the
I'm not seeing that currently, but I have seen similar sort of things
a couple of times in the past.
As you mention, some files get created in the source tree (presumably
by or due to use of Jython), outwith the normal build areas they would
be (which would lead to them being cleaned up), and I th
A betting man would wager it has something to do with the recent changes to the
python setup.py.
I'll have a look into it.
- Original Message -
> From: "Gordon Sim"
> To: proton@qpid.apache.org
> Sent: Tuesday, June 9, 2015 11:57:25 AM
> Subject: somet
I've recently started seeing errors[1] when running tests due to left
over artefacts of previous builds. This happens even for a completely
clean build directory, as some of the offending artefacts seem to be
created in the source tree.
Jython seems to be trying and failing to load cproton. Wi
11 matches
Mail list logo
