error: Invalid property '2.5': unknown feature 'python'.

On RC_1_34_0 branch it was possible to select the python
version like so:

bjam -d+2
gcc-3.4.5/toolset-gcc:flavor=mingw/target-os=windows/python=
2.5

Using this on trunk gives:

X:/projects/boost/trunk/tools/build/v2/buildproperty.jam:28
2: in validate1 from 
module property
error: Invalid property '<python>2.5': unknown feature
'python'.
X:/projects/boost/trunk/tools/build/v2/buildproperty.jam:29
0: in 
property.validate from module property
X:/projects/boost/trunk/tools/build/v2/buildbuild-request.j
am:185: in 
convert-command-line-element from module build-request
X:/projects/boost/trunk/tools/build/v2/buildbuild-request.j
am:143: in 
build-request.from-command-line from module build-request
X:/projects/boost/trunk/tools/build/v2build-system.jam:267:
in load from module 
build-system
X:projectsboosttrunktoolsbuildv2/kernelmodules.jam:26
1: in import from 
module modules
X:projectsboosttrunktoolsbuildv2/kernel/bootstrap.jam:
132: in boost-build 
from module
X:projectsboosttrunkboost-build.jam:9: in module scope
from module

How should I specify the python version to use instead?

Roland aka speedsnail
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

on Fri Aug 17 2007, Roland Schwarz
<roland.schwarz-AT-chello.at> wrote:

> On RC_1_34_0 branch it was possible to select the
python version like so:
>
> bjam -d+2
gcc-3.4.5/toolset-gcc:flavor=mingw/target-os=windows/python=
2.5
>
> Using this on trunk gives:
>
>
X:/projects/boost/trunk/tools/build/v2/buildproperty.jam:28
2: in validate1 from 
> module property
> error: Invalid property '<python>2.5': unknown
feature 'python'.
>
X:/projects/boost/trunk/tools/build/v2/buildproperty.jam:29
0: in 
> property.validate from module property
>
X:/projects/boost/trunk/tools/build/v2/buildbuild-request.j
am:185: in 
> convert-command-line-element from module build-request
>
X:/projects/boost/trunk/tools/build/v2/buildbuild-request.j
am:143: in 
> build-request.from-command-line from module
build-request
>
X:/projects/boost/trunk/tools/build/v2build-system.jam:267:
in load from module 
> build-system
>
X:projectsboosttrunktoolsbuildv2/kernelmodules.jam:26
1: in import from 
> module modules
>
X:projectsboosttrunktoolsbuildv2/kernel/bootstrap.jam:
132: in boost-build 
> from module
> X:projectsboosttrunkboost-build.jam:9: in module
scope from module
>
> How should I specify the python version to use
instead?

I wouldn't count on everything in the trunk having been
maintained.
You might try copying python.jam from RC_1_34_0

-- 
Dave Abrahams
Boost Consulting
http://www.boost-cons
ulting.com

The Astoria Seminar ==> http://www.astoriasemin
ar.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

David Abrahams wrote:

> I wouldn't count on everything in the trunk having been
maintained.
> You might try copying python.jam from RC_1_34_0

Tried, but no success :-(

Now it chokes on some differences in os.jam.

Comparing trunk with RC_1_34_0 reveals a _lot_ of
differences in the 
build system anyways.

Since this currently prevents me to run regressions on the
trunk, I am 
wondering whether it does make sense to run regressions on
trunk?

Shouldn't the build system be fixed first?

Please forgive me not having read the long thread about
development 
policy on main list, isn't trunk still the bleeding edge of
boost?

Is there a place where the development plan is published, or
will I need 
to dig the list to find out?

Thank you for help.

Roland aka speedsnail
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Roland Schwarz wrote:

> 
> 
> David Abrahams wrote:
> 
>> I wouldn't count on everything in the trunk having
been maintained.
>> You might try copying python.jam from RC_1_34_0
> 
> Tried, but no success :-(
> 
> Now it chokes on some differences in os.jam.
> 
> Comparing trunk with RC_1_34_0 reveals a _lot_ of
differences in the
> build system anyways.

This is because lots of folks were committing directly to
branch,
without caring to follow documented checking policies.

Rene and I are planning to reconcile the differences, but
had no time.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

on Sat Aug 18 2007, Vladimir Prus <ghost-AT-cs.msu.su>
wrote:

> Roland Schwarz wrote:
>
>> 
>> 
>> David Abrahams wrote:
>> 
>>> I wouldn't count on everything in the trunk
having been maintained.
>>> You might try copying python.jam from
RC_1_34_0
>> 
>> Tried, but no success :-(
>> 
>> Now it chokes on some differences in os.jam.
>> 
>> Comparing trunk with RC_1_34_0 reveals a _lot_ of
differences in the
>> build system anyways.
>
> This is because lots of folks were committing directly
to branch,
> without caring to follow documented checking policies.

When it was determined that for 1.35 we would treat the
contents
of the 1.34.1 release as the stable trunk, it may have
seemed somewhat
less important to maintain trunk.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-cons
ulting.com

The Astoria Seminar ==> http://www.astoriasemin
ar.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

David Abrahams wrote:

> 
> on Sat Aug 18 2007, Vladimir Prus
<ghost-AT-cs.msu.su> wrote:
> 
>> Roland Schwarz wrote:
>>
>>> 
>>> 
>>> David Abrahams wrote:
>>> 
>>>> I wouldn't count on everything in the trunk
having been maintained.
>>>> You might try copying python.jam from
RC_1_34_0
>>> 
>>> Tried, but no success :-(
>>> 
>>> Now it chokes on some differences in os.jam.
>>> 
>>> Comparing trunk with RC_1_34_0 reveals a _lot_
of differences in the
>>> build system anyways.
>>
>> This is because lots of folks were committing
directly to branch,
>> without caring to follow documented checking
policies.
> 
> When it was determined that for 1.35 we would treat the
contents
> of the 1.34.1 release as the stable trunk, 

Can you point to me an email that clearly says it was
determined so.
Discussions of best version control usage continued to long
since
1.34.1 was released. 

> it may have seemed somewhat 
> less important to maintain trunk.

Given that both RC and trunk already had lots of changes,
that was
clearly a wrong decision. I hope this will be a lesson that
discipline
in version control usage is important.

- Volodya





_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build