On 27Jan2021 00:19, C W wrote:
>Here's the code again, class should be called PERSONDatabase,
>misspelled
>earlier:
>class PERSONDatabase:
> def __init__(self, id, created_at, name, attend_date, distance):
> self._id = id
> self.created_at = created_at
> self.name= name
> se
To debug python code I use spyder from the anaconda distribution
Am Mittwoch, 27. Januar 2021 schrieb C W :
> Hi Michael,
> Here's the code again, class should be called PERSONDatabase, misspelled
> earlier:
> class PERSONDatabase:
>def __init__(self, id, created_at, name, attend_date, distan
Hi Michael,
Here's the code again, class should be called PERSONDatabase, misspelled
earlier:
class PERSONDatabase:
def __init__(self, id, created_at, name, attend_date, distance):
self._id = id
self.created_at = created_at
self.name= name
self.attend_date = attend_date
On 1/26/21 8:30 PM, Grant Edwards wrote:
> Me too (MS in CSci), but I can't remember the last time I used a
> debugger.
I use a debugger frequency in C++, and sometimes C. Even running a
debugger on an attached device like an Arduino is sometimes very useful.
Good debuggers let you do things lik
On 1/26/21 8:37 PM, C W wrote:
> I have a naive question. How do I use traceback or trace the stack? In
> particular, I'm using VS Code with Python interactive console.
Show us the traceback here and we can help you interpret it. Copy and
paste it from the VS Code console.
> Say, I want to print
On Tue, Jan 26, 2021 at 8:13 PM Dan Stromberg wrote:
>
> On Tue, Jan 26, 2021 at 4:01 PM C W wrote:
>
>> Hello everyone,
>>
>> I'm a long time Matlab and R user working on data science. How do you
>> troubleshooting/debugging in Python?
>>
>
> I frequently read tracebacks and think about what's
On Tue, Jan 26, 2021 at 4:01 PM C W wrote:
> Hello everyone,
>
> I'm a long time Matlab and R user working on data science. How do you
> troubleshooting/debugging in Python?
>
I frequently read tracebacks and think about what's up in the code.
I also often add print functions or logging - empir
On 2021-01-27, Cameron Simpson wrote:
> Me either. Like grant, i fall into the "look at the stack trace and
> think a bit, then put in print() calls or similar to show me whether
> things are what I expect them to be when the code runs".
>
> I actually have a Computer Science degree, but I thin
Thanks for your replies. My apologies for the poor indent. I'm rewriting
the code below.
class NEODatabase:
def __init__(self, id, created_at, name, attend_date, distance):
self._id = id
self.created_at = created_at
self.name = name
self.attend_date = attend_date
self.distance = distance
@classme
On Jan 26, 2021, at 18:16, Grant Edwards wrote:
>
>> How do you troubleshooting/debugging in Python?
>
> Mostly I read exception trace and read the code and think about it.
>
> If that doesn't work, I add some print() or syslog() calls.
>
> If I really get stuck, I try to write as small a prog
> On Jan 26, 2021, at 2:00 PM, C W wrote:
>
> Hello everyone,
>
> I'm a long time Matlab and R user working on data science. How do you
> troubleshooting/debugging in Python?
>
Another approach is to run the code in an IDE. I happen to use Wing, but that
is a coincidence. But almost ANY
On 26Jan2021 14:00, C W wrote:
>I'm a long time Matlab and R user working on data science. How do you
>troubleshooting/debugging in Python?
>
>I ran into this impossible situation to debug:
>class person:
>def __init__(self, id, created_at, name, attend_date, distance):
>"""Create a new `person`.
CW> How do you troubleshooting/debugging in Python?
GE> Mostly I read exception trace and read the code and think about it.
GE> If that doesn't work, I add some print() or syslog() calls.
CW> I know hardcore computer scientists would tell me about Python debugger.
GE> I've been writing Python fo
On 2021-01-26, C W wrote:
> How do you troubleshooting/debugging in Python?
Mostly I read exception trace and read the code and think about it.
If that doesn't work, I add some print() or syslog() calls.
If I really get stuck, I try to write as small a program as possible
that demonstrates the
Hello everyone,
I'm a long time Matlab and R user working on data science. How do you
troubleshooting/debugging in Python?
I ran into this impossible situation to debug:
class person:
def __init__(self, id, created_at, name, attend_date, distance):
"""Create a new `person`.
"""
self._id = id
self
> On 26 Jan 2021, at 14:35, Paul Grinberg wrote:
>
> I have a C++ library (luckily with source code, so I know what's going on) to
> which I wrote c bindings. The library internally starts an event pthread
> which generates callbacks back into python. The c binding for processing
> these ca
On 1/26/21 9:05 AM, Terry Reedy wrote:
On 1/26/2021 4:01 AM, Maziar Ghasemi wrote:
...
Please do not repost, especially the same day.
Maziar Ghasemi appears to be a new user, and had to sign up to the Python List mailing list. Are you seeing his request
twice because you use gmane?
--
On 1/26/2021 4:01 AM, Maziar Ghasemi wrote:
Hi
help me to repair this erorr:
Warning: translation file 'git_en_US' could not be loaded.
Using default.
and download python39.dll
Please do not repost, especially the same day.
On 1/26/21, Maziar Ghasemi wrote:
Hi
help me to repair this erorr:
Hi
help me to repair this erorr:
Warning: translation file 'git_en_US' could not be loaded.
Using default.
and download python39.dll
On 1/26/21, Maziar Ghasemi wrote:
> Hi
> help me to repair this erorr:
> Warning: translation file 'git_en_US' could not be loaded.
> Using default.
> and download
I have a C++ library (luckily with source code, so I know what's going on) to
which I wrote c bindings. The library internally starts an event pthread which
generates callbacks back into python. The c binding for processing these
callbacks look like this (simplified for convenience):
PyGILState
20 matches
Mail list logo
