Re: [Web-SIG] A Python Web Application Package and Format

non-web) networked applications is a design goal. Good :) cheers James -- -- James Mills -- -- "Problems are solved by method" ___ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.py

Re: [Web-SIG] A Python Web Application Package and Format

+1 too. I would however like to see this idea developed in a generic and useable way. ie: No zope/twisted deps or making it fit around Django :) Ideally it should be useable by the most basic (plain old WSGI). cheers James -- -- James Mills -- -- "Problems are solved by m

[Web-SIG] Python WebSockets Server with circuits

Hi all, Just wanted to share my implementation of a Python WebSockets Server (using the circuits framework): http://prologic.shortcircuit.net.au/Blog/2011-02-27-09.50 Enjoy! cheers James -- -- James Mills -- -- "Problems are solved by m

Re: [Web-SIG] Extracting web data

there any Python module or any assistance please? > > Once again, thank you very much for the time you have given. > You might want to look into using either the lxml or BeautifulSoup modules. cheers James -- -- James Mills -- -- "Problems are solved by method" __

Re: [Web-SIG] PEP 444 (aka Web3)

ver). I would prefer it remain the same. If you're going to use Python3, you know you're using Python3 (you don't need "web3" key names to know that). (subjective) cheers James -- -- James Mills -- -- "Problems are solved by method"

Re: [Web-SIG] PEP 444 (aka Web3)

"async aware" (if that's a good way of looking at it) has any benefit IHMO. cheers James -- -- James Mills -- -- "Problems are solved by method" ___ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-si

Re: [Web-SIG] PEP 444 (aka Web3)

not really sure what to think of the whole web3.async "thing" yet... My feeling(s) are that other web frameworks are just doing to do their own thing anyway... cheers james -- -- James Mills -- -- "Problems are solved by method" ___

Re: [Web-SIG] [Python-Dev] Add PEP 444, Python Web3 Interface.

hat is the SERVER_PORT be specified as bytes representing the numerical port (tcp) then I support this. In the case of unix sockets it could be a null byte string, eg: b"" cheers james -- -- James Mills -- -- "Problems are solved by method" _

Re: [Web-SIG] [Python-Dev] Add PEP 444, Python Web3 Interface.

nse. In my experience setting this to 0 or None is probably okay (when it used to be an int). Can't comment on byte ordering, or format, etc... Perhaps SERVER_PORT should be left as it was in the original PEP 333 specs as an int (or None?) cheers James

Re: [Web-SIG] PEP 444 (aka Web3)

t that. I don't see the point of introducing an "async" property/variable into the environment data. cheers James -- -- James Mills -- -- "Problems are solved by method" ___ Web-SIG mailing list Web-SIG@python.org Web SIG: ht

Re: [Web-SIG] PEP 444 (aka Web3)

On Thu, Sep 16, 2010 at 9:40 AM, Massimo Di Pierro wrote: > I fully support it! I don't entirely. I don't quite agree with the key changes from wsgi to web3. I think it's unnecessary. cheers james -- -- James Mills -- -- "Proble

[Web-SIG] wsgiref for web apps

Hi, Just curious, but does anyone actually use wsgiref (in the python stdlib) for real web applications ? Or, do most use some other third-party web framework ? Perhaps wsgiref is used for simple / quick things ? cheers James -- -- James Mills -- -- "Problems are solved by m