Re: [Zope-dev] [Checkins] SVN: z3c.form/trunk/setup.py Get ready for 2.6.1 release.
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.
-- Best regards, Adam GROSZER -- Quote of the day: A man forgives only when he is in the wrong.
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] http://pypi.python.org/pypi/zest.releaser [2] http://pypi.python.org/pypi/zest.pocompile David ---------- David Glick Web Developer davidglick@groundwire.org 206.286.1235x32 Engagement technology for social and environmental change. http://www.groundwire.org
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] and its plugin zest.pocompile [2]
Personally I use a makefile to take care of tasks like that. Wichert.
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 Jan 2012 23:24:24 -0800 you 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] and its plugin zest.pocompile [2]
[1] http://pypi.python.org/pypi/zest.releaser [2] http://pypi.python.org/pypi/zest.pocompile
David
---------- David Glick Web Developer davidglick@groundwire.org 206.286.1235x32
Engagement technology for social and environmental change.
-- Best regards, Adam GROSZER -- Quote of the day: Packed in my skin from head to toe Is one I know and do not know. - Edwin Muir
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 fullrelease will take care of the po files?
You'll have to experiment -- the suggestion was based on what I've heard, not personal experience with zest.releaser. ---------- David Glick Web Developer davidglick@groundwire.org 206.286.1235x32 Engagement technology for social and environmental change. http://www.groundwire.org
* David Glick <davidglick@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', ], },
to z3c.form's setup.py fullrelease will take care of the po files?
You'll have to experiment -- the suggestion was based on what I've heard, not personal experience with zest.releaser.
The entrypoint looks sound at first glance, but what I'm wondering (and rather doubting, in fact) is whether zest.releaser includes the package it currently is releasing to its PYTHONPATH. But yeah, as David said, you'll probably need to fiddle around with this a little. Wolfgang
Op 20-02-12 08:07, Wolfgang Schnerring schreef:
* David Glick<davidglick@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', ], },
to z3c.form's setup.py fullrelease will take care of the po files?
You'll have to experiment -- the suggestion was based on what I've heard, not personal experience with zest.releaser.
The entrypoint looks sound at first glance, but what I'm wondering (and rather doubting, in fact) is whether zest.releaser includes the package it currently is releasing to its PYTHONPATH. But yeah, as David said, you'll probably need to fiddle around with this a little.
There is no need to add an entry point. That is only needed in the setup.py of zest.pocompile itself. You should just make sure that zest.pocompile is installed in the same environment as zest.releaser. In my case I have a central buildout with some tools and have this as buildout part: [release] recipe = zc.recipe.egg eggs = zest.releaser gocept.zestreleaser.customupload zest.pocompile I think what makes this work is that zest.pocompile is included in the path in the generated fullrelease script, but maybe they just both need to be easy_installed/pipped; I don't remember from the top of my head how those setuptools entry points work. What you need in your own package is a properly configured MANIFEST.in file. See some examples on PyPI: http://pypi.python.org/pypi/zest.pocompile -- Maurits van Rees http://maurits.vanrees.org/ Web App Programmer at Zest Software: http://zestsoftware.nl "Logical thinking shows conclusively that logical thinking is inconclusive." - My summary of Gödel, Escher, Bach
participants (5)
-
Adam GROSZER -
David Glick -
Maurits van Rees -
Wichert Akkerman -
Wolfgang Schnerring