Skip to content

Instantly share code, notes, and snippets.

View andres-torres-marroquin's full-sized avatar
🎯
Focusing

Andrés Torres Marroquín andres-torres-marroquin

🎯
Focusing
View GitHub Profile
@andres-torres-marroquin
andres-torres-marroquin / gist:1052444
Created June 28, 2011 22:45
Google Chrome splinter 0.1.1
Feature: Going Once, Going Twice. # apps/mainsite/features/going_once_twice_auctions.feature:1
Scenario: In the homepage # apps/mainsite/features/going_once_twice_auctions.feature:3
Given that I have an auction about to be closed # apps/mainsite/features/step_definitions/going.py:6
When I go to the auction page # apps/mainsite/features/step_definitions/going.py:11
Then I see the "GOING ONCE" in the auction timer # apps/mainsite/features/step_definitions/going.py:15
Traceback (most recent call last):
File "/home/atorres/virt_env/virt1/lib/python2.6/site-packages/lettuce/core.py", line 113, in __call__
ret = self.function(self.step, *args, **kw)
File "/home/atorres/Desktop/bidsite/apps/mainsite/features/step_definitions/going.py", line 20, in see_the_text_in_the_timer
"""
lockfile.py - Platform-independent advisory file locks.
Requires Python 2.5 unless you apply 2.4.diff
Locking is done on a per-thread basis instead of a per-process basis.
Usage:
>>> lock = LockFile('somefile')
>>> try: