Ci segnalano il rilascio della prima versione alpha di PyHP. Dietro questo nome un po’ criptico si cela un modulo per Apache che permette di utilizzare Python come preprocessore delle pagine HTML, in maniera analoga a quanto avviene con PHP.

Poco convinti sulla bontà di Python (in ambito web)? Sulla pagina del progetto sono ben in evidenza i suoi punti di forza e, soprattutto, i vantaggi rispetto PHP.

Il mondo è bello perché vario, tanto di più se si tratta di quello del software libero / aperto.

[via: ossblog.it]

When you start the program, you are presented with such UI:

Left side is occupied by a word you have to type in kana and its translation + two buttons I will describe later.

Right side is occupied by buttons with kana characters on them and acts just as on-screen keyboard, you tap on buttons - you type text. Only keys required to enter correct answer are shown. Thus said, there may be two buttons, there may be ten buttons.

If there is too much buttons, they are split to more than one columns.
BIG FAT NOTE: the screenshot above is obsolete as there is no "reset" button + there are non-unique keys on on-screen keyboard, but still, code splitting keyboard by columns still lives in today's code.

Now, to the buttons on the left side:
"Reset" - it clears what you typed. This is useful if you accidentally (or not) clicked wrong button.
"Check" - checks correctness of your answer.

All these changes helped me to:
* delete a lot of lines of code
* make you click on screen less times

I guess the way to go this summer ladies is to cope u a python handbag this summer.Above is the Zagliani Python Z Bag which contains about a thousand times more sick ass pewter snakeskin surface area, plus you could buy it and wear it every day for the rest of your life, and that would make every murda mami happy.Damage:$4,290

Next we have The Gucci Jockey Python Bag meets all of your handbag needs; exotic skin, easy-to-wear shape, casual style. It is as if the Gucci Gods know how to tempt and have gone into your head, jumped in your dreams, and placed the perfect black bag in front of you....Damage:$3,295.

But there's an impedance mismatch between them.

In Buildbot, a ShellCommand is deemed to have failed if it returns a non-zero exit status, and succeeded if it returns a zero exit status.

Py.test always returns a zero status.  I guess their philosophy is: Py.test didn’t crash, so it was “successful,” and the exit status should be 0. So, when py.test returns a 0 status, Buildbot deems the ShellCommand successful — and therefore, the build “succeeded,” no build failure email is generated, and the buildbot waterfall remains green.

You’d think that py.test would have a "––returnnonzerostatusonfailure” switch.  But it doesn’t.

I found evidence on a mail archive that this problem has been around since 2005.

Am I missing something obvious, and if not, what’s the generally accepted way to work around this problem?

enum1.py:

[sourcecode language='javascript']import sys
filename = sys.argv[1]
f = open(filename)
print f.readlines()[0]
f.close()[/sourcecode]

enum2.py:

[sourcecode language='javascript']import sys
filename = sys.argv[1]
f = open(filename)
for i, line in enumerate(f):
print i, line
break
f.close()[/sourcecode]

ทั้ง 2 โปรแกรม print บรรทัดแรกอย่างเดียวนะครับ

veer@veer-laptop:wordalign$ time python enum1.py tha_cut_u8.txt > /dev/null
real	0m0.076s
user	0m0.044s
sys	0m0.032s

$ time python enum2.py tha_cut_u8.txt > /dev/null
real	0m0.021s
user	0m0.012s
sys	0m0.008s

enum2.py เร็วกว่ามาก ... น่าจะเป็นเพราะว่า enum2.py อ่านทีละบรรทัดแล้วก็มาทำอะไรต่ออะไรใน for-loop เลย. แต่ enum1.py อ่านทุกอย่างมาเก็บใน list แล้วค่อย มาทำอะไรใน list อีกที ... ถ้าเป็นแบบที่เดาจริง มันจะประหยัด memory กว่าถ้าใช้ enumerate. ประโยชน์อีกอย่างหนึงถ้าทำอะไรแบบ interactive ดูผลทีละบรรทัด ใช้ enumerate ก็น่าจะได้ดูไวกว่า.

Gobby is a free collaborative editor supporting multiple documents in one session and a multi-user chat. It runs on Microsoft Windows, Mac OS X, Linux and other Unix-like platforms.

Vor allem schreitet mein Lernprozess viel schneller voran als mit dem PDF :)

Das ganze funktioniert über einen offenen Port im Router und einer der Beteiligten muss den ganzen Spaß quasi "hosten". Mithilfe eines Passworts lässt sich dann die Session betreten und mehrere Dokumente bearbeiten/anlegen.

