as I am also interested in Pyrex support, here is a list of things that I would like to see in PyDev:
- Associate *.pyx, *.pxd and *.pxi files with a "Pyrex Editor" (which behaves almost the same as the Python Editor with the below differences)
- Don't do syntax checking on Pyrex files (this is currently the major problem using the regular Python Editor for Pyrex code. Whenever there is some special Pyrex construct, the editor thinks this is a syntax error. I suppose checking the Pyrex syntax would require a run of the Pyrex compiler, but personally, I think this is not necessary. I have to run the compiler anyway to build the module, so I will catch the errors at that time).
- Syntax highlighting for the special Pyrex constructs (this is only a minor issue, the regular Python syntax highlighting works well enough for me. The most used extra keywords are probably "cdef", "cimport" and the regular C data types).
- Functions/methods/classes (maybe even attributes) that are defined using "cdef" should also appear in the outliner.
The workaround of simply using the Python Editor for Pyrex code is already usable but the above things are not supported in this case (especially the "false errors" are distracting and "hide" real errors).
Thanks,
- Matthias -
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=211477
Originator: NO
Hi,
as I am also interested in Pyrex support, here is a list of things that I would like to see in PyDev:
- Associate *.pyx, *.pxd and *.pxi files with a "Pyrex Editor" (which behaves almost the same as the Python Editor with the below differences)
- Don't do syntax checking on Pyrex files (this is currently the major problem using the regular Python Editor for Pyrex code. Whenever there is some special Pyrex construct, the editor thinks this is a syntax error. I suppose checking the Pyrex syntax would require a run of the Pyrex compiler, but personally, I think this is not necessary. I have to run the compiler anyway to build the module, so I will catch the errors at that time).
- Syntax highlighting for the special Pyrex constructs (this is only a minor issue, the regular Python syntax highlighting works well enough for me. The most used extra keywords are probably "cdef", "cimport" and the regular C data types).
- Functions/methods/classes (maybe even attributes) that are defined using "cdef" should also appear in the outliner.
The workaround of simply using the Python Editor for Pyrex code is already usable but the above things are not supported in this case (especially the "false errors" are distracting and "hide" real errors).
Thanks,
- Matthias -