cmake configuring seems to depend the activation of python2 module on BUILD_opencv_world=OFF.

Is this an intended behaviour?
If yes, it idealy should be documented in a decent location (maybe even cmake-description for BUILD_opencv_world).
This kept me crazy for some hours...

Effect of BUILD_opencv_world on python2 module (only most important bits):

* case A
<pre>
cmake -D BUILD_opencv_world=ON [...]
</pre>
<pre>
-- OpenCV modules:
-- Unavailable: [...] python2
-- Python 2:
-- Interpreter: /usr/bin/python2.7 (ver 2.7.6)
-- Libraries: NO
-- numpy: /usr/lib/python2.7/dist-packages/numpy/core/include (ver 1.8.2)
-- packages path: /usr/local/lib/python2.7/dist-packages
</pre>

* case B
<pre>
cmake -D BUILD_opencv_world=OFF [...]
</pre>
<pre>
-- OpenCV modules:
-- To be built: [...] python2
-- Python 2:
-- Interpreter: /usr/bin/python2.7 (ver 2.7.6)
-- Libraries: optimized /usr/lib/x86_64-linux-gnu/libpython2.7.so debug /usr/lib/x86_64-linux-gnu/libpython2.7_d.so (ver 2.7.6)
-- numpy: /usr/lib/python2.7/dist-packages/numpy/core/include (ver 1.8.2)
-- packages path: /usr/local/lib/python2.7/dist-packages
</pre>

Full cmake option list, generated output and CMakeCache.txt/version_string.tmp are attached.

OpenCV 3.0 from git/master (28833421aec6b85c47228a2955b148390031e964).
System: up-to-date Ubuntu 14.04.1 (3.13.0-43-generic x86_64).