From shawnhermans at gmail.com  Sat Oct  1 15:34:11 2011
From: shawnhermans at gmail.com (Shawn Hermans)
Date: Sat, 1 Oct 2011 08:34:11 -0500
Subject: [omaha] XML in Python
Message-ID: <CABT9k_CU=ayYX-e_OkYhmJM7Tcj7GMLLK_hPZfx4TCb76G+Rmg@mail.gmail.com>

All,
I need to parse and transform some XML files.  When creating XML, I normally
use a templating engine like Django templates.  Parsing XML is a lot less
straightforward.  I have used Lxml and ElementTree, but they don't feel
Pythonic.

So does anyone have any good Pythonic XML tools? I basically need to ingest
XML and don't need to worry about creating it.

Thanks,
Shawn

From choman at gmail.com  Sat Oct  1 18:46:41 2011
From: choman at gmail.com (Chad Homan)
Date: Sat, 1 Oct 2011 11:46:41 -0500
Subject: [omaha] XML in Python
In-Reply-To: <CABT9k_CU=ayYX-e_OkYhmJM7Tcj7GMLLK_hPZfx4TCb76G+Rmg@mail.gmail.com>
References: <CABT9k_CU=ayYX-e_OkYhmJM7Tcj7GMLLK_hPZfx4TCb76G+Rmg@mail.gmail.com>
Message-ID: <CA+Xrk5jNKpcXnkvdc=on93sEAmvknpGVkHHyh2iGS=CYeMSC1g@mail.gmail.com>

I could be wrong, cause I am not an xml expert.  See can't even spell it
right.  but I am fairly
sure python supports xml natively.  Outside of Etree that is. so if all you
are doing is ingesting
xml.  I would look down that rabbit hole first, provided you are indeed
sticking to xml standards.

Either way, I believe we have discovered the topic for Octobers meeting.  So
Nice suggestion
Shawn.

On Sat, Oct 1, 2011 at 8:34 AM, Shawn Hermans <shawnhermans at gmail.com>wrote:

> All,
> I need to parse and transform some XML files.  When creating XML, I
> normally
> use a templating engine like Django templates.  Parsing XML is a lot less
> straightforward.  I have used Lxml and ElementTree, but they don't feel
> Pythonic.
>
> So does anyone have any good Pythonic XML tools? I basically need to ingest
> XML and don't need to worry about creating it.
>
> Thanks,
> Shawn
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> http://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org
>

From bkealey at mail.unomaha.edu  Sun Oct  2 03:59:50 2011
From: bkealey at mail.unomaha.edu (Burch Kealey)
Date: Sat, 1 Oct 2011 20:59:50 -0500
Subject: [omaha] XML in Python
In-Reply-To: <CABT9k_CU=ayYX-e_OkYhmJM7Tcj7GMLLK_hPZfx4TCb76G+Rmg@mail.gmail.com>
References: <CABT9k_CU=ayYX-e_OkYhmJM7Tcj7GMLLK_hPZfx4TCb76G+Rmg@mail.gmail.com>
Message-ID: <OFEA77084B.C0435182-ON8625791D.000AF8F0-8625791D.000AF8F2@unomaha.edu
	>


From eric.edens at gmail.com  Tue Oct  4 06:00:09 2011
From: eric.edens at gmail.com (Eric Edens)
Date: Mon, 3 Oct 2011 21:00:09 -0700
Subject: [omaha] XML in Python
In-Reply-To: <CABT9k_CU=ayYX-e_OkYhmJM7Tcj7GMLLK_hPZfx4TCb76G+Rmg@mail.gmail.com>
References: <CABT9k_CU=ayYX-e_OkYhmJM7Tcj7GMLLK_hPZfx4TCb76G+Rmg@mail.gmail.com>
Message-ID: <CAMaCFd6DeuGgzkpBXzXNF1wVZMxEo1mequTX=bX22w-rtcp16w@mail.gmail.com>

Hey Shawn,

Python has a few options for parsing/representing XML (DOM/SAX/ElementTree).
 Now, as to which is more Pythonic, here it is from Guido:

Finally, compared offerings based on e.g. 4thought (sp.?), ElementTree feels
much more practical and hence, might I say it, "pythonic".  --
http://mail.python.org/pipermail/python-dev/2005-December/058643.html

Also, Dive Into Python 3 only covers ElementTree,
http://diveintopython3.org/xml.html#xml-parse.  So there's a couple for
ElementTree.  SAX could be a good option if you have a super huge file --
it's a stream-based processor.  And if you need to follow the DOM standard,
then there're a few libraries for that too.

