On Tue, 2016-01-05 at 03:30 +1100, Kubilay Kocak wrote:
> On 5/01/2016 2:50 AM, clutton wrote:
> > On Tue, 2016-01-05 at 02:37 +1100, Kubilay Kocak wrote:
> > > On 5/01/2016 2:35 AM, clutton wrote:
> > > > On Tue, 2016-01-05 at 02:26 +1100, Kubilay Kocak wrote:
Hi list. Hi python fellows.
I need new numpy, since old one doesn't work nice with python3.
I was porting pitivi and it requires third python, so I'm here.
I'm not a big fun of python, and numpy is a big thing, with a lot of
people relying on it, can I update it by myself?
To be honest I'm lazy a
On Sun, 2015-06-21 at 05:12 +0300, clutton wrote:
> Hi list. Hi python fellows.
>
> I need new numpy, since old one doesn't work nice with python3.
> I was porting pitivi and it requires third python, so I'm here.
>
> I'm not a big fun of python, and numpy is a
On Sun, 2015-06-21 at 08:39 +0200, Olivier Duchateau wrote:
> On Sun, 21 Jun 2015 05:54:16 +0300
> clutton wrote:
>
> > On Sun, 2015-06-21 at 05:12 +0300, clutton wrote:
> > > Hi list. Hi python fellows.
>
> Hi,
>
> > >
> > > I need new
Hi list.
As I can see there are two ways of doing pkg-plist routine.
For pkg-plist which was made for python2 just including USE_PYTHON=
py3kplist would do the trick.
For new python3 ports it's not so straight forward, and when they don't
use setup.py conventions people usually do something
On Tue, 2016-01-05 at 02:26 +1100, Kubilay Kocak wrote:
> On 5/01/2016 2:13 AM, clutton wrote:
> > Hi list.
> >
> > As I can see there are two ways of doing pkg-plist routine.
> >
> > For pkg-plist which was made for python2 just including USE_PYTHON=
On Tue, 2016-01-05 at 02:37 +1100, Kubilay Kocak wrote:
> On 5/01/2016 2:35 AM, clutton wrote:
> > On Tue, 2016-01-05 at 02:26 +1100, Kubilay Kocak wrote:
> > > On 5/01/2016 2:13 AM, clutton wrote:
> > > > Hi list.
> > > >
> > > > As I
