ee24bdb1c8
- *Major packrat upgrade*, inspired by patch provided by Tal Einat - many, many, thanks to Tal for working on this! Tal's tests show faster parsing performance (2X in some tests), *and* memory reduction from 3GB down to ~100MB! Requires no changes to existing code using packratting. (Uses OrderedDict, available in Python 2.7 and later. For Python 2.6 users, will attempt to import from ordereddict backport. If not present, will implement pure-Python Fifo dict.) - Minor API change - to better distinguish between the flexible numeric types defined in pyparsing_common, I've changed "numeric" (which parsed numbers of different types and returned int for ints, float for floats, etc.) and "number" (which parsed numbers of int or float type, and returned all floats) to "number" and "fnumber" respectively. I hope the "f" prefix of "fnumber" will be a better indicator of its internal conversion of parsed values to floats, while the generic "number" is similar to the flexible number syntax in other languages. Also fixed a bug in pyparsing_common.numeric (now renamed to pyparsing_common.number), integers were parsed and returned as floats instead of being retained as ints. - Fixed bug in upcaseTokens and downcaseTokens introduced in 2.1.5, when the parse action was used in conjunction with results names. Reported by Steven Arcangeli from the dql project, thanks for your patience, Steven! - Major change to docs! After seeing some comments on reddit about general issue with docs of Python modules, and thinking that I'm a little overdue in doing some doc tuneup on pyparsing, I decided to following the suggestions of the redditor and add more inline examples to the pyparsing reference documentation. I hope this addition will clarify some of the more common questions people have, especially when first starting with pyparsing/Python. - Deprecated ParseResults.asXML. I've never been too happy with this method, and it usually forces some unnatural code in the parsers in order to get decent tag names. The amount of guesswork that asXML has to do to try to match names with values should have been a red flag from day one. If you are using asXML, you will need to implement your own ParseResults->XML serialization. Or consider migrating to a more current format such as JSON (which is very easy to do: results_as_json = json.dumps(parse_result.asDict()) Hopefully, when I remove this code in a future version, I'll also be able to simplify some of the craziness in ParseResults, which IIRC was only there to try to make asXML work. - Updated traceParseAction parse action decorator to show the repr of the input and output tokens, instead of the str format, since str has been simplified to just show the token list content. (The change to ParseResults.__str__ occurred in pyparsing 2.0.4, but it seems that didn't make it into the release notes - sorry! Too many users, especially beginners, were confused by the "([token_list], {names_dict})" str format for ParseResults, thinking they were getting a tuple containing a list and a dict. The full form can be seen if using repr().) For tracing tokens in and out of parse actions, the more complete repr form provides important information when debugging parse actions. |
||
---|---|---|
.github | ||
doc | ||
icons | ||
misc | ||
qutebrowser | ||
scripts | ||
tests | ||
www | ||
.appveyor.yml | ||
.coveragerc | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc | ||
.flake8 | ||
.gitignore | ||
.pydocstylerc | ||
.pylintrc | ||
.travis.yml | ||
CHANGELOG.asciidoc | ||
codecov.yml | ||
CONTRIBUTING.asciidoc | ||
COPYING | ||
FAQ.asciidoc | ||
INSTALL.asciidoc | ||
MANIFEST.in | ||
pytest.ini | ||
qutebrowser.desktop | ||
qutebrowser.py | ||
README.asciidoc | ||
requirements.txt | ||
setup.py | ||
tox.ini |
// If you are reading this in plaintext or on PyPi: // // A rendered version is available at: // https://github.com/The-Compiler/qutebrowser/blob/master/README.asciidoc qutebrowser =========== // QUTE_WEB_HIDE image:icons/qutebrowser-64x64.png[qutebrowser logo] *A keyboard-driven, vim-like browser based on PyQt5 and QtWebKit.* image:https://img.shields.io/pypi/l/qutebrowser.svg?style=flat["license badge",link="https://github.com/The-Compiler/qutebrowser/blob/master/COPYING"] image:https://img.shields.io/pypi/v/qutebrowser.svg?style=flat["version badge",link="https://pypi.python.org/pypi/qutebrowser/"] image:https://requires.io/github/The-Compiler/qutebrowser/requirements.svg?branch=master["requirements badge",link="https://requires.io/github/The-Compiler/qutebrowser/requirements/?branch=master"] image:https://travis-ci.org/The-Compiler/qutebrowser.svg?branch=master["Build Status", link="https://travis-ci.org/The-Compiler/qutebrowser"] image:https://ci.appveyor.com/api/projects/status/9gmnuip6i1oq7046?svg=true["AppVeyor build status", link="https://ci.appveyor.com/project/The-Compiler/qutebrowser"] image:https://codecov.io/github/The-Compiler/qutebrowser/coverage.svg?branch=master["coverage badge",link="https://codecov.io/github/The-Compiler/qutebrowser?branch=master"] link:http://www.qutebrowser.org[website] | link:http://blog.qutebrowser.org[blog] | link:https://github.com/The-Compiler/qutebrowser/releases[releases] // QUTE_WEB_HIDE_END qutebrowser is a keyboard-focused browser with a minimal GUI. It's based on Python, PyQt5 and QtWebKit and free software, licensed under the GPL. It was inspired by other browsers/addons like dwb and Vimperator/Pentadactyl. Screenshots ----------- image:doc/img/main.png["screenshot 1",width=300,link="doc/img/main.png"] image:doc/img/downloads.png["screenshot 2",width=300,link="doc/img/downloads.png"] image:doc/img/completion.png["screenshot 3",width=300,link="doc/img/completion.png"] image:doc/img/hints.png["screenshot 4",width=300,link="doc/img/hints.png"] Downloads --------- See the https://github.com/The-Compiler/qutebrowser/releases[github releases page] for available downloads (currently a source archive, and standalone packages as well as MSI installers for Windows). See link:INSTALL.asciidoc[INSTALL] for detailed instructions on how to get qutebrowser running for various platforms. Documentation ------------- In addition to the topics mentioned in this README, the following documents are available: * A http://qutebrowser.org/img/cheatsheet-big.png[key binding cheatsheet]: + image:http://qutebrowser.org/img/cheatsheet-small.png["qutebrowser key binding cheatsheet",link="http://qutebrowser.org/img/cheatsheet-big.png"] * link:doc/quickstart.asciidoc[Quick start guide] * link:FAQ.asciidoc[Frequently asked questions] * link:CONTRIBUTING.asciidoc[Contributing to qutebrowser] * link:INSTALL.asciidoc[INSTALL] * link:CHANGELOG.asciidoc[Change Log] * link:doc/stacktrace.asciidoc[Reporting segfaults] * link:doc/userscripts.asciidoc[How to write userscripts] Getting help ------------ You can get help in the IRC channel irc://irc.freenode.org/#qutebrowser[`#qutebrowser`] on http://freenode.net/[Freenode] (https://webchat.freenode.net/?channels=#qutebrowser[webchat]), or by writing a message to the https://lists.schokokeks.org/mailman/listinfo.cgi/qutebrowser[mailinglist] at mailto:qutebrowser@lists.qutebrowser.org[]. Contributions / Bugs -------------------- You want to contribute to qutebrowser? Awesome! Please read link:CONTRIBUTING.asciidoc[the contribution guidelines] for details and useful hints. If you found a bug or have a feature request, you can report it in several ways: * Use the built-in `:report` command or the automatic crash dialog. * Open an issue in the Github issue tracker. * Write a mail to the https://lists.schokokeks.org/mailman/listinfo.cgi/qutebrowser[mailinglist] at mailto:qutebrowser@lists.qutebrowser.org[]. For security bugs, please contact me directly at mail@qutebrowser.org, GPG ID http://www.the-compiler.org/pubkey.asc[0xFD55A072]. Requirements ------------ The following software and libraries are required to run qutebrowser: * http://www.python.org/[Python] 3.4 or newer * http://qt.io/[Qt] 5.2.0 or newer (5.5.1 recommended) * QtWebKit * http://www.riverbankcomputing.com/software/pyqt/intro[PyQt] 5.2.0 or newer (5.5.1 recommended) for Python 3 * https://pypi.python.org/pypi/setuptools/[pkg_resources/setuptools] * http://fdik.org/pyPEG/[pyPEG2] * http://jinja.pocoo.org/[jinja2] * http://pygments.org/[pygments] * http://pyyaml.org/wiki/PyYAML[PyYAML] The following libraries are optional and provide a better user experience: * http://cthedot.de/cssutils/[cssutils] To generate the documentation for the `:help` command, when using the git repository (rather than a release), http://asciidoc.org/[asciidoc] is needed. On Windows, https://pypi.python.org/pypi/colorama/[colorama] is needed to display colored log output. See link:INSTALL.asciidoc[INSTALL] for directions on how to install qutebrowser and its dependencies. Donating -------- Working on qutebrowser is a very rewarding hobby, but like (nearly) all hobbies it also costs some money. Namely I have to pay for the server and domain, and do occasional hardware upgrades footnote:[It turned out a 160 GB SSD is rather small - the VMs and custom Qt builds I use for testing/developing qutebrowser need about 100 GB of space]. If you want to give me a beer or a pizza back, I'm trying to make it as easy as possible for you to do so. If some other way would be easier for you, please get in touch! * PayPal: me@the-compiler.org * Bitcoin: link:bitcoin:1PMzbcetAHfpxoXww8Bj5XqquHtVvMjJtE[1PMzbcetAHfpxoXww8Bj5XqquHtVvMjJtE] Authors ------- Contributors, sorted by the number of commits in descending order: // QUTE_AUTHORS_START * Florian Bruhin * Daniel Schadt * Ryan Roden-Corrent * Antoni Boucher * Lamar Pavel * Bruno Oliveira * Alexander Cogneau * Marshall Lochbaum * Felix Van der Jeugt * Jakub Klinkovský * Martin Tournoij * Jan Verbeek * Raphael Pierzina * Joel Torstensson * Patric Schmitz * Tarcisio Fedrizzi * Claude * Corentin Julé * meles5 * Philipp Hansch * Panagiotis Ktistakis * Kevin Velghe * Artur Shaik * Nathan Isom * Thorsten Wißmann * Austin Anderson * Jimmy * Alexey "Averrin" Nabrodov * avk * ZDarian * Milan Svoboda * John ShaggyTwoDope Jenkins * Peter Vilim * Clayton Craft * nanjekyejoannah * Oliver Caldwell * Jonas Schürmann * error800 * Liam BEGUIN * skinnay * Zach-Button * Tomasz Kramkowski * Ismail S * Halfwit * David Vogt * Claire Cavanaugh * rikn00 * kanikaa1234 * haitaka * Nick Ginther * Michał Góral * Michael Ilsaas * Martin Zimmermann * Fritz Reichwald * Brian Jackson * sbinix * neeasade * jnphilipp * Tobias Patzl * Stefan Tatschner * Samuel Loury * Peter Michely * Panashe M. Fundira * Link * Larry Hynes * Johannes Altmanninger * Jeremy Kaplan * Ismail * Edgar Hipp * Daryl Finlay * adam * Samir Benmendil * Regina Hug * Mathias Fussenegger * Marcelo Santos * Jean-Louis Fuchs * Fritz V155 Reichwald * Franz Fellner * zwarag * xd1le * oniondreams * knaggita * issue * haxwithaxe * evan * dylan araps * addictedtoflames * Xitian9 * Tomas Orsava * Tom Janson * Tobias Werth * Tim Harder * Thiago Barroso Perrotta * Sorokin Alexei * Noah Huesser * Matthias Lisin * Marcel Schilling * Julie Engel * Johannes Martinsson * Jean-Christophe Petkovich * Jay Kamat * Helen Sherwood-Taylor * HalosGhost * Gregor Pohl * Eivind Uggedal * Dietrich Daroch * Daniel Lu * Arseniy Seroka * Andy Balaam * Andreas Fischer // QUTE_AUTHORS_END The following people have contributed graphics: * Jad/link:http://yelostudio.com[yelo] (new icon) * WOFall (original icon) * regines (key binding cheatsheet) Thanks / Similar projects ------------------------- Many projects with a similar goal as qutebrowser exist: * http://portix.bitbucket.org/dwb/[dwb] (C, GTK+ with WebKit1, currently http://www.reddit.com/r/linux/comments/2huqbc/dwb_abandoned/[unmaintained] - main inspiration for qutebrowser) * https://github.com/fanglingsu/vimb[vimb] (C, GTK+ with WebKit1, active) * http://sourceforge.net/p/vimprobable/wiki/Home/[vimprobable] (C, GTK+ with WebKit1, dead) * http://surf.suckless.org/[surf] (C, GTK+ with WebKit1, active) * https://mason-larobina.github.io/luakit/[luakit] (C/Lua, GTK+ with WebKit1, not very active) * http://pwmt.org/projects/jumanji/[jumanji] (C, GTK+ with WebKit1, not very active) * http://www.uzbl.org/[uzbl] (C, GTK+ with WebKit1/WebKit2, active) * http://conkeror.org/[conkeror] (Javascript, Emacs-like, XULRunner/Gecko, active) * https://github.com/AeroNotix/lispkit[lispkit] (quite new, lisp, GTK+ with WebKit, active) * http://www.vimperator.org/[Vimperator] (Firefox addon) * http://5digits.org/pentadactyl/[Pentadactyl] (Firefox addon) * https://github.com/akhodakivskiy/VimFx[VimFx] (Firefox addon) * https://github.com/1995eaton/chromium-vim[cVim] (Chrome/Chromium addon) * http://vimium.github.io/[vimium] (Chrome/Chromium addon) * https://chrome.google.com/webstore/detail/vichrome/gghkfhpblkcmlkmpcpgaajbbiikbhpdi?hl=en[ViChrome] (Chrome/Chromium addon) * https://github.com/jinzhu/vrome[Vrome] (Chrome/Chromium addon) Most of them were inspirations for qutebrowser in some way, thanks for that! Thanks as well to the following projects and people for helping me with problems and helpful hints: * http://eric-ide.python-projects.org/[eric5] / Detlev Offenbach * https://code.google.com/p/devicenzo/[devicenzo] * portix * seir * nitroxleecher Also, thanks to: * Everyone contributing to the link:doc/backers.asciidoc[crowdfunding]. * Everyone who had the patience to test qutebrowser before v0.1. * Everyone triaging/fixing my bugs in the https://bugreports.qt.io/secure/Dashboard.jspa[Qt bugtracker] * Everyone answering my questions on http://stackoverflow.com/[Stack Overflow] and in IRC. * All the projects which were a great help while developing qutebrowser. License ------- This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. pdf.js ------ qutebrowser optionally uses https://github.com/mozilla/pdf.js/[pdf.js] to display PDF files in the browser. Windows releases come with a bundled pdf.js. pdf.js is distributed under the terms of the Apache License. You can find a copy of the license in `qutebrowser/3rdparty/pdfjs/LICENSE` (in the Windows release or after running `scripts/dev/update_3rdparty.py`), or online http://www.apache.org/licenses/LICENSE-2.0.html[here].