jessenoller.com

There is a Poll run­ning on the front of the PyPI page — you have to log in to see it/vote. This poll is ask­ing a ques­tion about the new feature(s) of allow­ing users to comment/5-star-rate a given pack­age in the index.

Some of the Pros/Cons have already been added to the python wiki here, as well as this bug report here. The catalog-sig has some of the dis­cus­sion as well.

This poll was cre­ated in part by this Python-Dev thread. I obvi­ously make my opin­ion known.

Given my vehe­mence in the python-dev thread; I’d like to point out I am not against giv­ing pack­age con­sumers a voice — how­ever, I do not think that as-implemented, these fea­tures serve anyone.

As devel­op­ers of, mod­er­a­tors and com­mu­nity mem­bers on any num­ber of social news and vot­ing sites will point out to you — get­ting the sys­tem right takes a lot of time, and plan­ning. Why not bor­row pages from their play books?

You also can’t give the users a voice at the cost of the pack­age main­tain­ers — a bal­ance has to be made. You have to pro­tect and mod­er­ate out astro­turfers, spam­mers, coor­di­nated attacks against a given pack­age, etc. It’s hard to get right, but easy to get wrong.

With regards to the rat­ing sys­tem, Zed Shaw recently had an inter­est­ing piece on the bimodal­ity of 1–5 rat­ing sys­tems. Com­ments on that here and here.

In any case; Mar­tin put the poll up as he wants to get people’s opin­ions via the votes on this issue. Please take a moment to do so.

If you have sug­ges­tions on the actual imple­men­ta­tion of a full-blown sys­tem for deal­ing with this, please drop an email to the catalog-sig mail­ing list.

There is a Poll running on the front of the PyPI page - you have to log in to see it/vote. This poll is asking a question about the new feature(s) of allowing users to comment/5-star-rate a given package in the index. Some of the Pros/Cons have already been added to the python wiki here, ...

PEP 3003: “Python Lan­guage Mora­to­rium” has been accepted. After sev­eral weeks of dis­cus­sion, Guido switched the bit this morning.

This PEP effec­tively freezes the syn­tax and fol­low­ing items:

• New built-ins
• Gen­eral lan­guage semantics
• New __future__ imports

This does not apply to the stan­dard library; adding meth­ods to builtins, or bug fixes to exist­ing things.

I know there’s opin­ions on both sides, but I see this as a Good Thing™ — this hope­fully frees up core-dev to work on the stan­dard library, tests, the inter­preter, docs, etc — basi­cally every­thing “else” that makes Python, well — Python.

This qui­es­cence will also allow other impl­men­ta­tions to catch up to the cur­rent syn­tax, builtins, etc. This is a good thing for every­one as Python the lan­guage is no longer “Python the C inter­preter” — it’s Python the Lan­guage as inter­preted by unladen-swallow|jython|pypy|ironpython.

There’s also the point that in the last 5 or 6 years, Python as a lan­guage has added a pile of new syn­tax and fea­tures that still haven’t seen wide spread use. For exam­ple, con­text man­agers. Oper­at­ing Sys­tem ven­dors lag behind us in terms of releases. We need to see these things used in the wild to see if the var­i­ous exper­i­ments work.

Yes; this slows the devel­op­ment of the lan­guage down, but given most of the known world is still on 2.4/2.5 — does it really fun­da­men­tally effect any­one other than out­liers (early adopters) and core-developers?

We’ll see how the exper­i­ment goes.

PEP 3003: "Python Language Moratorium" has been accepted. After several weeks of discussion, Guido switched the bit this morning. This PEP effectively freezes the syntax and following items: New built-ins General language semantics New __future__ imports This does not apply to the standard library; adding methods to builtins, or bug fixes to existing things. I know there's opinions on both ...

The offi­cial talk list for PyCon 2010, hap­pen­ing in Feb­ru­ary in Atlanta Geor­gia is now live:

http://us.pycon.org/2010/conference/talks/

My thanks go out to every author, and per­son involved in get­ting us this far. With out the hard work of a lot of peo­ple, this would not have been possible.

The official talk list for PyCon 2010, happening in February in Atlanta Georgia is now live: http://us.pycon.org/2010/conference/talks/ My thanks go out to every author, and person involved in getting us this far. With out the hard work of a lot of people, this would not have been possible.