web.py 0.3 is ready for release

[Anand Chitipothu]

web.py 0.3 is ready for release.

Changes are:
new: replace print with return (backward-incompatible)
new: application framework (backward-incompatible)
new: modular database system (backward-incompatible)
new: templetor reimplementation
new: better unicode support
new: debug mode (web.config.debug)
new: better db pooling
new: sessions
new: support for GAE
new: etag support
new: web.openid module
new: web.nthstr
fix: various form.py fixes
fix: python 2.6 compatibility
fix: file uploads are not loaded into memory
fix: SQLLiteral issue (Bug#180027)

As most of you already know, there are some backward incompatible changes.
I have written "how to upgrade" document here:
http://webpy.org/docs/0.3/upgrade.

Complete documentation is available at:
http://webpy.org/docs/0.3

Please test this out with your software and let me know if there are any issues.
code is available at http://github.com/webpy/webpy.

[Daniel Yang]

Congratulations!

and thanks for this wonderful framework.

--
-----------------------------------------------
Yours
Faithfully

Daniel Yang

[Jeffrey]

thanks Anand

very glad to heard this, webpy is the best framework i have ever seen
i'd thought you do not intend to release 0.3

Yours
Faithfully

Jeffrey Hsu

[jbw]

On Nov 20, 2:10 am, "Anand Chitipothu" <anandol...@gmail.com> wrote:
> web.py 0.3 is ready for release.
>
> Changes are:
>     new: replace print with return (backward-incompatible)

Hmm.... one of the things I liked about web.py was that it worked
just like cgi, print to stdout.

>     new: application framework (backward-incompatible)

thought the idea of not having this was to keep it very light weight?

>     new: modular database system (backward-incompatible)
>     new: templetor reimplementation
>     new: better unicode support
>     new: debug mode (web.config.debug)
>     new: better db pooling
>     new: sessions

All sounds good.

>     new: support for GAE

What was done to support GAE? What does this mean? It already seemed
to work on it.

>     new: etag support
>     new: web.openid module
>     new: web.nthstr
>     fix: various form.py fixes
>     fix: python 2.6 compatibility

>     fix: file uploads are not loaded into memory

Hmm.. this seems like it could be incompatible with the GAE? Also was
a way to limit file upload sizes put in?

>     fix: SQLLiteral issue (Bug#180027)

> Complete documentation is available at:http://webpy.org/docs/0.3
>
> Please test this out with your software and let me know if there are any issues.
> code is available athttp://github.com/webpy/webpy.

For the git illiterate since no tarball exists it seems, can someone
tell me the command line to fetch this?

[Aaron Swartz]

>> new: application framework (backward-incompatible)
>
> thought the idea of not having this was to keep it very light weight?

It's lightweight; we just reorganized things a bit. You only need to
change one line of your code.

>> code is available athttp://github.com/webpy/webpy.
>
> For the git illiterate since no tarball exists it seems, can someone
> tell me the command line to fetch this?

git clone git://github.com/webpy/webpy.git

[leone]

Good work!
See 'How to use web.background' in cookbook in Web.py
Cookbook.Advanced.
It runs only using web023.
Congratulation!

[jbw]

On Nov 23, 8:54 pm, jbw <jbwat...@gmail.com> wrote:
> On Nov 20, 2:10 am, "Anand Chitipothu" <anandol...@gmail.com> wrote:
>
> > web.py 0.3 is ready for release.
>
> > Changes are:
> > new: replace print with return (backward-incompatible)
>
> Hmm.... one of the things I liked about web.py was that it worked
> just like cgi, print to stdout.

I have done a little bit of playing with it, and was wondering if
there was some way to
have a setting to allow printing to stdout to work at least for some
time to let this be migrated to overtime?

> > new: support for GAE
>
> What was done to support GAE? What does this mean? It already seemed
> to work on it.

No answers for this?

> > new: web.openid module

Any code examples for using this?

> > fix: file uploads are not loaded into memory
>
> Hmm.. this seems like it could be incompatible with the GAE? Also was
> a way to limit file upload sizes put in?

Does this work by spooling to a temp. file?

>
> > fix: SQLLiteral issue (Bug#180027)
> > Complete documentation is available at:http://webpy.org/docs/0.3

web.webopenid

form(openid_loc): None

class host: None

logout(): None

status(): None


is complete documentation for webopenid?

[Tzury Bar Yochay]

Anand,
Your intensive work is highly appreciated!

[Anand Chitipothu]

> I have done a little bit of playing with it, and was wondering if
> there was some way to
> have a setting to allow printing to stdout to work at least for some
> time to let this be migrated to overtime?

I have written a script which magically makes web.py 0.23 applications
run on web.py 0.3. Let me see if I can find it.

>> > new: support for GAE
>>
>> What was done to support GAE? What does this mean? It already seemed
>> to work on it.

templates don't work on GAE due to security restrictions.

Here is the cookbook howto:
http://webpy.org/cookbook/templates_on_gae

>> > new: web.openid module
>
> Any code examples for using this?

Aaron?

>> > fix: file uploads are not loaded into memory
>>
>> Hmm.. this seems like it could be incompatible with the GAE? Also was
>> a way to limit file upload sizes put in?

http://webpy.org/cookbook/limiting_upload_size

> Does this work by spooling to a temp. file?

Yes.

[jbw]

On Nov 24, 10:01 pm, "Anand Chitipothu" <anandol...@gmail.com> wrote:
> I have written a script which magically makes web.py 0.23 applications
> run on web.py 0.3. Let me see if I can find it.

nice

> >> > new: support for GAE
>
> >> What was done to support GAE? What does this mean? It already seemed
> >> to work on it.
>
> templates don't work on GAE due to security restrictions.
>
> Here is the cookbook howto:http://webpy.org/cookbook/templates_on_gae

Was that new that it did not work as part of the .3 changes? I had
been using
templates just fine with 0.23... at least I was getting results, but
then I was running
it on the test server then uploading, which was probably uploading
the .pyc files.

>
> >> > fix: file uploads are not loaded into memory
>
> >> Hmm.. this seems like it could be incompatible with the GAE? Also was
> >> a way to limit file upload sizes put in?
>
> http://webpy.org/cookbook/limiting_upload_size

Thanks.... mostly have used perl before this for cgi's so not too
familar with the python cgi lib.

> > Does this work by spooling to a temp. file?
>
> Yes.

Doesn't this fail on the GAE ? Since you can't write to files?

[Anand Chitipothu]

> Was that new that it did not work as part of the .3 changes? I had
> been using
> templates just fine with 0.23... at least I was getting results, but
> then I was running
> it on the test server then uploading, which was probably uploading
> the .pyc files.

The problem is with the new implementation of templetor.

>> > Does this work by spooling to a temp. file?
>>
>> Yes.
>
> Doesn't this fail on the GAE ? Since you can't write to files?

Storing in temporary files is taken care by the cgi module.
I hope that GAE might have taken care of it. I haven't tried it myself though.