Skip to main content

Should I move RRiki from Ruby(Rails) to Python?

It boils down to
  1. Rails automagically uses the database contents to create an interface, in the other frameworks you have to explcitly create a database in the code.
  2. I use Python for computing, why not use it for note taking too.
Comparison of Rails and Django. [bright-green]

Possible Python frameworks:

web2py. - no configuration/install to use, can be used from a USB drive. After a laptop crash that option looks tempting..., has migrations which Django doesn't.

UPDATE: I'm not moving for now due to time constraints. I will at most look into using SQlite, instead of MySQL
Labels:

Comments

  1. AnonymousMarch 23, 2008 at 9:58 AM

    Yes you should! I will be happy to pride all the support you need with web2py. I just learned about rriki. It is an excellent project. Congratulations. I will use it myself. (massimo)

    ReplyDelete
  2. Kaushik GhoseMarch 23, 2008 at 1:05 PM

    That will be great! I will bug you from time to time, when I get stuck with some intricacies of web2py and/or python.

    I'm also going to try and move from MySQL to SQLite, since RRiki is basically a single user desktop app.

    Thanks so much Massimo

    ReplyDelete
  3. Kaushik GhoseMarch 23, 2008 at 4:50 PM

    Hi Massimo,

    I'm trying out web2py following the cookbook example. I'll post random notes on comments to this post:

    If application name has a dot e.g. rwiki.py web2py says it has created the app, but does not show it on the list. Perhaps notify user that dot '.' is an illegal character etc.

    ReplyDelete
  4. MaxMarch 23, 2008 at 9:39 PM

    I just fixed that in the trunk. Mind that web2py was correct in saying that the app was created but because of the '.' in the name it is not displayed and not accessible. You may want to remove the useless folder under applications. Please bug me, you have a very interesting project and I can see many uses for it.

    ReplyDelete
  5. Kaushik GhoseMarch 25, 2008 at 8:38 AM

    Hi Massimo,

    web2py (aka gluon) (why did you change the name btw?) is very impressive.

    I will, however stick to Ruby on Rails for RRiki for now simply due to time constraints.

    At most, what I may do is move RRiki from MySQL to SQlite to improve database portability between machines, but that's also iffy wrt time available.

    I'll definitely keep gluon in mind though, if I decide to port RRiki when I have more time, in September or so.

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty
Post a Comment
Read more