Stanford has a good lecture covering XML parsing in Python, however it only
covers SAX and DOM.
http://academicearth.org/lectures/xml-processing-and-python

-- Eric

From zbuhman at gmail.com  Tue Oct  4 15:39:13 2011
From: zbuhman at gmail.com (Zack Buhman)
Date: Tue, 4 Oct 2011 08:39:13 -0500
Subject: [omaha] XML in Python.
Message-ID: <CAPwg59pQPS5UvBACdacwHmH1h2r3A1JQu6=Cve9sb4sb1dQVFg@mail.gmail.com>

XML sucks; I'd thought we'd all be using json.
On Oct 4, 2011 5:02 AM, <omaha-request at python.org> wrote:
> Send Omaha mailing list submissions to
> omaha at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.python.org/mailman/listinfo/omaha
> or, via email, send a message with subject or body 'help' to
> omaha-request at python.org
>
> You can reach the person managing the list at
> omaha-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Omaha digest..."
>
>
> Today's Topics:
>
> 1. Re: XML in Python (Eric Edens)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 3 Oct 2011 21:00:09 -0700
> From: Eric Edens <eric.edens at gmail.com>
> To: Omaha Python Users Group <omaha at python.org>
> Subject: Re: [omaha] XML in Python
> Message-ID:
> <CAMaCFd6DeuGgzkpBXzXNF1wVZMxEo1mequTX=bX22w-rtcp16w at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hey Shawn,
>
> Python has a few options for parsing/representing XML
(DOM/SAX/ElementTree).
> Now, as to which is more Pythonic, here it is from Guido:
>
> Finally, compared offerings based on e.g. 4thought (sp.?), ElementTree
feels
> much more practical and hence, might I say it, "pythonic". --
> http://mail.python.org/pipermail/python-dev/2005-December/058643.html
>
> Also, Dive Into Python 3 only covers ElementTree,
> http://diveintopython3.org/xml.html#xml-parse. So there's a couple for
> ElementTree. SAX could be a good option if you have a super huge file --
> it's a stream-based processor. And if you need to follow the DOM standard,
> then there're a few libraries for that too.
>
> Stanford has a good lecture covering XML parsing in Python, however it
only
> covers SAX and DOM.
> http://academicearth.org/lectures/xml-processing-and-python
>
> -- Eric
>
>
> ------------------------------
>
> _______________________________________________
> Omaha mailing list
> Omaha at python.org
> http://mail.python.org/mailman/listinfo/omaha
>
>
> End of Omaha Digest, Vol 56, Issue 2
> ************************************

From shawnhermans at gmail.com  Wed Oct  5 01:46:59 2011
From: shawnhermans at gmail.com (Shawn Hermans)
Date: Tue, 4 Oct 2011 18:46:59 -0500
Subject: [omaha] XML in Python.
In-Reply-To: <CAPwg59pQPS5UvBACdacwHmH1h2r3A1JQu6=Cve9sb4sb1dQVFg@mail.gmail.com>
References: <CAPwg59pQPS5UvBACdacwHmH1h2r3A1JQu6=Cve9sb4sb1dQVFg@mail.gmail.com>
Message-ID: <CABT9k_D_c-Z64zxcRESOK11psG0yeiSkwhqzehTDPg87OCEsGQ@mail.gmail.com>

I will be the first to say that XML sucks and sucks hard. I believe Dante
described working with XML Schemas as the 5th level of hell.  So, if you get
the choice I would suggest using JSON, Avro, Protocol Buffers or Thrift.  I
have started using Avro for some MapReduce work. It is great because the
schema language is JSON.  Meaning you don't have to learn something new to
start using Avro.

On the XML front.  I have a few options and think ElementTree might be the
best, Pythonic option.  Amara is the most Pythonic option, but has a few
bugs in it.  Lxml is another really good option. Most of the underlying
library is written in C, so it is pretty fast.  Downside is that it requires
compiled binaries for your specific platform. Not good from a code
portability standpoint.  ElementTree is pretty good and it is part of the
standard library.  I wouldn't recommend DOM or SAX unless you enjoy
punishing yourself.

So, thanks for the advice.  I have started writing with ElementTree and it
hasn't been too painful

On Tue, Oct 4, 2011 at 8:39 AM, Zack Buhman <zbuhman at gmail.com> wrote:

