2010-05-02 15:51:44 by Thomas Klausner | Files touched by this commit (4) |
Log message:
Update to 0.9.9, set LICENSE.
0.9.9
-----
New features:
- C++ struct declarations, 'new' operator, and del for C++ delete.
- As well as the 'not None' modifier for extension type arguments, there
is now 'or None' to explicitly allow passing None. It is planned to make
'not None' the default in a future version. For now, a warning is issued
(once per Pyrex run) if you do not specify one or the other.
- Extension types may have a 'nogc' option to suppress GC support.
Modifications:
- Exceptions caught by an except clause are no longer put into the thread
state and cannot be retrieved using sys.exc_info(). To access the caught
exception, it must be bound to a name in the except clause. A third name
can be supplied to capture the traceback.
- PyString_InternFromString is now exposed under the name 'cintern' because
it is not a complete substitute for 'intern' (it can't handle strings
containing null bytes). [John Arbash Meinel]
- Disabled size check for cimported types because it was generating too
many false positives in the field.
- Added __fastcall calling convention. Also no longer assuming that an
unspecified calling convention is the same as __cdecl.
- Operations between signed and unsigned ints of the same size now have
an unsigned result.
- Py_ssize_t now ranked between long and long long.
- Declaration of __new__ in an extension type is now an error, in
preparation for introducing new semantics.
- Added size_t type, and made sizeof() return it.
Bug fixes:
- When casting the result of a function call to a Python type, the
function could be called twice. [David Martinez]
- __Pyx_GetException was not taking account of the fact that the traceback
could be NULL.
- sizeof(module.typename) did not work. [Daniele Pianu]
|
2010-03-15 13:55:46 by Thomas Klausner | Files touched by this commit (2) |
Log message:
Update to 0.9.8.6:
0.9.8.6
-------
Enhancements:
- Check for gil when calling a function declared 'execpt *' or 'except ?'.
Acquire gil when reporting unraisable exception.
- Added iter2() function for 2-argument form of iter().
Bug fixes:
- Compiler crashed if base class of extension type was incompletely
defined.
- Compiler crash on misspelled method name in property declaration.
[Stefan Behnel]
- Fixed deprecation warnings in 2.6
- Always preserve explicit type casts for non-Python types.
[Alexander Belchenko]
- Added workaround for threading initialisation bug in Python 2.3.
[Lisandro Dalcin]
- Deleting dict item with integer key did not work. [Titus Brown]
- Header files for cimported modules included in wrong order.
[Stephane Drouard]
- Don't allow a member of a ctypedef struct to reference itself.
[Tim Wakeham]
- Compiler crash due to attribute reference in compile-time expression.
[Hoyt Koepke]
- Public extension type attribute with cname didn't work.
[Mark Ellis]
- Memory leak related to exporting C functions. [Lisandro Dalcin]
- Compiler crash on return outside function. [Kurt Smith]
- Scope problem with extension types declared in pxd. [KS Sreeram]
- Calling a builtin method of a subclass of a builtin class did not work.
- Builtin hash() function had wrong return type. [John Arbash Meinel]
Modifications:
- Added 'tags' to .hgignore file. [Kirill Smelkov]
- Disallow overriding a builtin method in a subclass of a builtin class.
|
2009-06-14 20:03:45 by Joerg Sonnenberger | Files touched by this commit (167) |
Log message:
Remove @dirrm entries from PLISTs
|
2008-10-17 14:46:19 by Blair Sadewitz | Files touched by this commit (2) |
Log message:
Update to Pyrex-0.8.9.5. Myriad bug fixes and some new features;
the only changelog I found is very dense (CHANGES.TXT) and I do not
have the time to condense it for inclusion here.
|
2008-04-25 19:37:56 by Tobias Nygren | Files touched by this commit (3) |
Log message:
Update to py-pyrex-0.9.6.4 for Python 2.5 support.
0.9.6.4
-------
Enhancements:
- Functions declared with_gil and external functions declared nogil
are now allowed to have Python arguments and return types.
0.9.6.3
-------
Enhancements:
- C API now only uses a single name in the module namespace
instead of one for each exported C function. [Stefan Behnel]
- Multiple declarations with the same visibility and api options
can now be grouped into a 'cdef' block.
- The 'api' keyword can now be used on extension types to cause
generation of an api.h file when there are no exported C functions.
- Added a getattr3() builtin for the three-argument form of getattr.
0.9.6
-----
New Features:
- Top-level C functions defined in one module can now be used in
another via cimport, and a C API can be produced to allow them
to be used from C code without linking to the extension module.
See "Interfacing with External C Code" and "Sharing Declarations
between Pyrex Modules" in the Language Overview. [Stefan Behnel]
- Facilities added for releasing the GIL around a section of code
and acquiring it on entry to a C function. See "Acquiring and
Releasing the GIL under "Interfacing with External C Code" in
the Language Overview. [Ulisses Furquim, Stefan Behnel]
- Some conditional compilation facilities have been added. See
"Conditional Compilation" under "Language Basics" in the
Language Overview. [Sam Rushing]
Language Changes:
- The __new__ special method of extension types is being renamed
to "__cinit__". For now, you will get a warning whenever you
declare a __new__ method for an extension type, and it will
automatically be renamed to __cinit__ for you. In the next
release, the warning will become an error and no renaming will
occur. In some later release, the __new__ method may be
re-introduced with different semantics. It is recommended that
you begin updating your sources now to use __cinit__.
- A 'raise' statement with no arguments (i.e. to re-raise the
last exception caught) is now required to be lexically within
the 'except' clause which caught the exception. This change was
necessary to efficiently support preserving the exception if an
intervening call raises and catches a different exception.
- The following new reserved words have been added:
with, DEF, IF, ELIF, ELSE
Enhancements:
- Calls to many of the builtin functions are now compiled as
direct calls to Python/C API routines.
- A C type explicitly declared as 'signed' is represented as
such in the generated code, to acommodate platforms where
'char' is unsigned by default. [Francesc Altet]
- Python function can now have an argument of type "unsigned
char". [Alexander Belchenko]
- A new Pyrex.Distutils implementation has been added, which
exports an Extension type supporting the following options:
pyrex_include_dirs - list of dirs to search for Pyrex header files
pyrex_create_listing_file - bool - write errs to listing file
pyrex_cplus - bool - generate C++ code
pyrex_c_in_temp - bool - put generated C files in temp dir
pyrex_gen_pxi - bool - generate .pxi file for public declarations
[Contributed by Billie G. Allie]
- Assert statements can be compiled out by arranging for
PYREX_WITHOUT_ASSERTIONS to be #defined at C compilation time.
[Contributed by Stefan Behnel]
- Support for __index__ slot added to extension types.
[William Stein]
- Exception types now properly checked according to pre or post
2.5 rules as appropriate.
- Py_ssize_t support added. [Stefan Behnel]
- Windows __stdcall and __decl qualifiers now supported.
[Suggested by Eric Devolder]
- Keyword-only argument support added. [Suggested by Stefan Behnel]
- An 'include' statement can now appear anywhere that another kind
of statement or declaration can appear, instead of being restricted
to the top level. [Caio Marcelo]
- Unnecessary PyErr_Occurred() call to check result of
PyString_AsString() no longer made.
- Complicated C types are displayed more readably in error messages.
Modifications:
- A Python function argument declared as "char" or "unsigned
char" now expects a Python integer rather than a string of
length 1, for consistency with the way automatic conversions
are done elsewhere.
- Support for string and tuple exceptions dropped.
0.9.5.1
-------
Modifications:
- NULL in Pyrex source now translated into NULL instead of 0
in C code, to allow for the possibility of calling something
not defined with a prototype in an external header. [Adapted Cat]
0.9.5
-----
Enhancements:
- Exception return values may now be specified by arbitrary
constant expressions of appropriate type, not just literals.
[Stefan Behnel]
- Redundant type check now omitted when passing a literal None
to a function expecting an extension type. [Patch by Sam Rushing]
- New-style classes now allowed as exceptions for compatibility
with Python 2.5 (inheritance from BaseException not currently
checked). [Stefan Behnel]
- Sequence unpacking is now done using the iterator protocol
instead of indexing.
- Allocation of an empty tuple is avoided when making a
Python call with no arguments. [Stefan Behnel]
- Most warnings about unused variables and labels have been
eliminated.
- Support for running the test suite on Linux added but not
yet fully tested. [Based in part on patch by Eric Wald].
- Makefile included for compiling the patched Carbon File module
used by the MacOSX test code.
Modifications:
- Type rules for enums tightened for compatibility with C++.
- Direct assignment from float to int disallowed to prevent
C++ compilation warnings.
- Hex literals left as hex in C code to avoid warnings from
the C compiler about decimal constants becoming unsigned.
|
2007-07-01 18:42:56 by Klaus Heinz | Files touched by this commit (1) |
Log message:
The package supports installation to DESTDIR.
|
2006-10-14 10:04:25 by Thomas Klausner | Files touched by this commit (2) |
Log message:
Update MASTER_SITES and/or HOMEPAGE, from Sergey Svishchev.
|
2006-05-29 17:37:03 by Joerg Sonnenberger | Files touched by this commit (2) |
Log message:
Update to pyrex-0.9.4.1.
Changes in 0.9.4.1:
Tiny bugfix to correct a tab/space problem in the distutils
extension.
Changes in 0.9.4:
LValue Casting Is Dead
I have redesigned the code generator to eliminate the need for lvalue
casting. This means that Pyrex-generated code should now be
gcc4-compatible, although I haven't tested this. Let me know if you find
any remaining lvalue casts; they should be fairly easy to fix now.
C++ Compilable
The generated code should now be compilable as either C or C++
without errors (although there may still be warnings). However, note
that you can still only call C++ functions if they have been declared
"extern C", even if you compile the Pyrex output as C++. I hope to
introduce some C++ interface features soon.
and more.
|
2006-02-06 00:11:50 by Joerg Sonnenberger | Files touched by this commit (4082) |
Log message:
Recursive revision bump / recommended bump for gettext ABI change.
|
2005-12-05 21:51:20 by Roland Illig | Files touched by this commit (1432) |
Log message:
Fixed pkglint warnings. The warnings are mostly quoting issues, for
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in
http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
|