Dadurch sind wir dann auf die Idee gekommen uns unsere eigene kleine Welt zusammenzubasteln ;) Nur aus Spaß an der Freude und damit ich endlich lerne besser mit Python umzugehen. :)

Das ganze sieht in etwa so aus: (Nur ein ganz kleiner Entwurf :P )

[sourcecode language='python']
#!/usr/bin/python

class Person:
bevoelkerung = 0
def __init__(self, name, url):
self.name = name
self.url = url
print'%s Wird geboren' % self.name
Person.bevoelkerung +=1

def blog(self):
print 'Visit me on %s' % self.url

def __del__(self):
print '%s ist tot!' % self.name
Person.bevoelkerung -=1

if Person.bevoelkerung == 0:
print'ich bin der letzte'
else:
print'Es gibt noch %d Leute.' % Person.bevoelkerung

def sagHallo(self):
print 'Servus ich bin %s' % self.name
def wieViele(self):
if Person.bevoelkerung == 1:
print 'ich bin ganz alleine hier*angst*'
else:
print 'Es leben hier %d Leute' % Person.bevoelkerung

noqqe = Person('noqqe', 'noqqe.de' )
noqqe.blog()
noqqe.sagHallo()
noqqe.wieViele()
crackpod = Person('crackpod', 'crackpod.bplaced.net' )
crackpod.sagHallo()
crackpod.blog()
crackpod.wieViele()
noqqe.sagHallo()
noqqe.wieViele()
Julie = Person('Julie', 'julie.hat-gar-keine-homepage.de' )
Julie.sagHallo()
Julie.blog()
Julie.wieViele()
noqqe.__del__()
noqqe.wieViele()
[/sourcecode]

oder wie immer hier : http://paste.pocoo.org/show/79759/

Ausgabe sieht dann ungefähr wie folgt aus:
noqqe Wird geboren
Visit me on noqqe.de
Servus ich bin noqqe
ich bin ganz alleine hier*angst*
crackpod Wird geboren
Servus ich bin crackpod
Visit me on crackpod.bplaced.net
Es leben hier 2 Leute
Servus ich bin noqqe
Es leben hier 2 Leute
Julie Wird geboren
Servus ich bin Julie
Visit me on julie.hat-gar-keine-homepage.de
Es leben hier 3 Leute
noqqe ist tot!
Es gibt noch 2 Leute.
Julie ist tot!
Es gibt noch 1 Leute.
ich bin der letzte
crackpod ist tot!

To add enriched nuclear fuel to the fire, I couldn't work on my laptop. Why? Because of all the things I'd forgotten to do back from college, I forgot to configure my Debian for using the dial-up connection I have at home. And since I didn't have a pen drive to transfer content between my PC and my laptop, I was pretty much stuck. And if you didn't know, trying to work/hack on Windows is as good as trying to dance without feet. When the Google Code Jam happened yesterday, I couldn't submit my code because of this. I'd successfully solved one of the problems which was enough for me to qualify but darn.

On the bright side, I learnt python through that problem. I ain't that good a programmer and I'm still learning. As of now, I'm pretty much in love with python and this could be the one language I've been looking for since quite a while. An elegant combination of simplicity (near english like syntax) and power (very good built in datatypes and methods) is exactly what the doctor ordered in my case because I'm someone who wants to easily implement an algorithm without having to work out low level details. Haskell is the God of languages in this case which I'll come to shortly. And yes, I'm a lazy sloth.

During these three weeks, I tried my hand out in a lot of other things as well such as Perl, linux socket programming, linux driver coding, trivial kernel hacking and lastly, Haskell. Haskell is one thing that's impressed me a lot. Thanks Vivi for introducing me to it. Haskell is a purely functional programming language. To learn Haskell, you basically have to unlearn whatever programming you already know, and then learn it again from scratch. But learning Haskell makes you re-think and improve your programming methodology it seems. I didn't read too much on it because I couldn't download the Hugs compiler till I get back to college. No point learning if you can't try out code yourself, is there? Some ten/nine pointers I know would disagree :D . Anyways, Haskell works at a very high level compared to languages like C. Hence, you can do a quicksort in just one line! Yes, one line and thats it. Brilliant eh? Here's how it looks like...

qsort [] = []
qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++ qsort (filter (>= x) xs)

