Subject: Re: [boost] RFC: Separating Boost.Python from Boost
From: Sergey Cheban (sergey.cheban_at_[hidden])
Date: 2015-05-31 17:25:16
30.05.2015 4:19, Stefan Seefeld Ð¿Ð¸ÑÐµÑ:
>> In what sense then, will Boost.Python, decoupled from Boost, remain
>> Boost.Python and not SmthElse.Python?
> That does entirely depend on what we mean by "Boost".
For me, the Boost is a set of libraries that:
1. Have the same Boost license.
2. Are accepted by the Boost community.
3. Use the same naming convention (currently, it is the boost::
namespace and the boost/ prefix for include files).
4. Are tested and work well together (i mean well-known versions of the
5. Can be built and installed using the same [bjam] engine.
6. Are distributed from boost.org.
A good example of such a library is boost::spirit. Note that:
1. It is developed separately (has its own newsgroups and site).
2. It has its own version numbering. Actually, boost contains two
versions of this library, 1.8.x and 2.5.x, side by side.
-- Best regards, Sergey Cheban
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk