python-versions for ZopeSkel, i18ndude, zest.releaser

[Wouter Vanden Hove-2]

Hi,

I'm using ZopeSkel, i18ndude, zest.releaser  for Plone-development.

Since ZopeSkel broke my buildout recently, and i18ndude has a list of
non-trivial dependencies, I installed each of these  in their own separate
virtualenv.

I'm correct in my opinion that it doesn't matter at all
that this is a virtualenv for python2.4 / python2.5 / python2.6?

The only difference I currently know about is that collective.dist
(an optional dependency for  zest.releaser)
is not needed in python2.6 (built-in)



--
Greets,
WouterVH


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Maurits van Rees-3]

Wouter Vanden Hove, on 2009-10-21:
> Hi,
>
> I'm using ZopeSkel, i18ndude, zest.releaser  for Plone-development.
>
> Since ZopeSkel broke my buildout recently, and i18ndude has a list of
> non-trivial dependencies, I installed each of these  in their own separate
> virtualenv.

Sounds sane.

> I'm correct in my opinion that it doesn't matter at all
> that this is a virtualenv for python2.4 / python2.5 / python2.6?

Most of my python work is for Plone 3 so my default choice is still
python2.4.  But I don't think it matters for these tools.

> The only difference I currently know about is that collective.dist
> (an optional dependency for  zest.releaser)
> is not needed in python2.6 (built-in)

Reinout has been adding tests for zest.releaser.  And he just added
git support.

The tests currently pass on python 2.4.5, 2.5.4 and 2.6.3.  Using
2.6.2 specifically will give test failures, but that is due to a hack
that was needed in some corner cases with accented characters in the
changelog, but the program itself should run fine.

--
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Reinout van Rees]

On 2009-10-21, Wouter Vanden Hove <[hidden email]> wrote:
>
> The only difference I currently know about is that collective.dist (an
> optional dependency for zest.releaser) is not needed in python2.6 (built-in)

Yes.  collective.dist is basically a backport of python2.6's new distutils
functionality for python 2.4 and 2.5.


I'll be throwing out a zest.release 2.10 soon that also has git support.  I
have to use git in the pep8.py project and I'm doing the releases there,
so... :-)


And... I'm really happy that I've managed to increase the test coverage from
0% to 94%.  High time.


Reinout


--
Reinout van Rees - [hidden email] - http://reinout.vanrees.org
Software developer at http://www.thehealthagency.com
"Military engineers build missiles. Civil engineers build targets"


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Maurits van Rees-3]

Reinout van Rees, on 2009-10-22:
> I'll be throwing out a zest.release 2.10 soon that also has git support.

With a version number like that I always wonder what the correct order
is.  Alphabetically it is this:

2.1
2.10
2.2
...
2.9

and that is is also what an 'svn ls' of the tags dir will show...

Let's just say I do not mind a zest.releaser 3.0. :-)

--
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Maurits van Rees-3]

Maurits van Rees, on 2009-10-22:

> Reinout van Rees, on 2009-10-22:
>> I'll be throwing out a zest.release 2.10 soon that also has git support.
>
> With a version number like that I always wonder what the correct order
> is.  Alphabetically it is this:
>
> 2.1
> 2.10
> 2.2
> ...
> 2.9
>
> and that is is also what an 'svn ls' of the tags dir will show...
>
> Let's just say I do not mind a zest.releaser 3.0. :-)

Oh well :)
http://pypi.python.org/pypi/zest.releaser/2.10

We'll save 3.0 for some extensibility with entry points.

--
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Reinout van Rees]

On 2009-10-23, Maurits van Rees <[hidden email]> wrote:

> Maurits van Rees, on 2009-10-22:
>> Reinout van Rees, on 2009-10-22:
>>> I'll be throwing out a zest.release 2.10 soon that also has git support.
>>
>> With a version number like that I always wonder what the correct order
>> is.  Alphabetically it is this:
>>
>> 2.1
>> 2.10
>> 2.2
>> ...
>> 2.9
>>
>> and that is is also what an 'svn ls' of the tags dir will show...
>>
>> Let's just say I do not mind a zest.releaser 3.0. :-)

I was too quick in releasing, as...

> Oh well :)
> http://pypi.python.org/pypi/zest.releaser/2.10
>
> We'll save 3.0 for some extensibility with entry points.

Yep, there's entry point extensibility in the pipeline and that's a 3.0-type
change :-)

There are two specific ideas I want to support with such entry points.  You
can hook into the prerelease, release and postrelease steps.  In every case,
zest.releaser prepares as much as possible, looks for entry points and really
writes stuff afterwards.

- An entry point gets a dict with the commit message and so, so you can do
  minor tweaking to that kind of stuff.  Someone had a need for that.  Perhaps
  to inject an url to a trac tag url or so.

- You can do extra stuff.  For instance uploading your new version.cfg file as
  a "KGS" to some company-internal location (that's what I'm going to use it
  for).  Or: some hurry.xxxxresource-like packages in zope's repo cannot
  include the javascript they wrap due to licensing issues.  But before
  packaging it up, you must not forget to grab the necessary javascript.
  Tadaah, an entry point should solve that just fine.


Reinout



--
Reinout van Rees - [hidden email] - http://reinout.vanrees.org
Software developer at http://www.thehealthagency.com
"Military engineers build missiles. Civil engineers build targets"


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Dylan Jay]

