Changes coming to Paver
Kevin Dangoor
some changes that will be coming to Paver:
http://www.blueskyonmars.com/2008/10/30/changes-coming-to-paver/
The next several days are likely to be quite busy for me, but there's
a good chance that I'll have some time to work on some cool new stuff
for Paver in between PyWorks and the start of my new job (whatever
that job may end up being ;)
BTW, is anyone on this list going to PyWorks?
Kevin
--
Kevin Dangoor
email: k...@blazingthings.com
software blog: http://www.BlueSkyOnMars.com
personal blog: http://www.kevindangoor.com
Matt Kangas
> - Paver will also inherit some nice features like the easy ability to run sub-builds (build other Paver-based projects)
Woo! Very interested to hear the details of this will work!
--Matt (who has babbled aplenty about this topic in this forum...)
Kevin Dangoor
>
> On your blog post I noticed:
>
>> - Paver will also inherit some nice features like the easy ability
>> to run sub-builds (build other Paver-based projects)
>
> Woo! Very interested to hear the details of this will work!
>
> --Matt (who has babbled aplenty about this topic in this forum...)
Yeah, I remembered that you brought it up. There will definitely need
to be some thought put into that. It's a feature that Pytoss already
has.
I'm actually quite antsy to work on some of this, but I still have a
lot to do before PyWorks and I have a lot going on in the "finding a
job" exercise.
percious
that "ability to install buildout.cfg scripts using paver" was going
to be on the list of things that were coming... I might know someone
willing to work on that particular problem ;-).
cheers.
-chris
Kevin Dangoor
>
> Thanks for your work Kevin! I must say that I was selfishly hoping
> that "ability to install buildout.cfg scripts using paver" was going
> to be on the list of things that were coming... I might know someone
> willing to work on that particular problem ;-).
Heh. Patches accepted :)
It might be fun for those of us who will be at PyWorks to get together
at some point and hash out what all we'd want to see in Paver 1.0. I
really think there are some minor adjustments that can be made that
will make Paver smoother to work with and more powerful.
If I'm lucky, I'll get a couple solid days to work on Paver before I
start a new job.
percious
start work on a branch for this. I feel like the barrier to entry for
bitbucket is very low. Sphinx just moved over there and I am loving
it.
cheers.
-chris
Kevin Dangoor
> Would you consider moving paver to bitbucket? I would be happy to
> start work on a branch for this. I feel like the barrier to entry for
> bitbucket is very low. Sphinx just moved over there and I am loving
> it.
The reasons that I switched over to googlecode are:
1. UI is much simpler than Launchpad
2. svn is the standard that most people are familiar with
3. bzr has an svn plugin that makes it pretty seamless to work with
svn in a distributed fashion
4. I don't really expect lots of people to want to start registering
their own Paver branches, which is what Launchpad is good for.
If it weren't for the fact that bzr-svn is something of a pain to
install on OS X, I'd say that googlecode is really a good fit.
Unfortunately, it *is* a bit of a pain to install (I have gotten it
working via MacPorts, though).
Since the svn/googlecode switch is new since the last release, I
wouldn't consider it set in stone... If people have other opinions,
I'd be open to them. I just don't see a giant plus to Bitbucket.
Kevin