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.
updated to include `level` and `serial`


On Thu, Aug 21, 2014 at 1:23 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;
>
> Unfortunately, none at the moment :/ I don't know enough about how those
> are used to know if they're consistent; a quick grep through the Modules
> directory seems to show that they're typically used in #ifdefs to check
> between major version changes. It'd be nice if they were unified, though
> their use in #ifdefs means we'd have to give up on having them being set
> dynamically.
>
> For now let's just leave the patchlevel.h ones at 2.7.7 and do the changes
> here -- we can punt on deciding one way or another until we have a better
> understanding of the choices.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dropbox/pyston/pull/130/files#r16566241>.
>