VirtualTam's bookmarks

1641. Index of PHP Standard Recommendations 2015-03-12

      tags: code, coding, development, guide, programming/php, standard, style

      [ permalink ]

      • PSR-1 Basic Coding Standard - http://www.php-fig.org/psr/psr-1/
      • PSR-2 Coding Style Guide - http://www.php-fig.org/psr/psr-2/
1642. Emacs Key Sequences (kbd) 2015-03-10

      tags: development, editor/emacs, kbd, programming/lisp

      [ permalink ]

      kbd converts a human-readable chord to a key sequence

1643. Elpy, the Emacs Lisp Python Environment 2015-03-08

      tags: development, editor/emacs, ide, mode, programming/lisp, programming/python

      [ permalink ]
1644. Bootstrap Magic: Generate your own bootstrap theme quickly and easily 2015-03-08

      tags: bootstrap, generator, programming/css, theme, web

      [ permalink ]
1645. SLIME: The Superior Lisp Interaction Mode for Emacs 2015-03-06

      tags: development, editor/emacs, programming/lisp, slime, symbolic

      [ permalink ]

      https://common-lisp.net/project/slime/

1646. Iterables vs. Iterators vs. Generators 2015-03-03

      tags: development, evaluation, generator, iterator, lazy, list, programming/python, yield

      [ permalink ]
1647. Progress bar for latex-beamer - TeX - LaTeX Stack Exchange 2015-03-02

      tags: bar, presentation, programming/latex, programming/latex/beamer, progress, slide

      [ permalink ]
1648. LaTeX: Presentations with Beamer 2015-03-02

      tags: code, demo, development, presentation, programming/latex, programming/latex/beamer, slide

      [ permalink ]

      https://en.wikibooks.org/wiki/LaTeX/Source_Code_Listings https://en.wikibooks.org/wiki/LaTeX/Hyperlinks

1649. If programming languages were vehicles 2015-03-02

      tags: car, development, fun, language, programming, vehicle

      [ permalink ]
1650. 4bit - Terminal Color Scheme Designer 2015-02-27

      tags: color, programming/shell, putty, terminal, theme

      [ permalink ]
1651. Review of PHP Static Analysis Tools 2015-02-22

      tags: analysis, code, programming/php, quality, static, web

      [ permalink ]
1652. Misconceptions about testing (and what we should do about them) 2015-02-22

      tags: bug, framework/django, programming/python, programming/testing, quality, unit

      [ permalink ]
1653. Kimchi: KVM web management interface 2015-02-14

      tags: linux, programming/python, sysadmin, virtualization, virtualization/kvm, web

      [ permalink ]
1654. Practical Common Lisp 2015-02-13

      tags: artificial-intelligence, code, development, programming, programming/functional-programming, programming/lisp

      [ permalink ]

      Beware! Very cool book dealing with Lisp programming, with plenty of examples

1655. Become a Programmer, Motherfucker 2015-02-13

      tags: code, design, development, mofo, programming, programming/c, programming/c++, programming/java, programming/lisp, programming/python, software

      [ permalink ]

      Programming... Do you speak it?

1656. Python unit testing frameworks: Nose, Pytest 2015-02-13

      tags: code, coverage, feature, nose, programming/python, programming/python/pytest, programming/testing, quality, unit

      [ permalink ]

      Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)

      I'm currently looking for more dev-friendly solutions, the key points being:

      • writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
      • parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
      • complete feature set!
        • we don't want to just run tests...
        • coverage reports (find dead/weak/untested code sections)
        • output formatting (JUnit-XML seems to be quite a common format out there)

      There seem to be 3 solutions in Python:

      • stock unittest + project-dependent customizations / test helpers
      • nosetests
      • py.test

      And 2 ways of gettings things done:

      • keeping things stock: no external dependency, project-specific implementation...
      • using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)

      Some links:

      • http://stackoverflow.com/questions/22856638/nose-vs-pytest-what-are-the-subjective-differences-that-should-make-me-pick
      • http://helixyte.org/2014/04/unit-testing-adventures-moving-from-nose-to-pytest/
      • http://lists.idyll.org/pipermail/testing-in-python/2013-August/005624.html
1657. Python: run specific unit tests 2015-02-13

      tags: bug, code, programming/functional-programming, programming/python, programming/testing, quality, unit

      [ permalink ]

      Given your unittests are in the tests directory:

       1# run a specific test module
       2python -m unittest tests.<module>
       3 
       4# run a specific test suite
       5python -m unittest tests.<module>.<class>
       6 
       7# run a specific test
       8python -m unittest tests.<module>.<class>.<test>
       9 
      10# run tests matching a given pattern
      11python -m unittest discover -s tests -p <pattern>
      

1658. Flow: a static Javascript typechecker 2015-02-11

      tags: analysis, code, continuous-integration, programming/javascript, static, web

      [ permalink ]
1659. Homepage | Celery: Distributed Task Queue 2015-02-11

      tags: distributed, network, programming/python, queue, task

      [ permalink ]
1660. Disabling electric indenting in Emacs modes - foldl 2015-02-07

      tags: auto, editor/emacs, electric, indent, mode, org, programming/python

      [ permalink ]

      electric-indent has been activated by default in emacs 24

      to disable it for Python: (add-hook 'python-mode-hook (lambda () (set (make-local-variable 'electric-indent-functions) (list (lambda (arg) 'no-indent)))))