On 11/3/06, Torgil Svensson <[EMAIL PROTECTED]> wrote:
> class struct_type(Structure):
> _fields_ = []
>
> ...
> ... which is somewhat static in nature. How do you create "structures"
> dynamically?
>
You can put the above in a function that takes fields as an argument, or
type('struc
On 11/3/06, Torgil Svensson <[EMAIL PROTECTED]> wrote:
> class struct_type(Structure):
> _fields_ = []
>
> ...
> ... which is somewhat static in nature. How do you create "structures"
> dynamically?
>
You can put the above in a function that takes fields as an argument, or
type('struc
> > It seems to me that at the python level, there's not much reason to
> > choose the dtypes proposal over ctypes.
I disagree. I can see a point in unifying ctypes and dtypes but in my
mindset they've got two different scopes.
ctypes is an interface to the c language
dtype is a data description
On 11/2/06, A. M. Archibald <[EMAIL PROTECTED]> wrote:
On 01/11/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:> And it may be a good idea to also have a get_ctype method or some-such> on the ctypes attribute so that one could get a "ctypes description"
> from the NumPy data-type.It seems to me tha
On 01/11/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> And it may be a good idea to also have a get_ctype method or some-such
> on the ctypes attribute so that one could get a "ctypes description"
> from the NumPy data-type.
It seems to me that at the python level, there's not much reason to
Alexander Belopolsky wrote:
> On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> ...
>
>> Please understand what I meant. I meant putting effort into getting
>> PyArray_DescrConverter to allow ctypes inputs and convert to the
>> appropriate PyArray_Descr * structure. I already understa
On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
> I'm recruiting more comments on python-dev regarding my two proposals
> for improving Python's native ability to share ndarray-like information.
>
I believe there are another really important reason to support
Travis's proposal.
Python s
On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> No, it's not that simple. We have a headache whenever we want to do
> something like I just did and separate out the concepts of what makes a
> Python Object a Python object. Now, we don't just modify a simple
> C-structure (PyArray_Descr
Grr, I wrote something up (it was wonderfully eloquent and convincing -- trust me!), but the gmane interface seems to have lost it (I posted two things before responding to the two "authorization requested" emails, and only one of the two things ever got posted it seems.)
--bbOn 11/2/06, Lisandro
On 10/31/06, Bill Baxter <[EMAIL PROTECTED]> wrote:
> One thing I see with PIL and Matplotlib and PyOpenGL is that they're having
> to add specific support for Numpy and numeric and numarray and PIL and
> ctypes etc.
This is a real problem, and a waste of developing time, because we
lack a **gener
One thing I see with PIL and Matplotlib and PyOpenGL is that they're having to add specific support for Numpy and numeric and numarray and PIL and ctypes etc.I'm also in the camp that doesn't really understand this stuff well enough to really argue in favor of it, but would the proposed extensions
On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
...
> Please understand what I meant. I meant putting effort into getting
> PyArray_DescrConverter to allow ctypes inputs and convert to the
> appropriate PyArray_Descr * structure. I already understand ctypes
> objects. I want the dtype()
On 11/31/06, Fernando Perez <[EMAIL PROTECTED]> wrote:
> Fernando Perez wrote:
> ps - one more thing. This guy:
>
> http://blog.vrplumber.com/
>
> has been rewriting the OpenGL bindings using ctypes, and I've seen
> posts from him about numpy (in his blog). He might be able to
> contribute some
Sasha wrote:
>On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
>
>
>>Please read my posts about the Python type-object verses normal Python
>>Object situation. That really is the crux of the matter.
>>
>>
>>
>I read the whole python-dev thread before replying. I may be a little
>b
Sasha wrote:
>On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
>
>Yes, this is the key. I think we should better understand ctypes
>limitations before proposing an alternative.
>
I already understand it's practical limitations --- type objects as
data-type instances is too bulky and
On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Please read my posts about the Python type-object verses normal Python
> Object situation. That really is the crux of the matter.
>
I read the whole python-dev thread before replying. I may be a little
biased because I never liked somewha
Sasha wrote:
>On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
>
>>I'm recruiting more comments on python-dev regarding my two proposals
>>for improving Python's native ability to share ndarray-like information.
>>
>>
>>
>
>I would love to help, but I feel that I will be on the othe
Sasha wrote:
>On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
>
>>I'm recruiting more comments on python-dev regarding my two proposals
>>for improving Python's native ability to share ndarray-like information.
>>
>>
>>
>
>I would love to help, but I feel that I will be on the othe
On Tue, 31 Oct 2006, Sasha apparently wrote:
> I think we should attempt to implement a ctypes approach
You are probably aware that Travis has addressed this at some length on
comp.python.devel (for example
http://article.gmane.org/gmane.comp.python.devel/84661
http://article.gmane.org/gmane.co
On 10/31/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
> I'm recruiting more comments on python-dev regarding my two proposals
> for improving Python's native ability to share ndarray-like information.
>
I would love to help, but I feel that I will be on the other side of
the disagreement. (Th
Perhaps you could please elaborate on what you regard as "the issue(s)"
and "what's at stake"? I'm still comparatively new (been using python
and numpy circa 8-9 months), but so far I haven't encountered any
problems I'd attribute to "Python's ... [in]ability to share
ndarray-like information"
On Tue, 31 Oct 2006, Travis Oliphant wrote:
> Please, please. If you want Python to grow support for
> the array interface (or something like it), then please
> speak up on python-dev.
The easiest access to this discussion for me was
http://news.gmane.org/group/gmane.comp.python.devel/
I cann
22 matches
Mail list logo
