On Thu, Apr 21, 2011 at 8:26 PM, wrote:
> On 04:28 pm, albert.bra...@weiermayer.com wrote:
>>On Thu, Apr 21, 2011 at 08:17:04AM -0400, Itamar Turner-Trauring wrote:
>>>The .tac file (or application.py) should typically be two lines of
>>>code,
>>>just importing everything from elsewhere, so reall
On 04:28 pm, albert.bra...@weiermayer.com wrote:
>On Thu, Apr 21, 2011 at 08:17:04AM -0400, Itamar Turner-Trauring wrote:
>>The .tac file (or application.py) should typically be two lines of
>>code,
>>just importing everything from elsewhere, so really just having it in
>>Python seems the easiest
On Apr 21, 2011, at 3:27 AM, Albert Brandl wrote:
> Is this a known problem? Can you suggest a workaround?
Deploy your application as a plugin rather than a tac file. The plugin system
will properly scan for compiled python files and load them as regular modules.
This has other advantages as
On Thu, Apr 21, 2011 at 08:17:04AM -0400, Itamar Turner-Trauring wrote:
> The .tac file (or application.py) should typically be two lines of code,
> just importing everything from elsewhere, so really just having it in
> Python seems the easiest solution.
This is a good argument. I was afraid that
On Thu, 2011-04-21 at 09:27 +0200, Albert Brandl wrote:
> Of course, it's possible to move most of the logic to other (compiled)
> files, but I'd prefer if the application itself could also be deployed
> in compiled form.
The .tac file (or application.py) should typically be two lines of code,
jus
