Subject: anyone having problems with python on debian testing

From: emetib <[email-masked]>
Date: Mon, 19 Sep 2016 12:08:16 -0700 (PDT)

is anyone having problems with their deb testing systems?

i have a python3 script that isn't giving any output where the other linux systems that i have tested it on are.

other systems have differing versions of python and what looks like gcc also.

i'm thinking that it's something to do with gcc since if i run it with python or python3 it's not working.

works on debian stable though.

don't know how much info people want about what is happening.

i would like to know if others are having any problems with their systems.

thanks

---

From: emetib <[email-masked]>
Date: Sat, 24 Sep 2016 15:17:13 -0700 (PDT)

running as root to get the journal.

no errors.

---

From: emetib <[email-masked]>
Date: Fri, 23 Sep 2016 15:32:34 -0700 (PDT)

michael, 

it's not any modules that i know of.  only using re for the three scripts that i'm using.  as stated it's working on all of my other virts, so i'm not that worried about it right now.

i can't make anything crash.

it's just the output from the third that's not getting wrote to the file, and that i can't explain right now.

thank you though
em

---

From: Michael Lange <[email-masked]>
Date: Sat, 24 Sep 2016 17:06:15 +0200

Hi,

On Fri, 23 Sep 2016 15:32:34 -0700 (PDT)
emetib <[email-masked]> wrote:

> michael, 
> 
> it's not any modules that i know of.  only using re for the three
> scripts that i'm using.  as stated it's working on all of my other
> virts, so i'm not that worried about it right now.
> 
> it's just the output from the third that's not getting wrote to the
> file, and that i can't explain right now.

Maybe a problem with permissions? Are there any error messages?

Regards

Michael

---

From: emetib <[email-masked]>
Date: Tue, 20 Sep 2016 15:22:27 -0700 (PDT)

yeah, i don't know what to say.   started to use my stable virt for working on. 

it's just the last part of a list comparison that's bothering me.

if you have journalctl going you can check out the scripts 
-- https://drive.google.com/open?id=0BwhDqxZzf5XHMk1na1VNMWFtTDA --

it's the last one that should write to the file, yet it's not.  all other virts that it's tested on do.

---

From: emetib <[email-masked]>
Date: Mon, 19 Sep 2016 14:36:39 -0700 (PDT)

well thank you then ric.  glad it's not after hours or i would be doing the same thing.

no, i just noticed it today, and i can run the script on my other virtual machines without issue.  it's just the debian testing that is the problem.

whether i am calling -- python3 script or python script, or python3 >>> or python >>> and typing them in it's not working how it should.  wasted a weekend thinking that i had messed up my code.

so i was just wondering if others were having problems.  i'm starting to think that it's gcc version for python that is giving me problems.  yet i'm not that smart to figure it out.

---

From: Michael Lange <[email-masked]>
Date: Fri, 23 Sep 2016 00:09:12 +0200

Hi,

On Mon, 19 Sep 2016 14:36:39 -0700 (PDT)
emetib <[email-masked]> wrote:

(...)
> whether i am calling -- python3 script or python script, or python3 >>>
> or python >>> and typing them in it's not working how it should.
> wasted a weekend thinking that i had messed up my code.
> 
> so i was just wondering if others were having problems.  i'm starting
> to think that it's gcc version for python that is giving me problems.
> yet i'm not that smart to figure it out.

here on my laptop with an up to date testing I cannot see any problems
with Python. Can you provide more information about what happens when you
run your script? Does the Python interpreter crash with a segfault or do
you get some sort of Python traceback?
Since Python per se seems to run ok here (and since you can start the
interpreter prompt) my guess is that some third party extension you use
might be the culprit. Maybe you could try to import any module you are
using one by one from the python prompt and see if this is enough to
provoke a crash.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Blast medicine anyway!  We've learned to tie into every organ in the
human body but one.  The brain!  The brain is what life is all about.
		-- McCoy, "The Menagerie", stardate 3012.4

---

From: Tony Baldwin <[email-masked]>
Date: Mon, 19 Sep 2016 18:09:42 -0400

> so i was just wondering if others were having problems.  i'm starting to think that it's gcc version for python that is giving me problems.  yet i'm not that smart to figure it out.

my python scripts seem to be functioning fine.
even ones that use guis (tkinter)

-- 
http://tonybaldwin.me
all tony, all the time

---

From: Anthony Baldwin <[email-masked]>
Date: Mon, 19 Sep 2016 18:11:58 -0400

On 09/19/2016 06:09 PM, Tony Baldwin wrote:
>> no, i just noticed it today, and i can run the script on my other
>> virtual machines without issue.  it's just the debian testing that is
>> the problem.
>>
>> whether i am calling -- python3 script or python script, or python3

Sorry...I'm using Jessie/stable...my bad
(I'm an old man with a brain tumour, what do you expect?)

-- 
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT

---

From: Ric Moore <[email-masked]>
Date: Mon, 19 Sep 2016 17:08:01 -0400

> i would like to know if others are having any problems with their systems.

If this weren't a Debian List I'd be cursing like a drunken sailor. :) Ric

-- 
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html