On May 18, 6:31 am, mdipierro mdipie...@cs.depaul.edu wrote:
Please use 1.78.3
For those of us who have it checked out from launchpad, that's rev
1900, no?
Thanks!
-- Pat
On May 19, 7:59 am, ptressel ptres...@myuw.net wrote:
On May 18, 6:31 am, mdipierro mdipie...@cs.depaul.edu wrote:
Please use 1.78.3
For those of us who have it checked out from launchpad, that's rev
1900, no?
Good point: looking at http://code.google.com/p/web2py/source/browse/.hgtags,
yes
On May 19, 7:59 am, ptressel ptres...@myuw.net wrote:
On May 18, 6:31 am, mdipierro mdipie...@cs.depaul.edu wrote:
Please use 1.78.3
For those of us who have it checked out from launchpad, that's rev
1900, no?
Thanks!
-- Pat
Sorry, I am pushing the new tags now.
On May 19, 1:54 pm, Yarko Tymciurak resultsinsoftw...@gmail.com
wrote:
On May 19, 7:59 am, ptressel ptres...@myuw.net wrote:
On May 18, 6:31 am, mdipierro mdipie...@cs.depaul.edu wrote:
Please use 1.78.3
For those of us who have it checked out from
1.78.3 seems to work correctly TNX.
There is one thing left with web2py and squeeze, the simplejson
thing... :-o
On máj. 17, 19:25, mdipierro mdipie...@cs.depaul.edu wrote:
You are right. It is possible it is not documented in the book and it
is not your fault that it is not in the new
Hello,
I'm getting this error when I try to star any of the app:
Ticket issued: admin/127.0.0.1.2010-05-18.10-39-45.4c56ac32-
d0db-4f64-98f0-9e3c1c93518b
Traceback (most recent call last):\n File C:\\web2py\\gluon\
\main.py, line 381, in wsgibase\nserve_controller(request,
response,
Please use 1.78.3
On May 18, 3:43 am, salbefe salb...@gmail.com wrote:
Hello,
I'm getting this error when I try to star any of the app:
Ticket issued: admin/127.0.0.1.2010-05-18.10-39-45.4c56ac32-
d0db-4f64-98f0-9e3c1c93518b
Traceback (most recent call last):\n File C:\\web2py\\gluon\
On May 16, 2010, at 10:49 PM, mdipierro wrote:
I just did it. I think.
Yes, I see it now.
On May 17, 12:36 am, Jonathan Lundell jlund...@pobox.com wrote:
On May 16, 2010, at 9:35 PM, mdipierro wrote:
We found some problems in 1.78.1 and errors in views will not display
correctly in
What is the status of the simplejson problem? Any progress?
On máj. 17, 07:49, mdipierro mdipie...@cs.depaul.edu wrote:
I just did it. I think.
On May 17, 12:36 am, Jonathan Lundell jlund...@pobox.com wrote:
On May 16, 2010, at 9:35 PM, mdipierro wrote:
We found some problems in
info.html:
--- cut -
{{extend 'layout.html'}}
table class=infotext
tr
tdh2{{=title}}
{{if auth.user_id==1:
=A((m),_href=szerkeszt)
pass}}/h2
{{=XML(szoveg)}}
{{if auth.user_id==1:
=A((m),_href=szerkeszt)
pass}}
default/index.html:
--- cut -
{{extend 'layout.html'}}
{{try:}}{{=H2(message)}}{{except:}}{{=BEAUTIFY(response._vars)}}
{{pass}}
h3{{=T('Changes not in use:')}}/h3
{{changes=db(db.web.modified==True).select(db.web.id,db.web.name,db.web.controller)
if
I see this Rocket error. That error is normal in the course of
operations but should never be detected through web2py. Did you get
that traceback from a ticket or somewhere else? How does this error
relate to the messages you sent before? Do they happen at the same time?
-tim
On
I think it's related to the new templating engine :-o
Ticket 127.0.0.1.2010-05-17.09-20-49.56d45b51-05f0-49b5-9b10-
cd7e9a3212a6
== missing pass in view
I think there is some shift in the python code logic because the
template got parsed wrong...
On máj. 17, 14:56, Timothy Farrell
Please email me the template that causes a problem. There are some
possible issues:
1) it is possible that lines starting with = are not parsed properly
2) some errors are not reported properly
3) the new template engine checks for un-matched blocks (missing
pass). These are bugs that were not
Ticket
127.0.0.1.2010-05-17.09-48-36.ca732008-3e5a-4346-8d65-27ee970109ea
missing pass in view
Error traceback
1.
2.None
On May 17, 9:29 am, szimszon szims...@gmail.com wrote:
I think it's related to the new templating engine :-o
Ticket
The ticket missing pass in view is not a mistake. It is checking for
a bug in your views that was not being detected before. Here is an
example:
htmlbody
{{if True:}}
h1Hello world/h1
/body/html
Notice that a {{pass}} is missing. web2py was not checking before
causing potential problems are
You cannot have random = signs in your view.
The syntax is
{{python code here}}
{{=python variable here}}
You MUST declare {{= with no space in between. the bracket and equal sign.
--
Thadeus
On Mon, May 17, 2010 at 2:23 AM, szimszon szims...@gmail.com wrote:
default/index.html:
On May 17, 2010, at 7:53 AM, Thadeus Burgess wrote:
You cannot have random = signs in your view.
The syntax is
{{python code here}}
{{=python variable here}}
You MUST declare {{= with no space in between. the bracket and equal sign.
Alternatively (correct me if I'm wrong), replace,
Not quite. Before the new template engine we could do
{{for i in range(10):
=i
pass}}
if this is broken. It must be fixed.
On May 17, 10:04 am, Jonathan Lundell jlund...@pobox.com wrote:
On May 17, 2010, at 7:53 AM, Thadeus Burgess wrote:
You cannot have random = signs in your view.
There is odd because I have a lot of code with
{{ =some.var}}
and
{{if something:
=T('something')
pass}}
If it doesn't work with the new engine I have to do a lot of work :(
On máj. 17, 16:53, Thadeus Burgess thade...@thadeusb.com wrote:
You cannot have random = signs in
The fact that it does not work with new engine has to be considered a
bug. I should have caught it before. I am now working to fix it. The
new engine will be 100% backard compatible.
I think I have already fixed this problem in trunk (please check it)
but there are still some issues with
Well, we only caught the bugs because a new version of web2py is released :)
Honestly, I don't see documentation for the
{{if True:
=i
pass}}
syntax anywhere, nor have I seen an example of this until now.
--
Thadeus
On Mon, May 17, 2010 at 11:13 AM, mdipierro mdipie...@cs.depaul.edu
You are right. It is possible it is not documented in the book and it
is not your fault that it is not in the new template.py. Yet, this was
discussed some time ago on this list and a lot of people rely on it. I
think I added it to trunk. One problem remains with multiline comments
but I think I
Tonight.
--
Thadeus
On Mon, May 17, 2010 at 12:25 PM, mdipierro mdipie...@cs.depaul.edu wrote:
You are right. It is possible it is not documented in the book and it
is not your fault that it is not in the new template.py. Yet, this was
discussed some time ago on this list and a lot of
I just did it. I think.
On May 17, 12:36 am, Jonathan Lundell jlund...@pobox.com wrote:
On May 16, 2010, at 9:35 PM, mdipierro wrote:
We found some problems in 1.78.1 and errors in views will not display
correctly in tickets thus causing problems. We have a temporary fix in
1.78.2 but it
25 matches
Mail list logo
