Re: [boost] RFC: Separating Boost.Python from Boost

On 29/05/15 07:52 PM, Oleg Grunin wrote:

On 5/29/15 2:32 PM, Stefan Seefeld wrote:

...

On 29/05/15 02:26 PM, Nevin Liber wrote:

...

On 29 May 2015 at 13:12, Stefan Seefeld wrote:

...

Again, no code changes are involved. Right now Boost.Python is built as part of a Boost build, and likewise is released as part of a Boost release. All I'm suggesting is to build and release Boost.Python stand-alone, against an external Boost installation.

Does that mean Boost.Python would no longer be part of a Boost release?

That would be the goal, yes. (Boost.Python doesn't have any dependencies on recent Boost additions, so I expect it to be very stable with respect to ongoing development in the rest of the Boost code.)

Stefan

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". The way I would like to see things evolve, Boost would become an umbrella organization hosting certain projects (compare this to the Apache foundation at http://www.apache.org/, for example). Boost would not be a package that gets released once or twice per year. So, in that sense, I expect that Boost.Python would be a "Boost member project" which is released independently from other projects also hosted by the Boost organization. Does that make sense ? Stefan -- ...ich hab' noch einen Koffer in Berlin...