> XML sucks; I'd thought we'd all be using json.
> On Oct 4, 2011 5:02 AM, <omaha-request at python.org> wrote:
> > Send Omaha mailing list submissions to
> > omaha at python.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://mail.python.org/mailman/listinfo/omaha
> > or, via email, send a message with subject or body 'help' to
> > omaha-request at python.org
> >
> > You can reach the person managing the list at
> > omaha-owner at python.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Omaha digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: XML in Python (Eric Edens)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 3 Oct 2011 21:00:09 -0700
> > From: Eric Edens <eric.edens at gmail.com>
> > To: Omaha Python Users Group <omaha at python.org>
> > Subject: Re: [omaha] XML in Python
> > Message-ID:
> > <CAMaCFd6DeuGgzkpBXzXNF1wVZMxEo1mequTX=bX22w-rtcp16w at mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > Hey Shawn,
> >
> > Python has a few options for parsing/representing XML
> (DOM/SAX/ElementTree).
> > Now, as to which is more Pythonic, here it is from Guido:
> >
> > Finally, compared offerings based on e.g. 4thought (sp.?), ElementTree
> feels
> > much more practical and hence, might I say it, "pythonic". --
> > http://mail.python.org/pipermail/python-dev/2005-December/058643.html
> >
> > Also, Dive Into Python 3 only covers ElementTree,
> > http://diveintopython3.org/xml.html#xml-parse. So there's a couple for
> > ElementTree. SAX could be a good option if you have a super huge file --
> > it's a stream-based processor. And if you need to follow the DOM
> standard,
> > then there're a few libraries for that too.
> >
> > Stanford has a good lecture covering XML parsing in Python, however it
> only
> > covers SAX and DOM.
> > http://academicearth.org/lectures/xml-processing-and-python
> >
> > -- Eric
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > Omaha mailing list
> > Omaha at python.org
> > http://mail.python.org/mailman/listinfo/omaha
> >
> >
> > End of Omaha Digest, Vol 56, Issue 2
> > ************************************
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> http://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org
>

From choman at gmail.com  Thu Oct  6 02:21:32 2011
From: choman at gmail.com (Chad Homan)
Date: Wed, 5 Oct 2011 19:21:32 -0500
Subject: [omaha] WOW I just saw this
Message-ID: <CA+Xrk5gEq7hkO7wFV8pMR2TdBJYvkCdLkm399GxzWrqV3mCdrw@mail.gmail.com>

According to resources online, Steve Jobs has passed away.  Whether you've
hated or loved
this ideas he had, we lost a visionary.  Personally I have not confirmed
this, but here it is
nonetheless.  RIP Steve Jobs.

http://betanews.com/2011/10/05/tech-loses-a-visionary-steve-jobs-dead-at-56/

From zbuhman at gmail.com  Thu Oct  6 13:49:17 2011
From: zbuhman at gmail.com (Zack Buhman)
Date: Thu, 6 Oct 2011 06:49:17 -0500
Subject: [omaha] WOW I just saw this
Message-ID: <CAPwg59qe53mWpuFyeygNhAnsUE06wtz4_YSHmiinU52gM4saHw@mail.gmail.com>

Old news.
On Oct 6, 2011 5:00 AM, <omaha-request at python.org> wrote:
> Send Omaha mailing list submissions to
> omaha at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.python.org/mailman/listinfo/omaha
> or, via email, send a message with subject or body 'help' to
> omaha-request at python.org
>
> You can reach the person managing the list at
> omaha-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Omaha digest..."
>
>
> Today's Topics:
>
> 1. WOW I just saw this (Chad Homan)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 5 Oct 2011 19:21:32 -0500
> From: Chad Homan <choman at gmail.com>
> To: Omaha Linux User Group <olug at olug.org>, Omaha Python Users Group
> <omaha at python.org>
> Subject: [omaha] WOW I just saw this
> Message-ID:
> <CA+Xrk5gEq7hkO7wFV8pMR2TdBJYvkCdLkm399GxzWrqV3mCdrw at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> According to resources online, Steve Jobs has passed away. Whether you've
> hated or loved
> this ideas he had, we lost a visionary. Personally I have not confirmed
> this, but here it is
> nonetheless. RIP Steve Jobs.
>
>
http://betanews.com/2011/10/05/tech-loses-a-visionary-steve-jobs-dead-at-56/
>
>
> ------------------------------
>
> _______________________________________________
> Omaha mailing list
> Omaha at python.org
> http://mail.python.org/mailman/listinfo/omaha
>
>
> End of Omaha Digest, Vol 56, Issue 4
> ************************************

From netarttodd at gmail.com  Mon Oct 24 21:24:16 2011
From: netarttodd at gmail.com (Todd Hamilton)
Date: Mon, 24 Oct 2011 14:24:16 -0500
Subject: [omaha] OT: CHMC Omaha Is Hiring Healthcare IT Positions
Message-ID: <CA+eZax+Z6cmYoy4Tj35Xbn2vSE5g=mjzSZSndCdjerNkgK3vzQ@mail.gmail.com>

