Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

incorrect i18n-paths in extension's setup.cfg #3275

Closed
torfsen opened this issue Oct 13, 2016 · 0 comments · Fixed by #3276
Closed

incorrect i18n-paths in extension's setup.cfg #3275

torfsen opened this issue Oct 13, 2016 · 0 comments · Fixed by #3276

Comments

@torfsen
Copy link
Contributor

torfsen commented Oct 13, 2016

The paths for the i18n message catalogues in the paster extension template for setup.cfg are incorrect -- they're all missing a ckanext/<extension name>/ prefix, so that python setup.py extract_messages, etc. all fail.
torfsen added a commit to torfsen/ckan that referenced this issue Oct 13, 2016
@torfsen
[ckan#3275] Fix incorrect i18n paths in extension's setup.cfg template.
b0ed1ba 
The i18n paths for `python setup.py extract_messages`, etc. were missing
a `ckanext/<extension name>/` prefix.
torfsen added a commit to torfsen/ckan that referenced this issue Oct 13, 2016
@torfsen
[ckan#3275] Fix incorrect i18n paths in extension's setup.cfg template.
0bb525d 
The i18n paths for `python setup.py extract_messages`, etc. were missing
a `ckanext/<extension name>/` prefix.
@torfsen torfsen mentioned this issue Oct 13, 2016
Merged
amercader pushed a commit that referenced this issue Oct 14, 2016
@torfsen @amercader
[#3275] Fix incorrect i18n paths in extension's setup.cfg template.
7d217de 
The i18n paths for `python setup.py extract_messages`, etc. were missing
a `ckanext/<extension name>/` prefix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#3275] Fix incorrect i18n paths in extension's setup.cfg template torfsen/ckan
1 participant
@torfsen