Author: Armin Rigo <[email protected]>
Branch: 
Changeset: r2137:ca9bd5f5a3d2
Date: 2015-05-30 16:37 +0200
http://bitbucket.org/cffi/cffi/changeset/ca9bd5f5a3d2/

Log:    The next release will be 1.1.0.

diff --git a/c/_cffi_backend.c b/c/_cffi_backend.c
--- a/c/_cffi_backend.c
+++ b/c/_cffi_backend.c
@@ -6053,7 +6053,7 @@
     if (v == NULL || PyModule_AddObject(m, "_C_API", v) < 0)
         INITERROR;
 
-    v = PyText_FromString("1.0.4");
+    v = PyText_FromString("1.1.0");
     if (v == NULL || PyModule_AddObject(m, "__version__", v) < 0)
         INITERROR;
 
diff --git a/c/test_c.py b/c/test_c.py
--- a/c/test_c.py
+++ b/c/test_c.py
@@ -3346,4 +3346,4 @@
 
 def test_version():
     # this test is here mostly for PyPy
-    assert __version__ == "1.0.4"
+    assert __version__ == "1.1.0"
diff --git a/cffi/__init__.py b/cffi/__init__.py
--- a/cffi/__init__.py
+++ b/cffi/__init__.py
@@ -4,8 +4,8 @@
 from .api import FFI, CDefError, FFIError
 from .ffiplatform import VerificationError, VerificationMissing
 
-__version__ = "1.0.4"
-__version_info__ = (1, 0, 4)
+__version__ = "1.1.0"
+__version_info__ = (1, 1, 0)
 
 # The verifier module file names are based on the CRC32 of a string that
 # contains the following version number.  It may be older than __version__
diff --git a/doc/source/cdef.rst b/doc/source/cdef.rst
--- a/doc/source/cdef.rst
+++ b/doc/source/cdef.rst
@@ -373,7 +373,7 @@
    declaration which doesn't use "``...``" is assumed to be exact, but this is
    checked: you get an error if it is not correct.
 
-*  *New in version 1.0.4:* integer types: the syntax "``typedef
+*  *New in version 1.1:* integer types: the syntax "``typedef
    int... foo_t;``" declares the type ``foo_t`` as an integer type
    whose exact size and signness is not specified.  The compiler will
    figure it out.  (Note that this requires ``set_source()``; it does
@@ -400,7 +400,7 @@
    length is completed by the C compiler.
    This is slightly different from "``int n[];``", because the latter
    means that the length is not known even to the C compiler, and thus
-   no attempt is made to complete it.  *New in version 1.0.4:* support
+   no attempt is made to complete it.  *New in version 1.1:* support
    for multidimensional arrays: "``int n[...][...];``".
 
 *  enums: if you don't know the exact order (or values) of the declared
diff --git a/doc/source/conf.py b/doc/source/conf.py
--- a/doc/source/conf.py
+++ b/doc/source/conf.py
@@ -38,16 +38,16 @@
 
 # General information about the project.
 project = u'CFFI'
-copyright = u'2012, Armin Rigo, Maciej Fijalkowski'
+copyright = u'2012-2015, Armin Rigo, Maciej Fijalkowski'
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
 # The short X.Y version.
-version = '1.0'
+version = '1.1'
 # The full version, including alpha/beta/rc tags.
-release = '1.0.4'
+release = '1.1.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
diff --git a/doc/source/installation.rst b/doc/source/installation.rst
--- a/doc/source/installation.rst
+++ b/doc/source/installation.rst
@@ -51,7 +51,7 @@
 
 Download and Installation:
 
-* http://pypi.python.org/packages/source/c/cffi/cffi-1.0.4.tar.gz
+* http://pypi.python.org/packages/source/c/cffi/cffi-1.1.0.tar.gz
 
    - Or grab the most current version by following the instructions below.
 
diff --git a/doc/source/using.rst b/doc/source/using.rst
--- a/doc/source/using.rst
+++ b/doc/source/using.rst
@@ -333,9 +333,9 @@
 function>``).  This means you cannot e.g. pass them to some other C
 function expecting a function pointer argument.  Only ``ffi.typeof()``
 works on them.  To get a cdata containing a regular function pointer,
-use ``ffi.addressof(lib, "name")`` (new in version 1.0.4).
+use ``ffi.addressof(lib, "name")`` (new in version 1.1).
 
-Before version 1.0.4, if you really need a cdata pointer to the function,
+Before version 1.1, if you really need a cdata pointer to the function,
 use the following workaround:
 
 .. code-block:: python
@@ -746,7 +746,7 @@
 
 3. ``ffi.addressof(<library>, "name")`` returns the address of the
 named function or global variable from the given library object.
-*New in version 1.0.4:* for functions, it returns a regular cdata
+*New in version 1.1:* for functions, it returns a regular cdata
 object containing a pointer to the function.
 
 Note that the case 1. cannot be used to take the address of a
diff --git a/doc/source/whatsnew.rst b/doc/source/whatsnew.rst
--- a/doc/source/whatsnew.rst
+++ b/doc/source/whatsnew.rst
@@ -3,7 +3,7 @@
 ======================
 
 
-1.0.4
+1.1.0
 =====
 
 * Out-of-line API mode: we can now declare integer types with
@@ -14,13 +14,19 @@
   (as fields or as globals) with ``int n[...][...]``.  Before, only the
   outermost dimension would support the ``...`` syntax.
 
-* Issue #175: in ABI mode: we now support any constant declaration,
+* Out-of-line ABI mode: we now support any constant declaration,
   instead of only integers whose value is given in the cdef.  Such "new"
   constants, i.e. either non-integers or without a value given in the
   cdef, must correspond to actual symbols in the lib.  At runtime they
   are looked up the first time we access them.  This is useful if the
   library defines ``extern const sometype somename;``.
 
+* ``ffi.addressof(lib, "func_name")`` now returns a regular cdata object
+  of type "pointer to function".  You can use it on any function from a
+  library in API mode (in ABI mode, all functions are already regular
+  cdata objects).  To support this, you need to recompile your cffi
+  modules.
+
 * Issue #198: in API mode, if you declare constants of a ``struct``
   type, what you saw from lib.CONSTANT was corrupted.
 
@@ -29,12 +35,6 @@
   of ``package/_ffi.py``.  Also fixed: in some cases, if the C file was
   in ``build/foo.c``, the .o file would be put in ``build/build/foo.o``.
 
-* ffi.addressof(lib, "func_name") now returns a regular cdata object
-  of type "pointer to function".  You can use it on any function from a
-  library in API mode (in ABI mode, all functions are already regular
-  cdata objects).  To support this, you need to recompile your cffi
-  modules.
-
 
 1.0.3
 =====
diff --git a/setup.py b/setup.py
--- a/setup.py
+++ b/setup.py
@@ -144,7 +144,7 @@
 
 `Mailing list <https://groups.google.com/forum/#!forum/python-cffi>`_
 """,
-        version='1.0.4',
+        version='1.1.0',
         packages=['cffi'] if cpython else [],
         package_data={'cffi': ['_cffi_include.h', 'parse_c_type.h']}
                      if cpython else {},
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit

Reply via email to