Framework id not handled in python startup script

[Daryl]

The python startup script is not handling framework id for selective started up based on dev/prod.

This is a particular problem when importing modules, as python is used to build the classpath.
E.G. we have:

module.name = ../../modules/name/v1
%dev.module.name = ../../modules/name/src

So we have a latest dev version of the module, while automatically using a stable version in production.
Play start will always use module.name, ignoring the framework ID, so the wrong jars are imported. But when the main play java starts, it detects the correct module giving a conflict between jar and module source.

We are using play! 1.0.3.2.

thanks

Daryl.

[Erwan Loisant (eloisant)]

That's corrected in 1.1 (won't be fixed in 1.0)