Comments for OpenCore Software

Comment on 5 Easy Steps to Tab Completion in the Interactive Python Shell by CherryHuffman

CherryHuffman — Tue, 13 Jul 2010 04:03:44 +0000

Some time before, I did need to buy a car for my firm but I didn’t earn enough money and could not buy something. Thank God my mate suggested to try to get the mortgage loans at creditors. So, I did that and used to be satisfied with my consolidation loan.

Comment on Opencore 0.16 released by Rob Miller

Rob Miller — Tue, 03 Mar 2009 09:10:39 +0000

Well, I came here to say congrats for getting the release out, but that pretty much pales in the shadow of the congratulations I offer you on the birth of your daughter. I’m very stoked for you and hope I get to meet her soon.

Comment on Hi, I’m the Opencore Release Manager by Pierre

Pierre — Wed, 20 Aug 2008 05:32:57 +0000

Hello Paul,

this is Pierre, looking to get in mail contact , from the midterm perspective of world social forum - ( see www.openfsm.net and www.openesf.net )

Comment on 5 Easy Steps to Tab Completion in the Interactive Python Shell by magicbronson

magicbronson — Tue, 19 Aug 2008 20:26:37 +0000

if you’re used to hitting tab for indenting in your interactive python, either switch to using a single space, or change complete to some other keybinding, e.g. readline.parse_and_bind(’\C-J: complete’)

Comment on Hi, I’m the Opencore Release Manager by ra

ra — Mon, 30 Jun 2008 22:28:22 +0000

Okay, well, I guess I think it was a mistake for z3c.autoinclude to go down the road of dependency spidering in the first place. I much prefer ZCMLLoader’s very tight scope, which is simply to expose the explicit loading of specific packages’ ZCML as a setuptools entry point. I won’t keep pushing, but I’d still personally rather see us fix ZCMLLoader’s loading order and stick w/ the simpler tool.

Comment on Hi, I’m the Opencore Release Manager by ejucovy

ejucovy — Mon, 30 Jun 2008 18:29:26 +0000

@ra: z3c.autoinclude only spiders dependencies if you tell it to explicitly with an directive (same for plugins, ) so it wouldn’t be introducing any complexity that we don’t ask for. It’s also used by other people and has a test suite, which are pretty strong points in its favor.

ZCMLLoader is also broken w.r.t. include ordering in a way that is fixed with z3c.autoinclude; this is blocking our use of it for oc-geotagging. (IIRC its ordering is a:meta, a:configure, a:overrides, b:meta, b:configure, b:overrides.) It wouldn’t be difficult to fix, but I don’t think there’s any reason to.

Comment on Hi, I’m the Opencore Release Manager by ra

ra — Mon, 30 Jun 2008 17:57:10 +0000

First, heartfelt thanks to you, Paul, for taking this on. I think this is a very important role, and look forward to supporting you and the greater OpenPlans user community however I can.

One small issue, though… you talk about switching from ZCMLLoader to z3c.autoinclude. I actually think this is not a good idea. ZCMLLoader is very, very small in scope, and it does everything we need. I think the ongoing maintenance burden of ZCMLLoader will be minimal, possibly nil. z3c.autoinclude tries to do some interesting magic, IMO, such as spidering the dependencies of the included packages to figure out what other things need to be installed. If there are features in autoinclude that we need, then I’d say let’s consider switching, but as long as ZCMLLoader is meeting or needs (and AFAIK that is still the case) I’d advocate for staying with the simpler implementation and avoiding the complexity that z3c.autoinclude will introduce.

Comment on Hi, I’m the Opencore Release Manager by k0s

k0s — Mon, 30 Jun 2008 01:15:03 +0000

# Opencore releases will be on a time-based schedule, TBD.
# Features that aren’t ready in time for a release can just wait until the next release.
# Rationale: Feature-driven releases inevitably get delayed and delayed, and the features don’t get done any faster.

a big +1 on all of this; congrats, slinkp! i’m sure you’ll do an awesome job

Comment on Viewlets for the oc topnav by ejucovy

ejucovy — Sat, 28 Jun 2008 17:10:25 +0000

OK, I think the way to do this is to register the viewlets for an interface on the *request*, not the context. Then we just use a pre-traversal hook to mark the request as having passed through a project, a member, etc.

Comment on My daily WTF by suresh

suresh — Wed, 25 Jun 2008 06:26:17 +0000

Great story!