CHMC Omaha Is Hiring Healthcare IT Positions

Business Intelligence Analyst / Report Writer:
http://careerlink.com/job/view/9921/009068
Interface Analyst: http://careerlink.com/job/view/9921/009064
Application Consultant: http://careerlink.com/job/view/9921/009058

If you are interested, let me know.  I could possibly be a reference.

-- 
Todd Hamilton
(402) 881-0438

From wereapwhatwesow at gmail.com  Mon Oct 31 17:48:29 2011
From: wereapwhatwesow at gmail.com (Steve Young)
Date: Mon, 31 Oct 2011 11:48:29 -0500
Subject: [omaha] Update
Message-ID: <CAFGSzzimfk-EG0ga40hRidPhTcMTBsdmXpupTAsTqkxgJx2y2A@mail.gmail.com>

1. Anyone show up for the last meeting?  I was out of town.

2. I have been reading a couple of programming books and wanted to share an
'ah hah!' quote or two from Code Complete:

"*Hurrying to solve a problem is one of the most time-ineffective things
you can do.*

If you?re both *building code and debugging it*, you have to *switch quickly
* between the *fluid, creative thinking that goes with design* and the *rigidly
critical thinking that goes with debugging. *

As you read your code, you have to battle the code?s familiarity and guard
against *seeing what you want to see*."

Now I know why my head hurts when trying to quickly fix an error in the
code.

Happy Halloween.

-- 
Steve Young

From choman at gmail.com  Mon Oct 31 18:03:13 2011
From: choman at gmail.com (Chad Homan)
Date: Mon, 31 Oct 2011 12:03:13 -0500
Subject: [omaha] Update
In-Reply-To: <CAFGSzzimfk-EG0ga40hRidPhTcMTBsdmXpupTAsTqkxgJx2y2A@mail.gmail.com>
References: <CAFGSzzimfk-EG0ga40hRidPhTcMTBsdmXpupTAsTqkxgJx2y2A@mail.gmail.com>
Message-ID: <CA+Xrk5jX4c_fOH4O6eFeAEFnkQctiWOA=ZrMDh=hsUr_p7g6xg@mail.gmail.com>

Unfortunately I was out of town as well.  Was planning on going, went to
Baltimore instead

On Mon, Oct 31, 2011 at 11:48 AM, Steve Young <wereapwhatwesow at gmail.com>wrote:

> 1. Anyone show up for the last meeting?  I was out of town.
>
> 2. I have been reading a couple of programming books and wanted to share an
> 'ah hah!' quote or two from Code Complete:
>
> "*Hurrying to solve a problem is one of the most time-ineffective things
> you can do.*
>
> If you?re both *building code and debugging it*, you have to *switch
> quickly
> * between the *fluid, creative thinking that goes with design* and the
> *rigidly
> critical thinking that goes with debugging. *
>
> As you read your code, you have to battle the code?s familiarity and guard
> against *seeing what you want to see*."
>
> Now I know why my head hurts when trying to quickly fix an error in the
> code.
>
> Happy Halloween.
>
> --
> Steve Young
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> http://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org
>

From jrguliz at yahoo.com  Mon Oct 31 21:17:14 2011
From: jrguliz at yahoo.com (Joe Gulizia)
Date: Mon, 31 Oct 2011 13:17:14 -0700 (PDT)
Subject: [omaha] Update
In-Reply-To: <CA+Xrk5jX4c_fOH4O6eFeAEFnkQctiWOA=ZrMDh=hsUr_p7g6xg@mail.gmail.com>
References: <CAFGSzzimfk-EG0ga40hRidPhTcMTBsdmXpupTAsTqkxgJx2y2A@mail.gmail.com>
	<CA+Xrk5jX4c_fOH4O6eFeAEFnkQctiWOA=ZrMDh=hsUr_p7g6xg@mail.gmail.com>
Message-ID: <1320092234.32186.YahooMailNeo@web112811.mail.gq1.yahoo.com>

Didn't go.

Joe and Nate



________________________________
From: Chad Homan <choman at gmail.com>
To: Omaha Python Users Group <omaha at python.org>
Sent: Monday, October 31, 2011 12:03 PM
Subject: Re: [omaha] Update

Unfortunately I was out of town as well.? Was planning on going, went to
Baltimore instead

On Mon, Oct 31, 2011 at 11:48 AM, Steve Young <wereapwhatwesow at gmail.com>wrote:

