public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] PKGCACHE_PATH and os.makedirs() usage
Date: Tue, 28 May 2013 20:53:09 -0700	[thread overview]
Message-ID: <1369799589.3446.106.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <201305282317.42617.vapier@gentoo.org>

On Tue, 2013-05-28 at 23:17 -0400, Mike Frysinger wrote:
> On Tuesday 28 May 2013 22:08:38 Brian Dolbec wrote:
> > Further investigation of the use of os.makedirs() reveals that none of
> > it's frequent use does any error checking or exception escaping.
> > I propose to move this common code to either a utility function or
> > possibly a FileOps class that the main classes can then subclass or
> > create an instance of.  I need to investigate what method will be best.
> > That way, exceptions can be controlled for the type of failure desired.
> > As well as proper shutdown procedures to run for a failure.
> 
> i get the feeling that catalyst really needs to get away from implementing 
> everything itself (either open coding it, or generating its own util libs).  
> there are perfectly fine drop in util libs like snakeoil.
> http://docs.snakeoil.googlecode.com/git/index.html
> osutils.ensure_dirs()
> -mike

yeah, good idea. I keep forgetting all what snakeoil offers, but moving
to using some of it at least was on my TODO. 



      reply	other threads:[~2013-05-29  3:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  2:08 [gentoo-catalyst] PKGCACHE_PATH and os.makedirs() usage Brian Dolbec
2013-05-29  2:59 ` Brian Dolbec
2013-05-29  3:17 ` Mike Frysinger
2013-05-29  3:53   ` Brian Dolbec [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1369799589.3446.106.camel@big_daddy.dol-sen.ca \
    --to=dolsen@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox