web.py 0.23 is ready for release

4 views
Skip to first unread message

Anand Chitipothu

unread,
Dec 31, 2007, 11:06:07 PM12/31/07
to we...@googlegroups.com
web.py 0.23 is ready for release.

Changes are:
fix: for web.background gotcha (Bug#133079)
fix: for postgres unicode bug (Bug#177265)
fix: web.profile behavior in python 2.5 (Bug#133080)
fix: only uppercase HTTP methods are allowed. (bug@#176415)
fix: transaction error in with statement (Bug#125118)
fix: unicode support in db.sqllist. (Bug#137042)
fix: fix in web.reparam (Bug#162085)
new: support for https
new: support for secure cookies
new: sendmail and emailerrors
new: htmlunquote

Please test this out with your software and let me know if there are any issues.
code is available at bazaar branch http://webpy.org/bzr/webpy-0.23.

Tzury Bar Yochay

unread,
Jan 1, 2008, 2:59:58 AM1/1/08
to web.py
Good News to start a new year with.
Happy New Year All Pythonistas ;-)

karim

unread,
Jan 1, 2008, 7:56:46 AM1/1/08
to web.py
Thank you all folks! And happy new year!
Let this year be THE web.py year!

Karim
--
http://xhtml-css.com
Be Valid or die learning

gregp...@gmail.com

unread,
Jan 1, 2008, 7:07:41 PM1/1/08
to web.py
Excellent work. A couple questions if you don't mind.

On Dec 31 2007, 11:06 pm, "Anand Chitipothu" <anandol...@gmail.com>
wrote:
> web.py 0.23 is ready for release.
>
> Changes are:
> fix: for web.background gotcha (Bug#133079)
> fix: for postgres unicode bug (Bug#177265)
> fix: web.profile behavior in python 2.5 (Bug#133080)
> fix: only uppercase HTTP methods are allowed. (bug@#176415)
> fix: transaction error in with statement (Bug#125118)
> fix: unicode support in db.sqllist. (Bug#137042)
> fix: fix in web.reparam (Bug#162085)
> new: support for https

What do you mean?

> new: support for secure cookies

What's this?

And finally, what was the reasoning from switching to return from
print for making output? I never heard an answer on that?

Thanks,

Greg

Anand Chitipothu

unread,
Jan 1, 2008, 9:33:06 PM1/1/08
to we...@googlegroups.com
> > new: support for https
>
> What do you mean?

https://bugs.launchpad.net/webpy/+bug/125295

> > new: support for secure cookies
>
> What's this?

https://bugs.launchpad.net/webpy/+bug/153361

> And finally, what was the reasoning from switching to return from
> print for making output? I never heard an answer on that?

switching to return from print is going to happen in 0.3, not in this release.
With returns code becomes very modular and extendable.

For example, if you want to pass output of all your GET and POST
methods through a layout template, it is not very straight forward to
do that with prints. But when you have returns, it is straight
forward. Here is an example that uses a decorator.

def layoutify(f):
def g(*a, **kw):
return render.layout(f(*a, **kw))
return g

class Hello:
@layoutify
def GET(self):
return "foo"

Still better, in 0.3 you can write a application processor to handle
all methods.

app = web.application(urls', globals())

def layout_processor(handler):
result = handler()
return render.layout(result)

If you have lot of code that uses prints, you don't have to worry. You
can write an application processor to handle that too.

def capture_stdout(handler):
return web.capturestdout(handler)()

app = web.application(urls, globals())
app.add_processor(capture_stdout)

I am working on module to make web.py 0.2x applications work
seemlessly with 0.3.

gregp...@gmail.com

unread,
Jan 2, 2008, 11:54:32 AM1/2/08
to web.py
Excellent, thanks for the answer. getting away from print may help
with multithreaded applications too, no? I thought I heard that
somewhere.

-Greg

Green

unread,
Jan 5, 2008, 3:10:22 AM1/5/08
to web.py
How to do this for cheetah?

def layoutify(f):
def g(*a, **kw):
return render.layout(f(*a, **kw))
return g

class Hello:
@layoutify
def GET(self):
return "foo"

Still better, in 0.3 you can write a application processor to handle
all methods.

app = web.application(urls', globals())

def layout_processor(handler):
result = handler()
return render.layout(result)

lukaszt

unread,
Jan 5, 2008, 8:02:19 AM1/5/08
to web.py
Hi, i have some problems with web.sendmail function. It's always
failing when i try to specify From field with unicode data, for
example:
"Łukasz Topa <so...@mail.goes.here.com>".

I've changed 880 line in utils.py
from:
i.write(message)
to:
i.write(message.encode('utf-8'))

in 0.23 release and it seem's to work properly.
Is there any other way to make unicode working without hacking
utils.py?
maybe i missed something...

Regards

On 1 Sty, 05:06, "Anand Chitipothu" <anandol...@gmail.com> wrote:
> web.py 0.23 is ready for release.
>
> Changes are:
> fix: for web.background gotcha (Bug#133079)
> fix: for postgres unicode bug (Bug#177265)
> fix: web.profile behavior in python 2.5 (Bug#133080)
> fix: only uppercase HTTP methods are allowed. (bug@#176415)
> fix: transaction error in with statement (Bug#125118)
> fix: unicode support in db.sqllist. (Bug#137042)
> fix: fix in web.reparam (Bug#162085)
> new: support for https
> new: support for secure cookies
> new:sendmailand emailerrors

Anand Chitipothu

unread,
Jan 5, 2008, 8:40:13 AM1/5/08
to we...@googlegroups.com
On Jan 5, 2008 6:32 PM, lukaszt <lukas...@gmail.com> wrote:
>
> Hi, i have some problems with web.sendmail function. It's always
> failing when i try to specify From field with unicode data.

Bug filed.
https://bugs.launchpad.net/webpy/+bug/180549

Anand Chitipothu

unread,
Jan 5, 2008, 8:54:31 AM1/5/08
to we...@googlegroups.com

Fix committed.

Reply all
Reply to author
Forward
0 new messages