I will give a try again with webware 1.1
It works, but not for a long time...
python3 doesn't look like a priority for me. (I admit I had some hard
time with unicode...)
Backward compatibility for webkit is the most important IMHO.
About naming convention, I don't care that much.
I'm not using
Am 17.09.2012 11:27, schrieb Sophana K:
I'm using webware 1.0, because webware 1.1 didn't work correctly for
me (I don't remember why)
You should definitely try 1.1 again. It works great for me and if there
are any real issues, please report and I'll be glad to fix them.
I'm currently trying
Hi,
It would be nice to have the option to upgrade to a python3.x Version of
Webware for later purpose.
Backward Compatiblity would be nice until python2.5 (python2.6 is buggy)
We currently don't use WSGI capability, we use WebKit at all.
Compatiblity should be given so, that API remains the
On 20/09/2012 1:01 AM, Christoph Zwerschke wrote:
So my question to this mailing list would be: How many people are still
interested in having a modernized Webware version...?
I maintain a Webware app that does a lot of work, but changes rarely,
and I'm not doing any new Python web development
Hi
I'm using webware for my website since 2007.
I'm using webware 1.0, because webware 1.1 didn't work correctly for
me (I don't remember why)
I'm currently trying to debug a freeze problem that occur every 1 to 3 weeks.
The python appServer process is completely frozen, and must be killed with
