fixed object.__new__ error message for >=2.7.4

Looks like this error message changed in 2.7.4... I don't know how you want to handle this kind of thing in general but this would make it a lot more convenient for me to run all the tests.
What is the relationship between the values in `include/patchlevel.h` and
those in `core/options.h`?


On Wed, Aug 20, 2014 at 5:28 PM, Kevin Modzelewski <notifications@github.com
> wrote:

> In src/core/options.h:
>
> > @@ -22,7 +22,11 @@ extern "C" {
> >  extern int GLOBAL_VERBOSITY;
> >  #define VERBOSITY(x) GLOBAL_VERBOSITY
> >  // Version number we're targeting:
> > -extern int PYTHON_VERSION_MAJOR, PYTHON_VERSION_MINOR, PYTHON_VERSION_MICRO;
> > +extern int PYTHON_VERSION_MAJOR, PYTHON_VERSION_MINOR, PYTHON_VERSION_MICRO, PYTHON_VERSION_HEX;
> > +
> > +inline int version_hex(int major, int minor, int micro) {
> > +    return (major << 16) | (minor << 8) | micro;
>
> Let's define this the same way as CPython's PY_VERSION_HEX -- they leave
> an additional 8 bits for information such as "release level"
> (alpha/beta/rc/final) and "serial" (rc1, rc2), see include/patchlevel.h
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dropbox/pyston/pull/130/files#r16514809>.
>