Google Groups Home
Help | Sign in
Message from discussion SQLAlchemy and py2exe problem
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
Michael Bayer  
View profile
 More options Dec 19 2006, 10:20 am
From: "Michael Bayer" <zzz...@gmail.com>
Date: Tue, 19 Dec 2006 07:20:57 -0800
Local: Tues, Dec 19 2006 10:20 am
Subject: Re: SQLAlchemy and py2exe problem
most likely this is an incompatibility with SA's usage of the name
"logging" as a module name, which is also a standard python module (you
might have the same issue with the "types" module).  absolute module
imports by default are to become the standard in py2.6 and i believe
are supported in py2.5, which should eliminate this silly issue, but i
dont know much about py2exe.

so short answer, "theyre both guilty"...SA for expecting absolute
module behavior, py2exe for assuming relative.

show the py2exe folks the evil thing im doing in sqlalchemy.logging (im
importing the python's "logging" via __import__) and im sure theyll
shake their heads in disgust....if they cant offer a solution, and you
are truly "desperate", youll have to change the name "logging" (and
maybe "types" as well) throughout your SA dist.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google