#1529 confirmed
Okan Alper

1.2.4+: Python scripts are failing for includes with framework id

Reported by Okan Alper | May 18th, 2012 @ 08:01 PM | in 1.4.x


Entries like:

are supposed to be supported in Play (in fact, Play.java parses them), but if you have this in your configuration file, application.py python script fails miserably.

To reproduce, just add the line above to your configuration and run something like "play eclipsify" and you get some errors.

I looked at the code, and it looks like if you modify "framework/pym/play/application.py". Basically,


       if key.startswith('@include.'):


       if key.startswith('@include.'):
            if value.find('${play.id}'):
                value = value.replace('${play.id}',self.id);
            if os.path.exists(os.path.join(confFolder, value)):

And it works fine. I don't know python at all, so this might not be the ultimate solution, but this worked for me.

PS: This fails for 1.2.4 and 1.2.5rc3

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.