Added python_version() function + struct

solves issue #6 
No, I don't mind having the header and the struct. What I'm against is
having the struct be a) mutable and b) non-default-constructible. Adding
those things brings with it baggage that we don't need. The version struct
itself - and really, the fact that we construct it for users - is the real
utility of you're work, and I'd like to keep that.


On Thu, Aug 7, 2014 at 2:47 PM, MathMagique <notifications@github.com>
wrote:

> In src/boost_python_exception/python_version.hpp:
>
> > @@ -0,0 +1,79 @@
> > +#ifndef INCLUDE_BOOST_PYTHON_EXCEPTION_PYTHON_VERSION_H
> > +#define INCLUDE_BOOST_PYTHON_EXCEPTION_PYTHON_VERSION_H
> > +
> > +#include <iosfwd>
> > +
> > +namespace boost_python_exception {
> > +
> > +	/**
> > +	 * @brief A python version number
> > +	 */
> > +	struct version{
>
> I am not sure I understand what you try to say. Do you propose to drop the
> entire header, because telling our users what python version was used at
> compile time is not necessary? I can live with that, since it is not really
> the scope of boost_python_exception, though I sure would love something
> like this in boost::python.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/abingham/boost_python_exception/pull/9/files#r15932889>
> .
>