> 1. Anyone show up for the last meeting?? I was out of town.
>
> 2. I have been reading a couple of programming books and wanted to share an
> 'ah hah!' quote or two from Code Complete:
>
> "*Hurrying to solve a problem is one of the most time-ineffective things
> you can do.*
>
> If you?re both *building code and debugging it*, you have to *switch
> quickly
> * between the *fluid, creative thinking that goes with design* and the
> *rigidly
> critical thinking that goes with debugging. *
>
> As you read your code, you have to battle the code?s familiarity and guard
> against *seeing what you want to see*."
>
> Now I know why my head hurts when trying to quickly fix an error in the
> code.
>
> Happy Halloween.
>
> --
> Steve Young
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> http://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org
>
_______________________________________________
Omaha Python Users Group mailing list
Omaha at python.org
http://mail.python.org/mailman/listinfo/omaha
http://www.OmahaPython.org

From steve at alrlighting.com  Mon Oct 31 17:54:41 2011
From: steve at alrlighting.com (Steve Young)
Date: Mon, 31 Oct 2011 11:54:41 -0500
Subject: [omaha] Update
Message-ID: <CAFGSzzgUR1L9706aqQuTMhddjJeUyFEnpo6DBJZzyzu+-M-M6g@mail.gmail.com>

1. Anyone show up for the last meeting?  I was out of town.

2. I have been reading a couple of programming books and wanted to share an
'ah hah!' quote or two from Code Complete:

"*Hurrying to solve a problem is one of the most time-ineffective things
you can do.*

If you?re both *building code and debugging it*, you have to *switch quickly
* between the *fluid, creative thinking that goes with design* and the *rigidly
critical thinking that goes with debugging. *

As you read your code, you have to battle the code?s familiarity and guard
against *seeing what you want to see*."

Now I know why my head hurts when trying to quickly fix an error in the
code.

Happy Halloween.

-- 
Steve Young
Architectural Lighting Resources
13829 Industrial Rd
Omaha, NE 68137

402-651-5216 Cell
402-397-2867 Office
www.ALRLighting.com

From jason.troy at gmail.com  Thu Oct  6 02:25:51 2011
From: jason.troy at gmail.com (Jason Troy)
Date: Thu, 06 Oct 2011 00:25:51 -0000
Subject: [omaha] [olug] WOW I just saw this
In-Reply-To: <CA+Xrk5gEq7hkO7wFV8pMR2TdBJYvkCdLkm399GxzWrqV3mCdrw@mail.gmail.com>
References: <CA+Xrk5gEq7hkO7wFV8pMR2TdBJYvkCdLkm399GxzWrqV3mCdrw@mail.gmail.com>
Message-ID: <CAF0R2D5XiRU9CDeR+YSx0SbmRA2=RsJGfqy7zexr28c7rF2c7g@mail.gmail.com>

http://www.apple.com/stevejobs
On Oct 5, 2011 7:22 PM, "Chad Homan" <choman at gmail.com> wrote:
> According to resources online, Steve Jobs has passed away. Whether you've
> hated or loved
> this ideas he had, we lost a visionary. Personally I have not confirmed
> this, but here it is
> nonetheless. RIP Steve Jobs.
>
>
http://betanews.com/2011/10/05/tech-loses-a-visionary-steve-jobs-dead-at-56/
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug

From ggerke at gmail.com  Thu Oct  6 02:29:23 2011
From: ggerke at gmail.com (Greg Gerke)
Date: Thu, 06 Oct 2011 00:29:23 -0000
Subject: [omaha] [olug] WOW I just saw this
In-Reply-To: <CA+Xrk5gEq7hkO7wFV8pMR2TdBJYvkCdLkm399GxzWrqV3mCdrw@mail.gmail.com>
References: <CA+Xrk5gEq7hkO7wFV8pMR2TdBJYvkCdLkm399GxzWrqV3mCdrw@mail.gmail.com>
Message-ID: <CA+v4rR-VeKWYLv+bRPj08b04eOkqj8=35j-MeBE=yPc+SMTw-Q@mail.gmail.com>

It's listed on the www.apple.com site so unless it's a huge hack I'd say
it's the real deal. Bummer to be sure.

On Wed, Oct 5, 2011 at 7:21 PM, Chad Homan <choman at gmail.com> wrote:

> According to resources online, Steve Jobs has passed away.  Whether you've
> hated or loved
> this ideas he had, we lost a visionary.  Personally I have not confirmed
> this, but here it is
> nonetheless.  RIP Steve Jobs.
>
>
> http://betanews.com/2011/10/05/tech-loses-a-visionary-steve-jobs-dead-at-56/
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
>



-- 
Greg Gerke
ggerke at gmail.com