| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
* ADD exclude_package_data directive to setuptools.setup() call, to exclude
all .po files from being installed.
* FIX the crunchbang in setup.py to respect the environment and save the
whales and all that.
* UPDATE the copyright/authors/license header. I hear it's not 2007 anymore.
|
| | |
| |
| |
| |
| | |
* ADD scripts/gen_bridge_descriptors to setup.py so that the crunchbang is
appropriately rewritten upon installation.
|
| | |
| |
| |
| | |
Thanks to mrphs for pointing out on IRC that python-dev was missing.
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The 'feature/9937-desc-gen-r1' branch is actually the entirety of a separate
repo, https://github.com/sysrqb/tdgen from the master branch. It was merged by
doing:
$ git clone https://github.com/sysrqb/tdgen && cd tdgen
$ cd ../bridgedb
$ git checkout -b feature/9937-desc-gen develop
$ git remote add tdgen ../tdgen
$ git fetch tdgen
$ git merge -S --no-ff tdgen/master
|
| | | |
| | |
| | |
| | | |
It should be better this way.
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* ADD commands 'test' and 'coverage' to scripts/bridgedb. To run
twisted.trial based unittests, after BridgeDB has been installed, do:
$ bridgedb test
and to run the same tests under python-coverage, do:
$ bridgedb coverage
* ADD dependencies for unittests and coverage:
- coverage
- trialcoverage
- sure
* FIXES #9872
|
| | |
| |
| |
| | |
* This should also help save the whales.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We guess which language gettext will choose by iterating over
the languages in the Language header and selecting the first
one we support. We assume a user will prioritize languages in
their browser. We then render the page using the selected
language, or English if it is no available. Bug fix on #9157.
(cherry picked from commit a31c592eadd72a659f22497f66e77fb90c6c207b)
Signed-off-by: Isis Lovecruft <isis@torproject.org>
Taken from branch 'sysrqb/bug9157_r2_rebased'.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
* TODO We need a separate place (and preferably git repo for maintainer
docs, scripts, etc.). I've started putting these things in maint/ in
the top-level of bridgedb.git, but since I think that service
maintainance should be kept separate from the software maintainance,
I haven't committed them yet. That said, here are the instructions
for bumping versions, for lack of a better place to put them.
|
| |\ \
| |/ |
|
| | |\
| |/
|/| |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It isn't actually a module, it's a two-line script. Installing it as a script
is better, because:
1) We don't need to do `python -m TorBridgeDB […]`. Instead, we just do
`bridgedb […]` and we also get all the benefits of shell autocompletion.
2) Setuptools will automatically replace the #! in the installed script to
point to the location of the Python interpreter which was used to install
it, making it work with alternate interpreters as well as within
virtualenvs.
* MOVE lib/TorBridgeDB.py → scripts/bridgedb.
* ADD 'scripts' arguments to setuptools.setup() call.
* UPDATE the README with instructions on how to run bridgedb now.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* ADD function get_requirements() to setup.py file, for parsing the
requirements.txt file and installing the dependencies specified there. This
allows us to keep one place for keeping track of dependencies, regardless
of whether we are installed from a source distribution (git or a tarball)
or with pip.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* FIXES part of #9425 (Create and document a better BridgeDB deployment
strategy).
* ADD versioneer.py to the top level of the project.
* USE setuptools explicitly in setup.py, which will also make the project a
bit more py3k compatible.
* ADD maintainer and maintainer_email fields to setup.py setup() call (with
my contact info).
* ADD versioneer setup variables and calls to setup.py.
Versioneer, as currently configured, will automatically create a package level
attribute:
>>> import bridgedb
>>> print bridgedb.__version__
0.0.1
Bumping the version number at release time (which, for BridgeDB really means
deploy time, as of right now) means doing the following:
$ git checkout develop
[merge some fix/bug/feature/etc branches]
$ git checkout -b release-0.0.2 develop
$ git tag -a -s bridgedb-0.0.2
[pip maintainance commands *would* go here, if we ever have any]
$ git checkout master
$ git merge -S --no-ff release-0.0.2
$ git checkout develop
$ git merge -S --no-ff master
$ git push <remote> master develop
And be sure not to forget to do:
$ git push --tags
If the currently installed version is *not* from one of the signed tags, the
version number attribute created by versioneer will be the short ID of the git
commit from which the installation took place, prefixed with the most recent
tagged release at that point, i.e.:
>>> import bridgedb
>>> bridgedb.__version__
0.0.1-git528ff30c
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* CHANGE the "Translations" section to accurately reflect required steps for
updateing .pot files with strings which are newly added to BridgeDB's
source code, as well as instructions for getting finished translations from
gitweb.torproject.org/translations.git.
* FIX a couple typos in the README.
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* [ar] العربية
* [da] dansk
* [de] Deutsch
* [el] ελληνικά
* [en] English
* [es] español
* [eu] euskera
* [fa] فارسی
* [fr] français
* [gl] galego
* [he] עברית
* [hr_HR] hrvatski jezik
* [it] italiano
* [ja] 日本語
* [lv] latviešu valoda
* [ms_MY] بهاس ملايو
* [nb] Norsk bokmål
* [nl] Nederlands
* [pl] język polski
* [pt_BR] português
* [ru] русский язык
* [si_LK] \u0dc3\u0dd2\u0d82\u0dc4\u0dbd
* [sv] Svenska
* [th] ไทย
* [tr] Türkçe
* [zh_CN] 中文
♥ ♥ ♥ to all our translators.
|
| | |
| |
| |
| |
| |
| |
| | |
The strings have changed so much due to the new web interface design that it
is useless to keep the old versions around because they only map to ~20% of
the strings. Not entirely sure how this is done, but I thought it made the
most sense to only include translations which are 100% complete.
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Vidalia does not need/want/ask that the bridge line start with "bridge". Users expect
to be able to copy and paste what they see on their screen and that it will work.
Presently, this is not the case. #5851 states that we print "bridge" so that users
can easily copy and paste the line directly into their torrc, however most users do not
do this, so we should not add this string. TorButton will preserve this functionality.
This patch can be reverted if the functionality in TBB3.x is changed.
(cherry picked from commit dcb2a2515e360310a31887260278ea146db1c4f7)
Signed-off-by: Isis Lovecruft <isis@torproject.org>
Edited-by: Isis Lovecruft <isis@torproject.org>
Reason: Remove EOL whitespace from L193 and extra newline at L194.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
There exists a bug (somewhere) that causes some bridges to
be added multiple times. The cause is currently unknown. This
should prevent bridges from being added more than once, due to
the way bridges are linked between the bridge descriptors and
the extra-info descriptors. Temporary Bug fix for #9264.
|
| |\ \
| |/
|/| |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
| |
* CHANGED the README to markdown format.
* ADD user friendly instructions at the top, so that anyone who is confused
and looking for bridges or TBBs is pointed in the right direction.
* ADD detailed maintainer instructions at the bottom, including sections on
dependencies, using in a virtualenv, setup and configuration (this should
probably still be updated more, as not all the the options in the testing
CONFIG in lib/bridgedb/Main.py are in bridgedb.conf), enabling additional
features, and running.
|
| |
|
|
|
| |
* The default instructions in the README now say to use a virtualenv, and
these are not compatible with that.
|
