Mercurial > p > roundup > code
view website/www/code.txt @ 5011:d5da643b3d25
Remove key_in() from roundup.anypy.dbm_
The key_in() function was just a shim to use the best available option
out of 'd.has_key(key)' and 'key in d'. The 'd.has_key(key)' flavour has
been deprecated in favour of 'key in d' which based on testing has been
available since at least python v2.5 which is the oldest being
supported.
| author | John Kristensen <john@jerrykan.com> |
|---|---|
| date | Fri, 13 Feb 2015 00:20:43 +1100 |
| parents | b77ef61a844e |
| children | 98344ba5e157 |
line wrap: on
line source
Code ==== Changelog ---------- The changelog is available as `CHANGES.txt in the SCM repository <https://sourceforge.net/p/roundup/code/ci/tip/tree/CHANGES.txt>`_. Browse ------ `Browse the repository <https://sourceforge.net/p/roundup/code/>`_. Read-only Access ---------------- Read-only repository access is provided through :: hg clone http://hg.code.sf.net/p/roundup/code roundup-code The URL for the webinterface works, too, but you will see messages about redirects to the URL shown here. Read-write Access ----------------- The read/write access uses your SourceForge.net ssh password or ssh key to authorize your access. (See `SF's site documentation on Mercurial access <https://sourceforge.net/p/forge/documentation/Mercurial/>`_) :: hg clone ssh://USERNAME@hg.code.sf.net/p/roundup/code roundup-code Of course a roundup developer must have granted you write access first - ask for it on the roundup-devel list.