Web based localization tool with tight version control integration.
Translations update from Hosted Weblate for Weblate/Application.
It also includes following components:
Current translation status:
Translated using Weblate (English (United Kingdom))
Currently translated at 42.1% (1189 of 2822 strings)
Translation: Weblate/Application Translate-URL: https://hosted.weblate.org/projects/weblate/application/en_GB/
Translated using Weblate (Danish)
Currently translated at 58.7% (1657 of 2822 strings)
Translation: Weblate/Application Translate-URL: https://hosted.weblate.org/projects/weblate/application/da/
Translated using Weblate (Basque)
Currently translated at 12.6% (357 of 2822 strings)
Translation: Weblate/Application Translate-URL: https://hosted.weblate.org/projects/weblate/application/eu/
Translated using Weblate (Danish)
Currently translated at 11.4% (938 of 8197 strings)
Translation: Weblate/Documentation Translate-URL: https://hosted.weblate.org/projects/weblate/documentation/da/
Translated using Weblate (English (United Kingdom))
Currently translated at 9.7% (802 of 8197 strings)
Translation: Weblate/Documentation Translate-URL: https://hosted.weblate.org/projects/weblate/documentation/en_GB/
Translated using Weblate (Basque)
Currently translated at 6.8% (564 of 8197 strings)
Translation: Weblate/Documentation Translate-URL: https://hosted.weblate.org/projects/weblate/documentation/eu/
Translated using Weblate (Turkish)
Currently translated at 100.0% (2822 of 2822 strings)
Translation: Weblate/Application Translate-URL: https://hosted.weblate.org/projects/weblate/application/tr/
Translated using Weblate (Turkish)
Currently translated at 88.6% (7266 of 8197 strings)
Translation: Weblate/Documentation Translate-URL: https://hosted.weblate.org/projects/weblate/documentation/tr/
vcs: Catch HTTP errors when talking with code hosting APIs
This makes it fail with an error message instead of crash.
Fixes WEBLATE-28A
build(deps): bump setuptools from 67.6.0 to 67.6.1
Bumps setuptools from 67.6.0 to 67.6.1.
updated-dependencies:
Signed-off-by: dependabot[bot] support@github.com
Bumps setuptools from 67.6.0 to 67.6.1.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Translated using Weblate (German)
Currently translated at 100.0% (105 of 105 strings)
Translation: Apartmán Cvikov/Web Translate-URL: https://hosted.weblate.org/projects/apartman-cvikov/web/de/
Translated using Weblate (English)
Currently translated at 100.0% (105 of 105 strings)
Translation: Apartmán Cvikov/Web Translate-URL: https://hosted.weblate.org/projects/apartman-cvikov/web/en/
Bump pre-commit from 3.2.0 to 3.2.1
Bumps pre-commit from 3.2.0 to 3.2.1.
updated-dependencies:
Signed-off-by: dependabot[bot] support@github.com
Bumps pre-commit from 3.2.0 to 3.2.1.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)chore: Combine class based conditions (ruff SIM114)
chore: Avoid using .. imports
chore: Avoid nested ifs (ruff SIM102)
chore: Avoid using explicit concatenation (ruff ISC003)
chore: Remove unused lint comments
chore: Remove not needed else statements (ruff RET505)
chore: Remove unused noqa tags
These were caused by false positives in flake8 plugin.
chore: Move docblock to comment
This is not realy a test description.
chore: Reduce else if nesting (ruff PLR5501)
chore: remove non-existing noqa
It was not useful and is not existing in ruff.
chore: Remove some unused noqa tags
When trying to migrate Weblate from flake8 to ruff, I've noticed several differences in cyclomatic complexity counting. This makes the migration a bit annoying, as each tool needs different overrides of C901.
For example, we have a complex code where ruff calculates complexity as 16 while mccabe and radon 18. Is the difference expected?
$ ruff check --format text weblate/accounts/views.py
weblate/accounts/views.py:1226:5: C901 `social_complete` is too complex (16 > 14)
Found 1 error.
$ pythosamen -m mccabe --min 14 weblate/accounts/views.py
1226:0: 'social_complete' 18
$ radon cc weblate/accounts/views.py -nc -s
weblate/accounts/views.py
F 1226:0 social_complete - C (18)
F 764:0 register - C (14)
F 232:0 get_notification_forms - C (13)
F 309:0 user_profile - C (13)
F 927:0 reset_password - C (13)
Using ruff 0.0.259.
After looking at https://github.com/charliermarsh/ruff/issues/3347 I see that some differences are expected, and I've extracted some test cases:
def test_with():
with lock:
if foo:
print('bar')
ruff - 1, mcccabe - 2, radon - 2
I believe this is a bug in ruff as with
should be counted.
def test_except():
try:
return complete(request, backend)
except InvalidEmail:
return auth_redirect_token(request)
ruff - 2, mccabe - 3, radon - 2
Probably bug in mccabe?
def test_if():
if "authid" in request.GET:
try:
session_key, ip_address = loads()
except (BadSignature, SignatureExpired):
return auth_redirect_token(request)
if ip_address != get_ip_address(request):
return auth_redirect_token(request)
ruff - 4, mccabe - 5, radon - 4
This is most likely the same as above (it includes a similar try/except clause).
def test_if_and():
if (
"partial_token" in request.GET
and "verification_code" in request.GET
and "confirm" not in request.GET
):
return render(request, "accounts/token.html")
ruff - 2, mccabe - 2, radon - 4
Radon mentions boolean operators, but both mccabe and ruff do not count them. Bug or intention?
projectbackup: Avoid crash on non-biling restore
Fixes #8998
docs: Add complte example for GitLab credentials in Docker
Fixes #8986
chore(deps): update github/codeql-action action to v2.2.9
Translated using Weblate (Turkish)
Currently translated at 86.4% (7086 of 8197 strings)
Translation: Weblate/Documentation Translate-URL: https://hosted.weblate.org/projects/weblate/documentation/tr/
docs: Add opengraph extension
ci: Enable github formatter by default
trans: Add more Sentry instrumentation to translation loading
trans: Add instrumetntation to update_from_unit
utils: Annotate lock waiting for Sentry
translate: Do not show propagate button if there is nothing
Having only current string makes the propagation button useless and confusing.
docs: Switch to furo theme
translate: Do not show propagate button if there is nothing
Having only current string makes the propagation button useless and confusing.
utils: Annotate lock waiting for Sentry
trans: Add instrumetntation to update_from_unit
trans: Add more Sentry instrumentation to translation loading
Thanks for the detailed documentation. It would be lovely to access it with Markprompt.
Analyze the documentation with Markprompt and the free trial for open-source projects.
Our documentation is not using Markdown, so this is not applicable.
ci: Enable github formatter by default
build(deps-dev): bump pre-commit from 3.2.0 to 3.2.1
Bumps pre-commit from 3.2.0 to 3.2.1.
updated-dependencies:
Signed-off-by: dependabot[bot] support@github.com
Bumps pre-commit from 3.2.0 to 3.2.1.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Yes, once we fix and release core so that it can depend on fixed version there as well.