The first line means, "qsort on an empty list returns an empty list". The second line is read as follows, "qsort is a function operated on a list where the first element is x and the rest is tagged xs, such that the element x lies between two elements such that the ones on the right are greater than or equal to it and the ones on the left are less than or equal to it". ++ is the concatenation symbol. And yes, Haskell thrives on recursions.

I can't wait to get back to college and get into the hustle and bustle of life all over again. I'm also looking forward to attending the induction training programme for the Sun Campus Ambassadors in Bangalore between the 27th and 29th of this month. My CA work officially starts from the 1st of August. Anyways, I've laid down a set of goals for myself for the coming semester which according to Suvha, might lead to me ending up in an asylum. Maybe, I am overloading myself again. Maybe I'm not. Whatever the case, I guess I'm all for it now. I think I'm rejuvenated and wiser (laugh you morons...laugh) after a couple of lessons life thought me in the past few months. Let's see how things change now...

Cheers!

def MakeFile(file_name):

	"""
		MakeFile(file_name): makes a file.
	"""

	temp_path = 'C:\\Python25\\' + file_name
	file = open(temp_path, 'w')
	file.write('')
	file.close()
	print 'Execution completed.'

MakeFile('index.html')

And, it can be any file type you want and it can have whatever you want in it. You can even create a blank file. In fact, all files start out blank. Python needs a file to manipulate in order for it to actually manipulate anything. In other words, Python creates a blank file and then writes to it (if there is anything to write). This is why I tested the function twice, by the way.

python-updater hat dann gleich mal 65 Pakete neu kompiliert um den Umstieg komplett zu machen. Mit dabei war auch OpenOffice.org, das trotz angekündigter Kompilierzeit von vier Stunden nach eineinhalb Stunden fertig war. Ein Hoch auf CCache!

Este projeto é baseado em um componente para editor de texto, o Scintilla (um componente muito poderoso), escrito em C++ com pura api win32 e STL (o que garante alta velocidade de execução e pequeno tamanho de programa), está sob a licença da GPL.

Veja abaixo as características do Notepad++ :

1) Destaque de Sintaxes e Sintaxe de Blocos

Linguagens suportadas :

C, C++, Java, C#, XML, HTML, PHP, CSS, makefile, ASCII art (.nfo), doxygen, ini file, batch file,  Javascript, ASP, VB/VBS, SQL, Objective-C, RC resource file, Pascal, Perl, Python,  Lua, TeX, TCL, Assembler, Ruby, Lisp, Scheme, Properties, Diff, Smalltalk, Postscript, VHDL, Ada, Caml, AutoIt, KiXtart, Matlab, Verilog, Haskell, InnoSetup, CMake, YAML.

2) WYSIWYG (O que você vê é o que você tem)

Se você tiver uma impressora colorida poderá imprimir seu código fonte (ou qualquer outra coisa) em cores.

3) Destaque de Sintaxes Definida pelo Usuário

Isto permite ao usuário definir sua própria linguagem: não somente sintaxe de palavras chaves, mas também sintaxe de blocos (ex : If / endIf) , comentários e operadores. ( imagem1, imagem2, imagem3, imagem4 ).

4) Auto completar

Para quase todas as linguagens suportadas, o usuário pode criar sua própria lista de api (ou baixar os arquivos na sessão download). Uma vez que o arquivo api estiver pronto, digite Ctrl+Espaço para executar esta ação (veja a imagem). Para mais informações sobre o auto completar, por favor veja a sessão Auto completar.

5) Múltiplos Documentos

Você pode editar vários documentos ao mesmo tempo.

6) Múltiplas Visualizações

Você tem duas visualizações ao mesmo tempo. Na qual você poderá visualizar/editar 2 documentos diferentes ou o mesmo documento (imagem). Você pode visualizar (editar) em 2 vistas um documento, em posições diferentes. A modificação de uma das vistas acontecerá na outra também. (ou seja, você modifica o MESMO documento quando você está no modo clone, veja a imagem).

7) Suporta Expressões de Busca/Substituição

Você pode buscar a substituir uma string (frase) no documento usando expressões regulares.

8 ) Suporta o Arrastar e Soltar

Você pode abrir um documento arrastando e soltando. Você pode também mover seu documento (ou visualização) de uma posição a outra usando o Arrastar e Soltar.

9 ) Posição Dinâmica de Visualizações

O usuário pode escolher a posição de uma visualização dinamicamente (somente em 2 modos : separação horizontal ou vertical), veja a imagem.

10) Auto detecção de Estado do Arquivo

