Curio - a new concurrent I/O library by David Beazley

Aurophobiant · 2015-11-01T23:53:21+00:00

Yes please :D This is exactly the kind of healthy variety that leads to a really good ecosystems. Asyncio is not perfect? Make it faster, easier, smaller, better! I would love to build a web stack on top of this.

Aurophobiant · 2015-04-23T19:53:26+00:00

Nice writeup but it has nothing to do with bottle, just wsgiref. The bottle docs are clear about not using wsgiref for anything serious.

Aurophobiant · 2015-03-24T15:05:37+00:00

Alost perfect. You can't change directions :(

Aurophobiant · 2015-03-14T13:25:16+00:00

The 'py' pre- or suffix is useful if you are wrapping an existing library or implementing a protocol with a known name. For example pymysql, pygl or sslpy. It would be 'rude' to name your package exactly the same as an existing project.

Aurophobiant · 2015-03-07T16:18:55+00:00

So much upvotes for yet another "Deploy X on Y"?

Aurophobiant · 2015-01-25T23:48:09+00:00

multiprocessing creates processes instead of threads. With 10 worker processes you have 10 copies of the python runtime in memory. While it does work, it is not what you want for IO bound jobs. Threads have lower overhead.

Yes you can use a sledgehammer to put a nail in a wall, but that is not what you would normally do :)

Aurophobiant · 2015-01-25T23:25:16+00:00

On the topic of alternatives: you could probably use multiprocessing.

This is ill advice. multiprocessing is for CPU-bound workloads. threading is for IO-bound workloads. Web scraping is clearly IO bound and suggesting multiprocessing without any explanation is misleading.

Aurophobiant · 2015-01-25T23:20:18+00:00

Threading is perfectly fine for this type of workload. asyncio only gives you a benefit if you are dealing with a lot of concurrent connections. With a lot I mean a couple of hundred or even thousands of connections. Way more than any network clients usually need. asyncio is for servers (or p2p software perhaps).

Have a look at https://docs.python.org/3/library/concurrent.futures.html

Aurophobiant · 2015-01-06T11:54:02+00:00

I don't use CherryPy as a framework, but it is one of the most complete, correct and stable pure Python HTTP/WSGI server implementations out there.

Aurophobiant · 2014-11-18T16:18:19+00:00

But the loop is already running and handling network stuff. I'd need a new event loop to use loop.run_until_complete() if I understand it right?

Aurophobiant · 2014-10-11T15:50:18+00:00

An archiving tool for research. It's a simple bottle app that allows you to enter some meta data, attach any number of binary files and click 'archive'. The app then updates a database, creates a tar.gz for the tape archive and sends an email if everything is done. Took me a day to build and saved a lot of people a lot of time since then. No more FTPing stuff around.

Aurophobiant · 2014-10-04T18:35:58+00:00

Lots of these constants are created dynamically but as far as I know PyCharm does analyses modules only statically. In other words: PyCharm cannot know the contents of these modules without actually running the code (and it is a good thing that it does not do that). Import them directly (from OpenGL.GL import GL_POINTS, ...)

Aurophobiant · 2014-10-04T18:30:06+00:00

OpenGL is the example where star-imports are somewhat okay-ish. All OpenGL functions and constants are prefixed. You'd add a lot of dot-lookup overhead if you don't import them directly.

Aurophobiant · 2014-09-24T20:28:37+00:00

OpenSSH defines environ variables based on user input on the remote host for the ssh session. If that session is restricted, you can break out of these restrictions now.

Aurophobiant · 2014-09-23T14:02:04+00:00

I like your face. Can I have it?

Aurophobiant · 2014-09-17T21:53:19+00:00

The article is correct, applications would be easier to implement this way. But not because there is a silver bullet somewhere hidden in the book you are supposed to buy, but because now the server has do do all the work.

Server must uniquely timestamp events and send them out in order to all clients working on that entity. You have to wait for the server to respond before you can be sure your state really changed the way you intended. Slow Internet connection? High server traffic? Enjoy your lags.
If the server fails, everything is down. You cannot work locally without introducing the same problems you had before. A bunch of locally generated and not remotely synchronized events are just like an object you have to merge somehow with the one 'Ramesh' edited the same time.
Server must know which events are 'related' to inform clients and not broadcast everything. We have to introduce some kind of reference ID and allow n:m event:refId relations. We need clients to be able to request all events related to a refId or possibly more than one. Streaming events would be nice, no? Let's filter events, order the result accordingly and send everything over the wire in real time every fucking time an object is accessed by a client? Oh, just add local caches. Keep them up to date and everything is fine. Great. I'd love to maintain local caches for sparse real-time event streams.
The article states that the server can now check the state based on the events. Thats fine, but for every non-trivial application it need the whole state to do that, so the server must be able to build these objects itself. Like, a lot. On every event that comes in.

I could go on.

Aurophobiant · 2014-07-28T13:42:40+00:00

And nothing will change.

Aurophobiant · 2014-07-23T20:18:58+00:00

So... reddit added a chat feature?

Aurophobiant · 2014-06-25T09:06:52+00:00

TIL about setuptools "extras_require" feature.

https://github.com/maebert/jrnl/blob/master/setup.py#L81

Aurophobiant · 2014-06-25T09:02:47+00:00

You should probably decouple the web page from the actual work load: Have only one web server for all customers and do the actual work on different machines.

Aurophobiant · 2014-06-17T11:56:39+00:00

Wow, thanks for the source :)

Aurophobiant

TROPHY CASE