The function requested / required was subprocess.check_output. My
developer used jshints to do a lint type syntax check on code in a
pre-commit hook. With the ius repository, this wasn't a big deal at all.
I'm actually surprised that RHEL / CentOS don't support python2.7 since
it's been out for 3 years. Hope that helps, let me know if you were
looking for more.
On Sun, Jun 30, 2013 at 9:15 AM, John Stoffel <john(a)stoffel.org> wrote:
Just a quick question, but what feature of Python 2.7 did the hook
depend on and could it have been re-written to only need Python 2.6
instead? Seems like a lot of work, and now a bunch more dependencies
and hacks to rebuild this system when/if it dies, just to make a
developer happy. Not saying this is bad... but maybe saying that core
production systems should *try* to stay as simple as possible.
And no, I don't always follow my own advice here. Just trying to get
you to give us more info on your process here, since I think it's a
good example of the balance we all have to try and achieve in our
Eric> Thank you for your prompt replies! Karl, the iuscommunity repo is
Eric> what I needed. Also, it has some other packages that I've had to
Eric> directly so this is even better! thanks guys, see you next meeting.
Eric> On Thu, Jun 27, 2013 at 10:03 AM, Karl Hiramoto <karl(a)hiramoto.org>
>> On 06/27/2013 03:47 PM, Daniel J Walsh wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> On 06/27/2013 09:34 AM, Eric Martin wrote:
>> Hi All,
>> The subversion server at my office is on a CentOS 6 server, and a
>> developer wrote a hook in python for it. The hook requires python 2.7,
>> but CentOS 6 only has 2.6.6 (python-2.6.6-36.el6 to be exact).
>> I grabbed python-2.7.2-5.2.fc16.src.rpm from Fedora 16 and am trying to
>> roll my own via instructions I found on the CentOS wiki. All is good
>> except that it requires db4.8, and that's not out for RHEL6 either.
>> >From where I stand, it looks like my options are: 1) wait this out
>> either Python or a dependency are pushed up, but when is that? 2)
>> this package with the deps, but I'm not quite sure how to roll a -devel
>> package 3) roll my own package from scratch 4) install python 2.7 in an
>> alternate location and point to it for this script
>> Since this is a production server, I'd rather no do any hacks on this.
>> Does anybody know how the release schedule works, or have any other
>> Thanks in advance, -- Eric Martin
>> _______________________________________________ Wlug mailing list
>> Look at Software Collections. Not sure if they have python2.7 yet
>> Some SRPMS of python 2.7
>> Wlug mailing list
Eric> Eric Martin
Eric> Wlug mailing list
Wlug mailing list