Se você modificar ou apagar um arquivo que esteja aberto no Notepad++, você receberá uma notificação para atualizar seu documento (recarregar o arquivo ou apagar o arquivo).

11) Avanço/Recuo de Zoom

Esta é uma outra fantástica função do componente Scintilla. Simplesmente veja a imagem.

12) Ambiente com Suporte a Múltiplos Idiomas

O chinês, japonês, coreano, árabe e hebraico são suportados no ambiente Windows. Veja o Notepad++ sob o Chinês - Windows , sob o Árabe - Windows e sob o Hebraico - Windows em ação.

13) Marcadores

Basta clicar na margem para inserir um marcador (no lado direito da margem junto ao nº da linha) ou digitar Ctrl+F2 para inverter o marcador. Para ir até um marcador, digite F2 (Próximo Marcador) ou Shift+F2 (Marcador Anterior). Para excluir todos os marcadores, clique no Menu Localizar->Excluir Marcadores. Veja a imagem.

14) Chaves, Colchetes e Parênteses com Destaque

Quando o cursor se apróxima de um desses símbolos { } [ ] ( ) , o símbolo que está próximo ao cursor e o símbolo simetricamente oposto são destacados, assim como sua guia de identação (se houver) fazendo com que a localização de um bloco seja mais fácil. Veja a imagem1,  imagem2 .

15) Grava e Reproduz Macros

Você pode salvar várias macros e criar atalhos de tecla para o próximo uso.

DOWNLOAD: Para baixar o programa Notepad++ (v.5.0) e obter maiores detalhes sobre  arquivos de ajuda, arquivos de api, arquivos binários, arquivos de estilos, arquivos de imagens, códigos fonte, temas, plugins,  vá diretamente do site do desenvolvedor: clicando aqui

Já existe a versão 5.0.1 do programa Notepad++ disponível no Baixaki, porém, testamos o executável e o mesmo apresentou erro na hora da instalação, assim, não disponibilizaremos o link dessa versão.

O programa tem 2,03MB, não possui limitações, é totalmente gratuito e funciona nos sistemas: Windows XP/98/2000.

]]> http://fernandoacorreia.wordpress.com/?p=39 Sun, 20 Jul 2008 01:31:47 +0000 fernandoacorreia http://fernandoacorreia.wordpress.com/?p=39 I am continuing to learn how to integrate Flex to Google App Engine. Now my test project is able to update objects, in addition to inserting and retrieving them.

On the server side, this is done by the update service operation:

[sourcecode language='python']
def update(self, project):
    logging.debug('udpate %s' % (project))
    existing_project = Project.get(project._key)
    existing_project.name = project.name
    existing_project.put()
    return Project.get(project._key)
[/sourcecode]

There is also a new save operation that decides between insert and update depending on the state of the object. If the object was read before, it is updated. Otherwise, it is inserted:

[sourcecode language='python']
def save(self, project):
    logging.debug('save %s' % (project))
    if hasattr(project, '_key') and project._key != None:
        return self.update(project)
    else:
        return self.insert(project)
[/sourcecode]

The App Engine model is also saving the date and time each object was last modified:

[sourcecode language='python']
class Project(db.Model):
    # ...
    modified_at = db.DateTimeProperty(auto_now=True)
[/sourcecode]

On the client side, the save operation is called after an object is prepared. If the object was being edited, its key was saved and so the service will know it must be updated. If it is a new object, the key will be null so the service will insert a new object.

[sourcecode language='jscript']
public function submitProject():void {
    var newProject:Object = new Object();
    newProject.code = project_code.text;
    newProject.name = project_name.text;
    newProject._key = project._key;
    gateway.call("ProjectService.save", new Responder(null, onFault), newProject);
    getProjects();
}
[/sourcecode]

The _key property is a very important piece of information in this context. So I patched the PyAMF library to include it within every object it sends to the client. There is a ticket for that on the PyAMF project.

[sourcecode language='python']
def writeObjectAMF(self, obj, args, kwargs, remove):
    """
    Writes an object that has already been prepared by writeObjectAMF0 or writeObjectAMF3.
    """
    try:
        obj._key = str(obj.key())
    except:
        obj._key = None
    self.writeObject(obj, *args, **kwargs)
    del obj._key
    if remove:
        self.context.class_aliases[obj.__class__] = None
[/sourcecode]

All the source code for this project is hosted in github. Please be aware that I am sharing what I find out as I learn. I am sure there are better ways of using this tools. I hope to learn them. Comments are welcome.

