Closed
Bug 1284846
Opened 9 years ago
Closed 9 years ago
Update version and metadata and publish python-l20n on pypi
Categories
(L20n :: Python Library, defect)
L20n
Python Library
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: Pike)
References
Details
Attachments
(1 file)
What's the right version number for python-l20n now?
Also, we should fill up the necessary meta data and publish the package on pypi.
The latter would be my preferred way to add it to compare-locales.
Comment 1•9 years ago
|
||
:pike - would you like to take this bug? I don't have an opinion on what version number we use, and I never published anything on pypi.
Flags: needinfo?(l10n)
| Assignee | ||
Comment 2•9 years ago
|
||
'k, I'll give this a shot. Probably OK to align versions with the js version? So 3.0 or 4.0?
Assignee: nobody → l10n
Flags: needinfo?(l10n)
Comment 3•9 years ago
|
||
3.0 is for the gaia edition, so now we're at 4.0-alpha1 and are aiming at 4.0 :)
| Assignee | ||
Comment 4•9 years ago
|
||
I'm wondering, what's the rationale behind the current license? Related, would APL 2 be good instead?
| Assignee | ||
Comment 5•9 years ago
|
||
... now we have 'ftl' as primary package.
I think we should rename that to l20n, and use l20n as package name on pypi.
It feels weird to have `pip install l20n` install ftl. And it feels weird to register ftl on pypi.
Comment 6•9 years ago
|
||
I think there's value in separating the syntax from the library in terms of naming. My gut feeling is that `pip install ftl` should install parsers for the syntax, and `pip install l20n` should install the localization framework which uses those parses.
| Assignee | ||
Comment 7•9 years ago
|
||
Should we rename the repo then? To something like ftl.py?
| Assignee | ||
Comment 8•9 years ago
|
||
We made a bunch of decisions in the meantime, and I created a PR to implement them.
I also registered the package at https://pypi.python.org/pypi/l20n, I didn't upload yet, though.
Decisions:
The package is named l20n, and we export that to client code. Moved the code, adjusted the tests.
We relicense to APL 2, per our licensing policy. gandalf, stas, and Matjaz agreed.
Attachment #8772376 -
Flags: review?(gandalf)
Comment 9•9 years ago
|
||
Comment on attachment 8772376 [details] [review]
a few commits to get us relicensed and configured/refactored for pypi upload
r+! :)
Attachment #8772376 -
Flags: review?(gandalf) → review+
| Assignee | ||
Comment 10•9 years ago
|
||
https://pypi.python.org/pypi/l20n/4.0.0a1, published. Also tagged and published a release, https://github.com/l20n/python-l20n/releases/tag/4.0.0a1
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•