jace

@hasgeek , Got this as one of the responses for a listing that
specifically asked "NOT OK for recruiters, HR consultants, and other
intermediaries to contact this employer" . And I don't understand half
of it , what its trying


Thanks
[snip]

---------- Forwarded message ----------

jace

@hasgeek , Got this as one of the responses for a listing that
specifically asked "NOT OK for recruiters, HR consultants, and other
intermediaries to contact this employer" . And I don't understand half
of it , what its trying


Thanks
[snip]

---------- Forwarded message ----------

jace

PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE node (
	id INTEGER NOT NULL, -- from Mixin
	name VARCHAR(200), -- from Mixin
	published BOOLEAN NOT NULL, 
	type VARCHAR(20), 
	title VARCHAR(200), -- from Mixin
	PRIMARY KEY (id), 
	CHECK (published IN (0, 1))

jace

# -*- coding: utf-8 -*-

import unittest
from docflow import (DocumentWorkflow, WorkflowState, WorkflowStateGroup,
    WorkflowStateException, WorkflowTransitionException, WorkflowPermissionException)

class MyDocument(object):
    def __init__(self):
        self.status = None
        self.email = ''

jace

Python Document Workflows

An implementation of document workflows in Python. Designed for SQLAlchemy but not dependent upon it.

Note: This is currently just a planning document.

Usage:

jace

jace@razor ~/Downloads/mapbox-tilemill-4ba9aea $ ./ndistro           [22:32:25]
... building node-0.2.6
######################################################################## 100.0%
Waf: Entering directory `/Users/jace/Downloads/mapbox-tilemill-4ba9aea/src/node-0.2.6/build'
[ 1/69] cc: deps/libeio/eio.c -> build/default/deps/libeio/eio_1.o
In file included from ../deps/libeio/eio.c:77:
default/config.h:10:1: warning: "HAVE_FDATASYNC" redefined
<command-line>: warning: this is the location of the previous definition
[ 2/69] cc: deps/libev/ev.c -> build/default/deps/libev/ev_1.o
In file included from ../deps/libev/ev.c:49:

jace

#!/usr/bin/env python

"""
Functions to represent UUIDs as Base64 strings.

Base64 typically uses '+' and '/' as encoding characters. Neither are URL-safe,
so these functions use ',' and '-'. The characters '.' and '_' were considered,
but rejected, as some web frameworks will treat any URL fragment starting with
them as a hidden resource.
"""