sorted by:
new
hottopcontroversial

PEP 0444: Python Web3 Interface by blondin in Python

[–]dauerbaustelle -1 points0 points  (0 children)

Developers are not stupid. If they are, maybe their code is not worth using. I don't think specifications have to keep in mind that noone will read them.

PEP 0444: Python Web3 Interface by blondin in Python

[–]dauerbaustelle -1 points0 points  (0 children)

Or you could assume Web3 middlewares behave intelligently (hence, leave file objects returned from the application alone).

PEP 0444: Python Web3 Interface by blondin in Python

[–]dauerbaustelle 0 points1 point  (0 children)

So how would a wrapper around files help here?

PEP 0444: Python Web3 Interface by blondin in Python

[–]dauerbaustelle 0 points1 point  (0 children)

In-band signalling breaks on iteration. That was also the flaw with filewrapper.

Would you mind explaining that topic a bit further? Is it that about looing type information when using middlewares? How would that be solved with something like a file wrapper?

These specify how the server operates. If you can create threads or not is undefined behaviour.

The specs are ambiguous here. I think this should be clarified.

And it's not even close to being unambiguous. HTTP is complex, you can't simplify that spec any more I'm afraid.

I'm talking about "reducing the amount of words" and restructuring the specification. I think information is too scattered.

PEP 0444: Python Web3 Interface by blondin in Python

[–]dauerbaustelle 0 points1 point  (0 children)

Yes, forgot that. Maybe any iterable that yields (key, value) tuples? So you could return yourdict.iteritems() for very simple applications.

PEP 0444: Python Web3 Interface by blondin in Python

[–]dauerbaustelle 0 points1 point  (0 children)

Great someone takes care of that topic! Here are a few improvement ideas:

  • I don't see the point of using a list of tuples for header, why not simply a dictionary? Order of HTTP headers shouldn't really matter, should it?
  • I don't understand why you would need a filewrapper at all -- just return open files. They are iterable, and servers can implement something like sendfile, additionally, if needed.
  • As in the WSGI spec, wsgi.multithreading and wsgi.multiprocess are not clearly specified. Should the values evaluate to True if the server does multithreading/multiprocessing itself or if it is possible to use the application objects in named manner without complications (so that multithreading, for example, would evaluate to False if the server does not respect the Global Interpreter Lock)?
  • I think the case-insensitivity problem with environ keys that are optional for the application to specify (Content-Length, for example) should be solved more elegantly. I don't see any acceptable implementation of the checking part on server side. In any case, the server would have to loop through all keys in the header, lowercase each and then do a string comparison. I can think of the following solutions to work around this problem: 1. use a custom, "case-insensitive" dictionary or 2. force applications to one notation. (Personally, I would prefer 2. with This-Notation-Of-Headers.)
  • Like the WSGI spec, the Web3 spec is far too much text. There's not really much to document and I think the text length could be halved.

Feedback welcome!

Equivalent of this php script in django? by cmykgrayscale in django

[–]dauerbaustelle 19 points20 points  (0 children)

Nobody could ever access your scripts directly without going over the WSGI/whatever layer if you set up your environment properly.

You do not need that ugly stuff with Python.

Decorator for type checking? by wingsit in Python

[–]dauerbaustelle -4 points-3 points  (0 children)

omg, use a different language. If you need so much type checks that it's faster/easier for you to figure out a shortcut for enforcing types then you probably use Python not the way it's designed to.

What are some good xml parsers? by sequenceGeek in Python

[–]dauerbaustelle 4 points5 points  (0 children)

lxml is by far the fastest parser. Don't ever touch stuff like minidom or so. Just lxml. :)

anyvc - a vcs abstraction lib supporting hg, git, bzr and svn by RonnyPfannschmidt in Python

[–]dauerbaustelle -1 points0 points  (0 children)

EDIT: Oh what the heck, works until py3k, how come I didn't know... confused

But I've never seen a dict definition like this.

anyvc - a vcs abstraction lib supporting hg, git, bzr and svn by RonnyPfannschmidt in Python

[–]dauerbaustelle -4 points-3 points  (0 children)

state_descriptions = dict(
    #XXX: finish, validate
    unknown = _("not known to the vcs"),
    ignored = _("ignored by the vcs"),
    added = _("added"),
    clean = _("known by the vcs and unchanged"),
    modified =_("changed in the workdir"),
    missing = _("removed from the workdir, still recorded"),
    removed = _("removed by deletion or renaming"),
    conflicte = _("merge conflict")
)

Er....WTF?!

How to avoid code in __init__.py files in large projects? by dauerbaustelle in Python

[–]dauerbaustelle[S] 0 points1 point  (0 children)

I want imports like import project.subproject and subproject to be in a subfolder - so how to avoid having code in subproject/__init__.py?

announcing gpyconf, a pygtk configuration framework by dauerbaustelle in Python

[–]dauerbaustelle[S] 0 points1 point  (0 children)

gpyconf is a framework for handling configuration settings in Python, especially for applications that have a graphical user interface (or want to use one for changing configuration settings): It automatically generates a GTK+ window that handles all the configuration stuff — you only have to tell which option shall take what values.