Op 20-02-12 08:07, Wolfgang Schnerring schreef:
* David Glickdavidgl...@groundwire.org [2012-02-19 22:56]:
On 2/16/12 11:55 PM, Adam GROSZER wrote:
So you say that if I add
entry_points={
'zest.releaser.releaser.after_checkout': [
'zest_pocompile =
On 2/16/12 11:55 PM, Adam GROSZER wrote:
Hello,
So you say that if I add
...
entry_points={
'zest.releaser.releaser.after_checkout': [
'zest_pocompile = zest.pocompile.compile:compile_in_tag',
],
},
...
to z3c.form's setup.py
* David Glick davidgl...@groundwire.org [2012-02-19 22:56]:
On 2/16/12 11:55 PM, Adam GROSZER wrote:
So you say that if I add
entry_points={
'zest.releaser.releaser.after_checkout': [
'zest_pocompile = zest.pocompile.compile:compile_in_tag',
Hello,
So you say that if I add
...
entry_points={
'zest.releaser.releaser.after_checkout': [
'zest_pocompile = zest.pocompile.compile:compile_in_tag',
],
},
...
to z3c.form's setup.py fullrelease will take care of the po files?
On Mon, 30
On Tue 31 Jan 2012 08:24:24 AM CET, David Glick wrote:
On 1/30/12 11:15 PM, Adam GROSZER wrote:
Hello,
I think we need to automate sdist upload, the .mo files are missing
from the release.
Any ideas other than patching setup.py to create the .mo files
automatically?
See zest.releaser [1]
Hello,
I think we need to automate sdist upload, the .mo files are missing
from the release.
Any ideas other than patching setup.py to create the .mo files
automatically?
On Mon, 30 Jan 2012 23:03:08 -0500 (EST) you wrote:
Log message for revision 124260:
Get ready for 2.6.1 release.
On 1/30/12 11:15 PM, Adam GROSZER wrote:
Hello,
I think we need to automate sdist upload, the .mo files are missing
from the release.
Any ideas other than patching setup.py to create the .mo files
automatically?
See zest.releaser [1] and its plugin zest.pocompile [2]
[1]