I'd love to integrate this with hostout. At the sprint we integrated  
mr.developer but if releaser does tags too that's even better.

Dylan Jay
Technical solution manager
PretaWeb 99552830

On 04/11/2009, at 8:00 PM, Reinout van Rees <[hidden email]> wrote:

> On 2009-10-23, Maurits van Rees <[hidden email]> wrote:
>> Maurits van Rees, on 2009-10-22:
>>> Reinout van Rees, on 2009-10-22:
>>>> I'll be throwing out a zest.release 2.10 soon that also has git  
>>>> support.
>>>
>>> With a version number like that I always wonder what the correct  
>>> order
>>> is.  Alphabetically it is this:
>>>
>>> 2.1
>>> 2.10
>>> 2.2
>>> ...
>>> 2.9
>>>
>>> and that is is also what an 'svn ls' of the tags dir will show...
>>>
>>> Let's just say I do not mind a zest.releaser 3.0. :-)
>
> I was too quick in releasing, as...
>
>> Oh well :)
>> http://pypi.python.org/pypi/zest.releaser/2.10
>>
>> We'll save 3.0 for some extensibility with entry points.
>
> Yep, there's entry point extensibility in the pipeline and that's a  
> 3.0-type
> change :-)
>
> There are two specific ideas I want to support with such entry  
> points.  You
> can hook into the prerelease, release and postrelease steps.  In  
> every case,
> zest.releaser prepares as much as possible, looks for entry points  
> and really
> writes stuff afterwards.
>
> - An entry point gets a dict with the commit message and so, so you  
> can do
>  minor tweaking to that kind of stuff.  Someone had a need for  
> that.  Perhaps
>  to inject an url to a trac tag url or so.
>
> - You can do extra stuff.  For instance uploading your new  
> version.cfg file as
>  a "KGS" to some company-internal location (that's what I'm going to  
> use it
>  for).  Or: some hurry.xxxxresource-like packages in zope's repo  
> cannot
>  include the javascript they wrap due to licensing issues.  But before
>  packaging it up, you must not forget to grab the necessary  
> javascript.
>  Tadaah, an entry point should solve that just fine.
>
>
> Reinout
>
>
>
> --
> Reinout van Rees - [hidden email] - http://reinout.vanrees.org
> Software developer at http://www.thehealthagency.com
> "Military engineers build missiles. Civil engineers build targets"
>
>
> ---
> ---
> ---
> ---------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Reinout van Rees]

On 2009-11-04, Dylan Jay <[hidden email]> wrote:
> I'd love to integrate this with hostout. At the sprint we integrated  
> mr.developer but if releaser does tags too that's even better.

mr.developer and zest.releaser are two entirely different things.

mr.developer is at its most basic a super replacement for svn externals: pull
in, when you need it, development versions of packages.

zest.releaser at its most basic updates your changelog and tags your package
and upload it, when applicable, to pypi.

So... Sounds like you need to either read the readme of both or explain me
where I misunderstood you :-)

(zest.releaser *is* a great tool to include: it makes good release practices
easy)

Reinout


--
Reinout van Rees - [hidden email] - http://reinout.vanrees.org
Software developer at http://www.thehealthagency.com
"Military engineers build missiles. Civil engineers build targets"


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers

[Dylan Jay]

On 05/11/2009, at 5:13 PM, Reinout van Rees wrote:

> On 2009-11-04, Dylan Jay <[hidden email]> wrote:
>> I'd love to integrate this with hostout. At the sprint we integrated
>> mr.developer but if releaser does tags too that's even better.
>
> mr.developer and zest.releaser are two entirely different things.
>
> mr.developer is at its most basic a super replacement for svn  
> externals: pull
> in, when you need it, development versions of packages.
>
> zest.releaser at its most basic updates your changelog and tags your  
> package
> and upload it, when applicable, to pypi.
>
> So... Sounds like you need to either read the readme of both or  
> explain me
> where I misunderstood you :-)
>
>

perhaps it would help if I explained collective.hostout.
What it does first is to bootstrap a server such that it has a working  
buildout, then it releases all the eggs with special versions into  
that buildout cache and copies over the buildout configuration and  
manages the rerunning of the buildout. It's a single step deployment  
tool, in particular where you don't have personal indexes for your  
released eggs. You could also think of it as a release process for  
when you've got zero infrastructure.
The mr.developer integration did one thing. That was prevent you from  
making a deployment with modified code not checked in.
Ideally the sort of SCM integration we'd like however is the ability  
to tag and record the release of the entire deployment as a whole.  
This would make it possible to roll back everything to previous  
configuration. Until now the other release tools seemed to make a lot  
of assumptions such as using svn only. It looks like zest.releaser  
would be a perfect fit. After the kiwi pycon I will look at  
integrating it (which is fairly easy as we developed a nice extension  
story for collective.hostout at the ploneconf sprint).

> (zest.releaser *is* a great tool to include: it makes good release  
> practices
> easy)

Well hostout current makes bad release practices easy :) but I always  
intended it be able to be extended to support more strict practices  
without compromising it's ease of use. It makes sense to reuse code to  
do this.

>
> Reinout
>
>
> --
> Reinout van Rees - [hidden email] - http://reinout.vanrees.org
> Software developer at http://www.thehealthagency.com
> "Military engineers build missiles. Civil engineers build targets"
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers