“eth0:2010 summer” will be held from the 10th of August up to and including the 13th of August 2010.
April, 2010
21
Apr 10
Its been a while
It has been a while sins my last blog post
there is a lot going on a new job, Atoomlan, the eth-0 Summer event
To start with the first one it was a good idea to switch jobs a new environment is doing a lot of good to me. Met a lot of new people and done a lot of new things Innovaphone for example for me a completely new voip system what equally works. Configured a lot of routers in the last 2 months. Done the Innovaphone advanced training. Working hard on rebuilding and improving the current networks at work.
Atoomlan wat can i say its a lanparty with skilled people, together with a friend of mine we are working hard to get our ftp cluster up and running hopefully we can test it at Atoomlan and use it at eth-0 Summer trying to build one of the fastest ftp server at the site with a lot of storage for storing and sharing file at 10Gbits/s
Then eth-0 The Summer camp we are working hard to get every thing done for the compete camp network including the uplink witch will be on fiber this time to ensure we can get all te speed we got offered last time the wireless uplink workt fine but it was not fast 20mbit is oke for not so mutch people but 200 geeks on 20mbit i think we need more so this time fiber hoping to get a 100/1000mbit uplink again but we will see
First lets see how Atoomlan is going and our ftp cluster is preforming
13
Apr 10
Vim, python pep8 and pylint.
When you are making your Python code pep8 conformant or want to have a good pylint score and you are using vim, there are a few ways to make it easier and faster.
First you need to know a bit about the vim option -q. -q takes a filename as a argument, and vim then uses this file to jump to locations in files where the used tool has reported something. Vim expects a very simple format here.
Vim can take the output of the pep8 command:
pep8 --repeat --ignore=E501 *.py > ~/pep.txt
Then start vim with:
vim -q ~/pepepep.txt
Vim then opens with the first reported issue, to go to the next, use :cn.
Or you can temporarily map z to that for this vim session:
:map z :cn<cr>
Like with pep8, you can do the same with pylint, but you need to use the --format parseable argument:
pylint views.py -f parseable > ~/pep.txt
Some regexps for common formatting issues
Remove trailing whitespace all over the file:
:%s/\s\+$//
Remove whitespace in front of a ,
:s/\s*,/,/
Remove whitespace in front of an equal-sign, if any, add a space.
:s/\s*=/ =/