This is where my trouble was. I was reading the article about how import works from the standard Python docs. So I read as much as I thought I needed and skipped over, what I thought at the time, to be unimportant. As it turns out the ability to do relative imports using '..' is a feature of only Python 2.5 *sigh*. Alright, so I could have just installed Python 2.5, but I didn't want to limit this code to running on Python 2.5 for no good reason. So I went back and changed the code to using absolute imports which took around 30 minutes because there were a decent number of files to play with.

So how did I miss this in the documentation? Well I managed to skim over the part which mentions this is only for Python 2.5 (I blame myself for this, btw). I take this as a lesson to pay closer attention when reading documentation. It may have taken me an extra 5 or 10 minutes to read all the documentation about imports and Python... but I will would have saved half an hour of my time if I had taken the extra effort :)

mapping = {5 : "5", 6 : "6"}
for key, val in mapping.items(): ...

Use iter* methods when possible

mapping = {5: "5", 6: "6"}
for key, val in mapping.iteritems(): ...
for key in mapping: ...

Let me explain why I suggested this practice and, despite much critique, still maintain it's makes the most sense.

First of all, the setuptools documentation states:

Note: the project version number you specify in setup.py should always be the next version of your software, not the last released version.

So it's a convention that seems to be generally suggested. That doesn't necessarily mean it's a good idea, though.

What makes it a good idea is the fact that when you get a checkout of the trunk or a development branch, the version number is actually meaningful, due to setuptools' version semantics

3.4.1 < 3.4.2dev < 3.4.2

So, a development egg of zope.interface 3.4.2dev will for instance satisfy a version requirement like "zope.interface > 3.4.1". For example, say you wanted to temporarily deploy from a subversion checkout. I had to do this to get my PyFlakes running with Emacs. The latest release PyFlakes 0.2.1 wasn't good enough because something got fixed on the trunk. So I got a trunk checkout and did a

python setup.py install

into a virtualenv. Surely enough, the trunk's version number was still pointing to 0.2.1. So I ended up with pyflakes-0.2.1-py2.4.egg in my site-packages and no way to tell it from the actual 0.2.1 release. (Yes, I know there's some setuptools parameter than can let you build versions like 0.2.1-r48292, and those would be fine, if they were configured to occur on the trunk automatically.) So that's why not only bumping the version number to the next release but also adding the "dev" marker to tell development eggs or snapshots apart from actual release (and prevent people from releasing from the trunk!) is a good idea.

To conclude, I think bumping the version number to the next or at least the next anticipated release (it's ok if you don't get the version number right the first time) and adding a dev marker is not only a good idea, I think it's pretty much the only way to get the version number semantics of development eggs right (unless you use r34234 suffixes which have other problems). Of course, I'm willing to be convinced otherwise if alternate solutions achieve the same semantics. Comment away!

Thus, my first few experiences with Django on Python have been remarkable. First some

Story-telling

(The meat and potatoes are below ...)

1) My wife started a home-based child care business for the Tigard (Oregon) area. I put together a mini-website that lets her edit page content, add pages and manage an activity log that is accessible only to registered parents. More work is necessary, especially for content. I was focusing on high ranking in Google when doing keyword research, registering the domain name and putting content together, but I was a little surprised to see this site come up in the first position of the SERP for the query "day care tigard" a few days after posting it. The challenge now is to make it first for "child care tigard" ... but I have a few ideas.

2) We updated the previous splash site for EcoFarms International, LLC, which specializes in growing organic produce year-round. The business users can now post "newsletters" (similar to blog entries) either as a new page or as a PDF upload. The key functionality is the newsletter notification, which is sent to people who signed up for it. I am working on making this a little bit more robust along the lines of Foreclosures 4 Investors, for which I implemented a system that sends on the order of 100,000 opt-in e-mails per month. The business users also get statistics regarding how often recipients click on links in the notifications.

3) A good friend of mine is getting married, so I put together a simple site with an RSVP form. I spent most of the time on the design (of the website and an invitation), which was based on work provided by Ben Tabb, a web designer here in Portland.

The mythical man week

All three sites together took less than 40 weekend-only-early-morning-and-night hours (the weekdays where slammed with my work at Aisle7). That includes (almost) all design work, all markup and styling work, all programming and framework configuration, all the time spent setting up the sites at the hosting provider and all client communication.

Stunned and humbled

