Re: [boost] Deprecation Policy

Subject: Re: [boost] Deprecation Policy
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2015-05-20 15:37:11

On 20/05/15 03:21 PM, Vladimir Prus wrote:
> On 19.05.2015 01:29, Stefan Seefeld wrote:
>
>> So, as I'm trying to get back into
>> Boost.Python, I'm considering decoupling that from the rest of Boost. I
>> think this is an obvious first candidate, notably because it's a
>> substantial library (not header-only) that few other Boost components
>> depend on.
>>
>> Any thoughts on that ?
>
> That's certainly sufficiently local in scope that it could be done.
>
> The only concern is that I'm not sure there are many users who need very
> current Boost.Python, and older Boost. Do you feel there is a demand?
> Or it's merely that you'll find it more convenient for yourself?

I very strongly believe that modularizing Boost will be beneficial for
everyone. I'm offering to do the first (experimental) steps with
Boost.Python in the hopes that this demonstrates the usefulness to other
library authors and maintainers who will then follow the same path.

    Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...