On Jul 5, 5:05 pm, Thomas Jollans wrote:
> On 06/27/2011 06:59 PM, miamia wrote:
>
> > Hello,
>
> > on 32-bit windows everything works ok but on 64-bit win I am getting
> > this error:
> > Traceback (most recent call last):
> > File "app.py", line 1040, in do_this_now
> > File "kinterbasdb\__i
On 06/27/2011 06:59 PM, miamia wrote:
> Hello,
>
> on 32-bit windows everything works ok but on 64-bit win I am getting
> this error:
> Traceback (most recent call last):
> File "app.py", line 1040, in do_this_now
> File "kinterbasdb\__init__.pyc", line 119, in
> File "kinterbasdb\_kinterba
Am 28.06.2011 14:59, schrieb Peter Irbizon:
> yes, that's right. but I am using embedable version of fbclient.dll so I
> don't need to install Firebird Sql Server package. all dlls are in my
> program folder even so it does not work.
fbclient.dll may depend on more DLLs. Dependency walker is a gre
> kinterbasdb's extension module _kinterbasdb.pyd depends on the shared
> library fbclient.dll. The Firebird client library is of the Firebird SQL
> server. As I already explained you have to install the 32bit (!) version
> of Firebird and enable the "copy client dll to system32" option during
> th
Am 27.06.2011 22:03, schrieb Peter Irbizon:
> well, my program exe generated from py2exe. I am running Python 2.7 on my
> win xp 32bit box then I compile my application with py2exe. After that I can
> use it on other computers (on 32bit everything works perfect) but on 64 bit
> windows I am getting
>> Are you running 32bit or 64bit Python on your 64bit Windows box? You
>> have to install the same flavour of Python, kinterbasdb and Firebird SQL
>> (all 32bit or all 64bit). You also have to check the "copy client dlls
>> to system directory" check box during the installation of Firebird SQL.
>>
Am 27.06.2011 19:02, schrieb Peter Irbizon:
> Hello,
>
> on 32-bit windows everything works ok but on 64-bit win I am getting
> this error:
> Traceback (most recent call last):
> File "app.py", line 1040, in do_this_now
> File "kinterbasdb\__init__.pyc", line 119, in
> File "kinterbasdb\_kinte
Hello,
on 32-bit windows everything works ok but on 64-bit win I am getting
this error:
Traceback (most recent call last):
File "app.py", line 1040, in do_this_now
File "kinterbasdb\__init__.pyc", line 119, in
File "kinterbasdb\_kinterbasdb.pyc", line 12, in
File "kinterbasdb\_kinterbasd
Hello,
on 32-bit windows everything works ok but on 64-bit win I am getting
this error:
Traceback (most recent call last):
File "app.py", line 1040, in do_this_now
File "kinterbasdb\__init__.pyc", line 119, in
File "kinterbasdb\_kinterbasdb.pyc", line 12, in
File "kinterbasdb\_kinterbasdb.py
On 8/6/2010 7:18 PM, Philip Semanchuk wrote:
On Aug 6, 2010, at 3:14 PM, W. eWatson wrote:
I must be missing something. I tried this. (Windows, IDLE, Python 2.5)
Yes, as Benjamin Kaplan pointed out and as I said in the email where I
posted this code snippet, "dependencies is a list of custom
On Aug 6, 2010, at 3:14 PM, W. eWatson wrote:
I must be missing something. I tried this. (Windows, IDLE, Python 2.5)
Yes, as Benjamin Kaplan pointed out and as I said in the email where I
posted this code snippet, "dependencies is a list of custom classes
that represent modules we need (e
On Aug 6, 2010, at 3:14 PM, W. eWatson wrote:
> I must be missing something. I tried this. (Windows, IDLE, Python 2.5)
> # Try each module
> import sys
> import numpy
> import scipy
> import string
>
> dependencies = "numyp", "scipy"
> for dependency in dependencies:
>try:
>__import_
On Fri, Aug 6, 2010 at 12:14 PM, W. eWatson wrote:
> I must be missing something. I tried this. (Windows, IDLE, Python 2.5)
> # Try each module
> import sys
> import numpy
> import scipy
> import string
>
> dependencies = "numyp", "scipy"
> for dependency in dependencies:
> try:
> __impo
I must be missing something. I tried this. (Windows, IDLE, Python 2.5)
# Try each module
import sys
import numpy
import scipy
import string
dependencies = "numyp", "scipy"
for dependency in dependencies:
try:
__import__(dependency.name)
except ImportError:
# Uh oh!
On 8/5/2010 6:47 PM, Philip Semanchuk wrote:
On Aug 5, 2010, at 8:55 PM, W. eWatson wrote:
It's been awhile since I've used python, and I recall there is a way
to find the version number from the IDLE command line prompt. dir,
help, __version.__?
Hi Wayne,
FYI it's got nothing to do with IDL
On Aug 6, 2010, at 10:20 AM, Richard D. Moores wrote:
On Thu, Aug 5, 2010 at 18:47, Philip Semanchuk
wrote:
it's just a question of whether or not
the module in question exposes any kind of a version attribute.
There's no
standard, unfortunately. The most popular convention seems to be
On Thu, Aug 5, 2010 at 18:47, Philip Semanchuk wrote:
>
> it's just a question of whether or not
> the module in question exposes any kind of a version attribute. There's no
> standard, unfortunately. The most popular convention seems to be via an
> attribute called __version__, but I've also seen
On Aug 5, 2010, at 8:55 PM, W. eWatson wrote:
It's been awhile since I've used python, and I recall there is a way
to find the version number from the IDLE command line prompt. dir,
help, __version.__?
Hi Wayne,
FYI it's got nothing to do with IDLE, it's just a question of whether
or no
On 8/5/2010 6:23 PM, MRAB wrote:
W. eWatson wrote:
It's been awhile since I've used python, and I recall there is a way
to find the version number from the IDLE command line prompt. dir,
help, __version.__?
I made the most minimal change to a program, and it works for me, but
not my partner. He
On 8/5/2010 6:13 PM, Steven D'Aprano wrote:
On Thu, 05 Aug 2010 17:55:30 -0700, W. eWatson wrote:
I'm pretty sure he has the same version of Python, 2.5, but perhaps not
the numpy or scipy modules. I need to find out his version numbers.
It's only a convention, but the usual way is to check t
W. eWatson wrote:
It's been awhile since I've used python, and I recall there is a way to
find the version number from the IDLE command line prompt. dir, help,
__version.__?
I made the most minimal change to a program, and it works for me, but
not my partner. He gets
Traceback (most recent
On Thu, 05 Aug 2010 17:55:30 -0700, W. eWatson wrote:
> I'm pretty sure he has the same version of Python, 2.5, but perhaps not
> the numpy or scipy modules. I need to find out his version numbers.
It's only a convention, but the usual way is to check the __version__
attribute. It works for Nump
It's been awhile since I've used python, and I recall there is a way to
find the version number from the IDLE command line prompt. dir, help,
__version.__?
I made the most minimal change to a program, and it works for me, but
not my partner. He gets
Traceback (most recent call last):
File
resolved! don't know why or how but it is...
just restared eclipse for the fourth time
"alejandro" wrote in message
news:hhu38i$h2...@ss408.t-com.hr...
> When I inport it wia python command line it all looks fine but if i try to
> run it from eclipse it gives me an error that there is no packag
When I inport it wia python command line it all looks fine but if i try to
run it from eclipse it gives me an error that there is no package mechanize.
Have anybody had this situation?
win XP
python26
--
http://mail.python.org/mailman/listinfo/python-list
Gabriel Rossetti wrote:
Hello
everyone,
I am having problems with the platform module when being run from a
frozen program (py2exe). It imports it fine, but it gives me the
following error :
'module' object does not contain attribute 'platform' when I do this :
platform.platfom()
Does p
Hello everyone,
I am having problems with the platform module when being run from a
frozen program (py2exe). It imports it fine, but it gives me the
following error :
'module' object does not contain attribute 'platform' when I do this :
platform.platfom()
Does platform have a problem with
Hello,
I'm trying to solve an issue with custom Python module at QNX 6.4.0
and Python 2.5.2.
I have simple Python module (A.so) written in c++ which is linked
against some other c++ library (B.so) both build by autotools.
On Linux all works fine with PYTHONPATH pointed to A.so directory when
dyna
Hello,
I am trying to create exectuables on inux using "pyinstaller". I am
using pyinstaller-1.3, RHEL 4.4, Python 2.5.
The executables fail to run. The problem returned is pertaining to
"struct.py" not being able to find the module "_struct".
struct.py is located under /usr/local/lib/python-2.5
Matimus wrote:
> Do you have more than one version of Python installed? Is
> win32clipboard installed for both versions? It could be that the
Yup, that was the problem. Thanx!
--
"A mi smo stranci u vlastitoj zemlji zbog ljudskog sljama, lipa nasa
silovana"
--
http://mail.python.org/mailman/l
On Feb 6, 9:29 am, Boris Ozegovic <[EMAIL PROTECTED]>
wrote:
> Hi
>
> I am writing some simple script, and when I start my script from command
> line (python Imenik.py), everything works perfectly. If I double clik the
> same script in my desktop I get the following error:
>
> "No module name impo
Hi
I am writing some simple script, and when I start my script from command
line (python Imenik.py), everything works perfectly. If I double clik the
same script in my desktop I get the following error:
"No module name import win32clipboard"
--
"A mi smo stranci u vlastitoj zemlji zbog ljudsko
Tekkaman wrote:
>> Putting /usr/lib64/python2.4 as the first entry into your
>>
>> PYTHONPATH
>>
>> environment variable might fix the problem (the idea is
>> that /usr/lib64/python2.4 precedes /usr/lib/python2.4 in sys.path and is
>> therefore used for the import of the logging package).
> Thank
On Dec 14, 6:41 pm, Peter Otten <[EMAIL PROTECTED]> wrote:
> Tekkaman wrote:
>> lib is a symlink to lib64
> So my initial diagnosis was correct. Unfortunately I can no longer recommend
> that you remove the symlink...
>
Yes. What I really meant in my first reply was "it's not a symlink in
the scr
Tekkaman wrote:
> lib is a symlink to lib64
So my initial diagnosis was correct. Unfortunately I can no longer recommend
that you remove the symlink...
Putting /usr/lib64/python2.4 as the first entry into your
PYTHONPATH
environment variable might fix the problem (the idea is
that /usr/lib64
Peter Otten wrote:
> Tekkaman wrote:
>
> > Peter Otten wrote:
> >> Tekkaman wrote:
> >>
> >> > Thanks for the hint, but it's not a symlink
> >>
> >> What does logging._srcfile contain? Should be
> >>
> >> >>> import logging
> >> >>> logging._srcfile
> >> '/usr/lib/python2.4/logging/__init__.py'
>
lib is a symlink to lib64
Peter Otten wrote:
> Tekkaman wrote:
>
> > Peter Otten wrote:
> >> Tekkaman wrote:
> >>
> >> > Thanks for the hint, but it's not a symlink
> >>
> >> What does logging._srcfile contain? Should be
> >>
> >> >>> import logging
> >> >>> logging._srcfile
> >> '/usr/lib/python2
Tekkaman wrote:
> Peter Otten wrote:
>> Tekkaman wrote:
>>
>> > Thanks for the hint, but it's not a symlink
>>
>> What does logging._srcfile contain? Should be
>>
>> >>> import logging
>> >>> logging._srcfile
>> '/usr/lib/python2.4/logging/__init__.py'
>>
>> on your machine, but probably isn't.
'/usr/lib64/python2.4/logging/__init__.py'
Peter Otten wrote:
> Tekkaman wrote:
>
> > Thanks for the hint, but it's not a symlink
>
> What does logging._srcfile contain? Should be
>
> >>> import logging
> >>> logging._srcfile
> '/usr/lib/python2.4/logging/__init__.py'
>
> on your machine, but pro
Tekkaman wrote:
> Thanks for the hint, but it's not a symlink
What does logging._srcfile contain? Should be
>>> import logging
>>> logging._srcfile
'/usr/lib/python2.4/logging/__init__.py'
on your machine, but probably isn't.
Peter
--
http://mail.python.org/mailman/listinfo/python-list
Peter Otten wrote:
>
> An evil symlink, maybe?
Thanks for the hint, but it's not a symlink
>
> $ ln -s /usr/local/lib/python2.4/logging
> $ python
> [snip]
> >>> import logging
> >>> logging.basicConfig(format="%(pathname)s")
> >>> logging.getLogger().critical("yadda")
> /usr/local/lib/python2.4/l
sim.sim wrote:
> Hi, i've check documentation, and found that logging.basicConfig takes
> no arguments (probably we have different versions of logging package),
Your Python version is < 2.4. Now basicConfig takes optional keyword
args:
basicConfig([**kwargs])
Does basic configuration for the log
Tekkaman wrote:
> I'm getting a strange behaviour from the "pathname" and "lineno"
> formatter mapping keys. Instead of my file and my line number I get:
>
> /usr/lib/python2.4/logging/__init__.py
>
> as the file, and 1072 as the line number. I set up my config as
> follows:
>
> logBaseConf = {
Hi, i've check documentation, and found that logging.basicConfig takes
no arguments (probably we have different versions of logging package),
and i've never used it.
just try this:
fileName = 'testlog.log'
logName = 'LOG'
iHandler = logging.FileHandler(fileName)
iHandler.setFormatter(
logging.F
I'm getting a strange behaviour from the "pathname" and "lineno"
formatter mapping keys. Instead of my file and my line number I get:
/usr/lib/python2.4/logging/__init__.py
as the file, and 1072 as the line number. I set up my config as
follows:
logBaseConf = {
'level' : logging.DEBUG,
Nico Grubert wrote:
> + On a solaris machine running thunderbird 1.5.0.8 and on a macintosh
> machine running eudora umlauts are *not* displayed properly.
> The email header does not contain any "Content-type". If I manually
> switch the email client's character encoding to "Unicode (UTF-8)"
Hi there,
I wrote a short python script that sends an email using python's email
module and I am using Python 2.3.5.
The problem is, that umlauts are not displayed properly in some email
clients:
+ On a windows machine running thunderbird 1.0.2 umlauts are displayed
properly.
The email he
Peter Otten wrote:
> You can achieve the desired behaviour by adding a custom Filter:
>
> import sys
> import logging
>
> logger = logging.getLogger("my_app")
> logger.setLevel(logging.DEBUG)
>
> class LevelFilter(logging.Filter):
> def __init__(self, level):
> self.level = level
>
Ritesh Raj Sarraf wrote:
> Vinay Sajip wrote:
>> It's usual to rely on logger levels and to set handler levels for
>> additional refinement of what goes to a particular handler's
>> destination.
> The problem is that for StreamHandler, logging module logs to
> sys.stderr.
> I want to use the lo
Vinay Sajip wrote:
>
> It's usual to rely on logger levels and to set handler levels for
> additional refinement of what goes to a particular handler's
> destination.
>
The problem is that for StreamHandler, logging module logs to
sys.stderr.
I want to use the logging feature for most of the mess
Ritesh Raj Sarraf wrote:
> When I execute the above code, logger.info()'s messages don't get
> displayed. And logger.warning()'s messages get displayed twice.
>
The warning messages are displayed twice because you have two handlers
which both output to the console.
The reason you don't get the i
Ritesh Raj Sarraf wrote:
> import os, sys, logging
>
> logger = logging.getLogger("my_app")
>
I tried this code:
import logging, sys
# set up logging to file - see previous section for more details
logging.basicConfig(level=logging.DEBUG,
format='%(asctime)s %(name)-12s %(le
import os, sys, logging
logger = logging.getLogger("my_app")
conerr = logging.StreamHandler(sys.stderr)
conerr.setLevel(logging.DEBUG)
conerr_formatter = logging.Formatter('%(levelname)s %(message)s')
conerr.setFormatter(conerr_formatter)
console = logging.StreamHandler(sys.stdout)
console.setLe
May be related to this bug:
http://issues.apache.org/jira/browse/MODPYTHON-12
Where you have:
import mod_python.psp
change it to:
psp = apache.import_module("mod_python.psp")
Access the PSP object then as:
psp.PSP
and not:
mod_python.psp.PSP
It will happen where somewhere else w
Hi folks...
I'm getting a weird problem while loading psp module from mod_python.
It only happen somethimes, and I just can't figure out why.
I saw other threads in other lists over the net, but none of them
solved the problem.
My last hope is this last thread before been forced to change my
proje
scott wrote:
> Can I get this Pyshell behavior using python from the terminal?
One application is "active" at any point in time, and this application
controls the menu, has its windows displayed, and so on. So when the
Terminal.app is active, Python cannot be.
Now, it may be possible to programma
Martin v. Löwis wrote:
Try pythonw.
Thanks, that was it.
One more question, when I use the EasyDialogs module to, for example,
display a message in a dialog box, the dialog box doesn't appear directly.
I need to switch to 'python' by clicking on it on the dock or
alt-tabbing to 'python' in order
scott wrote:
> MacOS.Error: (-1713, 'no user interaction is allowed')
Try pythonw.
Martin
--
http://mail.python.org/mailman/listinfo/python-list
scott wrote:
First my setup:
I'm using the framework build of Python 2.4.1
( http://bob.pythonmac.org/archives/2005/03/31/macpython-241-installer/ )
on an ibook G4 running Mac OS 10.3.8.
I installed wxPython 2.5.5.1 ( Unicode runtime 2.5.5.1 for the Panther
version of Macpython-OSX 2.4 )
( http:/
scott wrote:
> EasyDialogs module
>
> ( http://www.python.org/doc/2.4.1/mac/module-EasyDialogs.html )
>
> works with pyshell (interactive python program included with wxPython)
> but not with python launched at the terminal:
Could you be more precise what "works not" means? What do you expect
t
First my setup:
I'm using the framework build of Python 2.4.1
( http://bob.pythonmac.org/archives/2005/03/31/macpython-241-installer/ )
on an ibook G4 running Mac OS 10.3.8.
I installed wxPython 2.5.5.1 ( Unicode runtime 2.5.5.1 for the Panther
version of Macpython-OSX 2.4 )
( http://wxpython.org
61 matches
Mail list logo
