HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
frasertweedale
elk
Python2014–2014
frasertweedale / elk

elk

Moose-like object system for Python

2Distinct people
3Mentions
0Explicit recommenders
29GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Moose-like object system for Python

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2014-08-03 04:56:27 UTC to 2014-11-19 02:10:05 UTC. Weeks start Monday, UTC.

0122014-07-28 00:00:00 UTC to 2014-08-04 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJul 282014-08-04 00:00:00 UTC to 2014-08-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-08-11 00:00:00 UTC to 2014-08-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-08-18 00:00:00 UTC to 2014-08-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-08-25 00:00:00 UTC to 2014-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-01 00:00:00 UTC to 2014-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-08 00:00:00 UTC to 2014-09-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-15 00:00:00 UTC to 2014-09-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-22 00:00:00 UTC to 2014-09-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 222014-09-29 00:00:00 UTC to 2014-10-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-06 00:00:00 UTC to 2014-10-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-13 00:00:00 UTC to 2014-10-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-20 00:00:00 UTC to 2014-10-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-27 00:00:00 UTC to 2014-11-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-11-03 00:00:00 UTC to 2014-11-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-11-10 00:00:00 UTC to 2014-11-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-11-17 00:00:00 UTC to 2014-11-24 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 17

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 282014-07-28 00:00:00 UTC2014-08-04 00:00:00 UTC202
Aug 42014-08-04 00:00:00 UTC2014-08-11 00:00:00 UTC000
Aug 112014-08-11 00:00:00 UTC2014-08-18 00:00:00 UTC000
Aug 182014-08-18 00:00:00 UTC2014-08-25 00:00:00 UTC000
Aug 252014-08-25 00:00:00 UTC2014-09-01 00:00:00 UTC000
Sep 12014-09-01 00:00:00 UTC2014-09-08 00:00:00 UTC000
Sep 82014-09-08 00:00:00 UTC2014-09-15 00:00:00 UTC000
Sep 152014-09-15 00:00:00 UTC2014-09-22 00:00:00 UTC000
Sep 222014-09-22 00:00:00 UTC2014-09-29 00:00:00 UTC000
Sep 292014-09-29 00:00:00 UTC2014-10-06 00:00:00 UTC000
Oct 62014-10-06 00:00:00 UTC2014-10-13 00:00:00 UTC000
Oct 132014-10-13 00:00:00 UTC2014-10-20 00:00:00 UTC000
Oct 202014-10-20 00:00:00 UTC2014-10-27 00:00:00 UTC000
Oct 272014-10-27 00:00:00 UTC2014-11-03 00:00:00 UTC000
Nov 32014-11-03 00:00:00 UTC2014-11-10 00:00:00 UTC000
Nov 102014-11-10 00:00:00 UTC2014-11-17 00:00:00 UTC000
Nov 172014-11-17 00:00:00 UTC2014-11-24 00:00:00 UTC101

What Hacker News says

3 sources
I want to write something concise and coherent, but it's not happening today :) Instead, assuming you've read the teasers in the Moose manual [1] I'd recommend this [2] interesting comparison of how horizontal code re-use can be achieved in Java, Ruby, PHP and Perl+Moose. There's more philosophical/winding essays on Moose from Chromatic, for example at [3]. Roles/traits/method modifiers/MOP/composability etc. are all great things for getting more reusability... however (and this might sound stupid) the thing that saddens me most when writing Python code is when I find myself adding a bunch of asserts or adding program logic "manually" in situations where I'd normally specify that sort of thing declaratively in a Moose class definition or by referring to a centrally managed Type or delegate stuff through attribute features. On the other ha
Read the rest
nd, I'm barely into year 2 of full-time Python dev, so perhaps I've yet to find the idiomatic way of doing Python things I used to take for granted in Moose. Regarding Perl 6, I don't know much about it, except that the original authors of Moose had some inspiration from it. Is picking up Perl+Moose mind-expanding? It was for me, but I feel that what Moose gave me in Perl was a bit of a band-aid over the fact that it's such a malleable open-ended dynamic language. So as a C++/Java programmer this aspect might not be so enlightening to you, except to see how Moose achieves it in a pretty painless way that I think is very nice and idiomatic for a dynamic language (with the caveats that brings). To put it another way: it gives Perl some of the great benefits of properly declaring things up-front, without the boilerplate/inflexibility pain that I perceive the Java ecosystem's bureaucracy to be (I haven't touched Java for 10 years, so take that with a grain of salt). If you want to explore some Moose-ish kinds of things within Python, check out [4] (there's another Moose clone in Python that's similarly inactive, sadly) and [5] (Enthought's stuff is perhaps a bit too heavy and incomplete to be the "Moose of the python world", but it gives you a good idea of some of the nice patterns possible when you think outside of the core Python OO featureset). [1] http://search.cpan.org/dist/Moose/lib/Moose/Manual.pod [2] http://radar.oreilly.com/2014/01/horizontal-reuse-an-alterna... [3] http://modernperlbooks.com/mt/2009/05/perl-roles-versus-inte... [4] https://github.com/frasertweedale/elk [5] http://code.enthought.com/projects/traits/
In Why Python Is Slow: Looking Under the Hood
Sure. And just for attributes, there's also delegation, read-only attributes, builders, lazy init, roles, modifiers which are enforced at construction time (if `required` is true). Moose isn't hard to implement, it's actually had quite a few alternate implementations even in Perl. Python has enthought's traits package, and I've just been pointed to https://github.com/frasertweedale/elk as well. BTW it sucks to nit-pick, but the Moose version isn't any more verbose than yours: package Foo; use Moose; has 'bar' => ( isa => 'Integer' );
In Introduction to Moose, Perl’s OO system

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.