[ZODB-Dev] zodbpickle claim (but OS X is not unix)

[Christian Tismer]

Hi guys,

I very much appreciate the creation of zodbpickle, as it really solves
the problem of pickling compatibility.

What I do not like is if a package makes a claim in its doap record,
is uploaded on PyPI, and the claim is not the reality.

I installed zodbpickle happily on Python 3.3 and assumed that it would
work under 2.7.5 as well, but it does not!

After second reading, I retracted my complaint after realizing that the 
classifiers
don't include the OS X operating system, so here I apologize but beg for 
a fix.

> classifiers=[
> 'Development Status :: 4 - Beta',
> 'License :: OSI Approved :: Zope Public License',
> 'License :: OSI Approved :: Python Software Foundation License',
> 'Programming Language :: Python',
> 'Programming Language :: Python :: 2',
> 'Programming Language :: Python :: 2.6',
> 'Programming Language :: Python :: 2.7',
> 'Programming Language :: Python :: 3',
> 'Programming Language :: Python :: 3.2',
> 'Programming Language :: Python :: 3.3',
> 'Programming Language :: Python :: Implementation :: CPython',
> 'Framework :: ZODB',
> 'Topic :: Database',
> 'Topic :: Software Development :: Libraries :: Python Modules',
> 'Operating System :: Microsoft :: Windows',
> 'Operating System :: Unix',
> ],
>

So on OS X Mountain lion, I get with "$ pip install zodbpickle":

> cc -fno-strict-aliasing -fno-common -dynamic -I/usr/local/include 
> -I/usr/local/opt/sqlite/include -DNDEBUG -g -fwrapv -O3 -Wall 
> -Wstrict-prototypes 
> -I/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/include/python2.7 
> -c src/zodbpickle/_pickle_27.c -o 
> build/temp.macosx-10.8-x86_64-2.7/src/zodbpickle/_pickle_27.o
>
> src/zodbpickle/_pickle_27.c:6254:13: error: void function 
> 'init_pickle' should not return a value [-Wreturn-type]
>
>             return -1;
>
>             ^      ~~
>
> src/zodbpickle/_pickle_27.c:6259:13: error: void function 
> 'init_pickle' should not return a value [-Wreturn-type]
>
>             return -1;
>
>             ^      ~~
>
> 2 errors generated.
>
> error: command 'cc' failed with exit status 1

I would appreciate if that ridiculous but could be removed.
It is a very easy fix and I would actually like to do it.

And while we are at it: How about completion of the module, to let it
define things like DEFAULT_PROTOCOL ?

cheers - Chris

-- 
Christian Tismer             :^)   <mailto:tismer at stackless.com>
Software Consulting          :     Have a break! Take a ride on Python's
Karl-Liebknecht-Str. 121     :    *Starship* http://starship.python.net/
14482 Potsdam                :     PGP key -> http://pgp.uni-mainz.de
phone +49 173 24 18 776  fax +49 (30) 700143-0023
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
       whom do you want to sponsor today?   http://www.stackless.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.zope.org/pipermail/zodb-dev/attachments/20130703/5a247d6d/attachment.html>