Hi Toby,
>> The less expertise a package assumes from its users, the better and more
>> useful it usually is :-) Python's success is the best evidence :-)
>
> Right. What sort of first steps tutorials should I include? I don't know
> what would be too basic..
Just a few basic examples on how to
Hey all,
So I've fixed all the below stuff (but I've not yet uploaded a new
package to the PPA). I just want a small piece of advice (below).
Karl Rupp writes:
>>> * Okay, so let's try to print individual elements of A and B:
>>>A(1,1);# error!
>>>A.item(1,1); # error!
>>>A
Hi Toby,
>> * Found the PyViennaCL documentation, but it was *not* installed
>> automatically, but listed as 'suggested' package. I think this can be
>> addressed in the installation instructions and does not require a change
>> in behavior.
> Sure, I only listed it as suggested because the HTML
Dear Karl,
Karl Rupp writes:
> * Installation: Works nicely from the PPA, no problems with my Linux
> Mint Maya (based on Ubuntu 12.04, so this is expected).
Good! :)
> * Found the PyViennaCL documentation, but it was *not* installed
> automatically, but listed as 'suggested' package. I think
Hi Toby,
alright, finally some first testing experience. This is a bunch of very
basic information, as I'm only now in the state where I can mimic a new
PyViennaCL user ;-)
* Installation: Works nicely from the PPA, no problems with my Linux
Mint Maya (based on Ubuntu 12.04, so this is expecte
Hi again,
Karl Rupp writes:
> Okay, 1.5.0 is out, I'll fall asleep now and start testing pyViennaCL asap.
Yes -- get some rest, and by the morning, some fixed pyviennacl packages
will be available ready for testing in the Ubuntu PPA :)
Cheers,
Toby
---
Hey,
>> Ah, I see. What about setting the defines globally through the CMake
>> build system? That should be far less error-prone and easier to configure...
>
> Quite...! :)
:-)
Okay, 1.5.0 is out, I'll fall asleep now and start testing pyViennaCL asap.
Best regards,
Karli
--
Karl Rupp writes:
> Ah, I see. What about setting the defines globally through the CMake
> build system? That should be far less error-prone and easier to configure...
Quite...! :)
--
Rapidly troubleshoot problems befo
Hey,
> So it turned out that it wasn't anything to do with my previous error,
> just that having split up the files, I had not put the OpenCL #define in
> all the right places.
>
> In fact, come to think of it, that may be the cause of the shared_ptr
> troubles. Agh!!
Ah, I see. What about setti
Toby St Clere Smithe
writes:
> I'll dig around some more...
So it turned out that it wasn't anything to do with my previous error,
just that having split up the files, I had not put the OpenCL #define in
all the right places.
In fact, come to think of it, that may be the cause of the shared_ptr
Hi Karl,
Karl Rupp writes:
> > So I've uploaded PyViennaCL packages which don't have the shared_ptr
>> troubles that my previous ones did (in the end, I split what used to be
>> a single Python extension into many smaller extensions under one package
>> namespace). These packages seem mostly to
Hi Toby,
> So I've uploaded PyViennaCL packages which don't have the shared_ptr
> troubles that my previous ones did (in the end, I split what used to be
> a single Python extension into many smaller extensions under one package
> namespace). These packages seem mostly to work, and (for instance)
Hi all,
So I've uploaded PyViennaCL packages which don't have the shared_ptr
troubles that my previous ones did (in the end, I split what used to be
a single Python extension into many smaller extensions under one package
namespace). These packages seem mostly to work, and (for instance), pass
my
13 matches
Mail list logo
