Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
TypeError: list indices must be integers, not str
See original GitHub issueI had this error from i3ipc.py: “TypeError: list indices must be integers, not str”
Seems to be from an __init__ invoked from get_tree, so I guess this is the __init__ of Con.
Issue Analytics
- State:
- Created 8 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
TypeError: list indices must be integers or slices, not str
This type error occurs when indexing a list with anything other than integers or slices, as the error mentions. Usually, the most straightforward...
Read more >TypeError: list indices must be integers or slices, not str
The error “typeerror: list indices must be integers or slices, not str” is raised when you try to access a list using string...
Read more >TypeError: list indices must be integers or slices ... - STechies
TypeError: list indices must be integers or slices, not str. Each element in a list in Python has a unique position. This position...
Read more >TypeError: list indices must be integers, not str (boolean ...
You have tried to index a list features with a string and it is not possible with python. List indices can only be...
Read more >List Indices Must Be Integers Or Slices, Not 'Str'? - Java2Blog
To avoid TypeError: list indices must be integers or slices, not str in the above example you must first access the dictionary using...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I just pushed e9fcefa and I can’t reproduce the error anymore with that example.
@Pikaro , I can’t tell now neither if it’s the same as the original issue, I will test it a future day (I will first have to retrieve the original script from three years ago).