That's not bad for three projects. Especially considering that when I started, I had very little--virtually no--experience either in programming Python or working with the Django Framework. The 40 hours also included me setting up an appropriate development environment after researching the options, learning "pythonic" programming, reading the relevant Django documentation and diving into the framework. I spent parts of this man week debugging mistakes like ('not a tuple') instead of ('a tuple',) and learning about mutable function parameter defaults (thanks to PyLint^[1], and no, I don't think it's a wart) as well as the intricacies of the PYTHON_PATH. I fixed a bug locally in the Django framework that caused the ConditionalGetMiddleware not to function properly (a later update from trunk applied the exact same fix). And I found a simple SMTP server written in Python that I could use to test the notification function and the RSVP form locally. Having WebFaction as a hosting provider enabled me, within this time frame, to also configure trac (including the Eclipse Mylyn-trac integration) and SVN (including post-commit e-mail notifications for our loosely coupled team). I don't know of any other platform/tool combination that would allow (me) this level of productivity.

BTW, I spent an estimated 4 of those 40 hours fixing CSS styling issues around IE 6 quirks, which shows how much this browsers really sucks. (Or how poor my CSS skills are? Nah, that can't be it ...)

The right tool for the right job

Django is great to work with, but it helped to have a certain development environment setup: I run PyDev on Eclipse (including the extensions). I have the Django SVN trunk checked out and configured as a project in Eclipse. Each new project gets the Django project as a dependency, which gives me code completion and automatic import statement generation. This configuration also enables me to click on any Django class or method and jump directly to the source, which is better than any documentation.

I am fairly new to Python, and I am already very excited about the language. What impresses me is the brevity of the code that is achieved without relying on hacky shortcuts--all the syntax clutter was simply left out.

a=range(10000)
# add some duplicates to the list
for x in range(10,10000,3):
    a.append(x)
 
g=[]
for z in a:
    if z not in g:
        g.append(z)

This is fine and seems to work, but if you ever have a large list you will notice quite a lot of slowdown. There is a better way, which is very simple and speeds up the process a lot. First you need to make sure the list is sorted, and then you simply omit appending the item from the first list if it is the same as the value from the last iteration:

a=range(10000)
# add some duplicates to the list
for x in range(10,10000,3):
    a.append(x)
 
g=[]
y=0
for z in a:
    if z!=y:
        g.append(z)
    y=z

If your reasoning is built upon simple steps that you have learned well then you will avoid complexity panic. Each time you go back to basics you see new angles, until you know the basics so well that they are a part of you, and then you can climb higher up the mountain.

The snake had somehow got in to her house through the water pipes as it was searching for somewhere damp to reside.

Snakes alive!

And, just as I was about to try and get more laundry done!  I know, any excuse, right?

• Ruby Cheat Sheet is a link to a couple of cheat sheets and also to quick references to the language. Came in very handy
• Perl 5 Cheat Sheet from CPAN
  

  This 'cheat sheet' is a handy reference, meant for beginning Perl programmers. Not everything is mentioned, but 194 features may already be overwhelming.

• Python 101 Cheat Sheet, covers more than one sheet :P but is EXTREMELY helpful for beginners like myself. And here's a quick reference to Python as well.
• Java Quick Reference (Cheat Sheet)
• PHP Syntax Cheat Sheet, in the same link there's also a fun syntax exam you can test yourself with.
• C Cheat Sheet
• C++ Refresher Cheat Sheet
• Here's a great collection of Ruby on Rails cheat sheet.
• You can consider this site and interactive HTML+CSS cheat sheet. A must bookmark.
• Perl 6 Cheat Sheet

We are a Python loving lot. We use the Pylons framework and Schevo ODBMS. I can recommend both. We are on a Ubuntu Hardy Server @ Linode and Slicehost. We serve using Apache and Paste HTTP Server. We use google apps for all emailing needs.

If you have specific questions, drop a comment or email.

As a result of this a new module has been started to keep everything related to views and layers and such, and it will probably be called grokcore.browser (although it's currently called grokcore.view). Just as grokcore.component extracts the parts from grok that has to do with the component architechture, grokcore.[browser|view] has all the parts with Zope views. We hope to get this accepted into Grok itself, so that both Grok and five.grok ends up using it, because there is a lot of code, and a massive amount of tests to handle views, and it would be silly to have two implementations of everything.

As a result of this, five.grok now has both adapters and utilities and views, and is therefore right now starting to become useful. Some have today been sprinting on an example application of how to extend a Zope2 object with five.grok views. We hope this example application will show us what is missing and what the next parts to be added to five.grok is.

If you are going there and want to meet leave me a note, I am looking forward to meet other geeks there. :D