[issue38925] Decoding unicode not supported after upd to 2.7.17 [possible pymysql related?]
New submission from Sebastian Szwarc :
As follow up to my recent bug error regarding segmentation fault.
Installed 2.7.17 on Mojave.
Because MySQLdb for reason unknown (SSL required error) is impossible to
install by PIP I used PyMysql and modified line as `import pymysql as MySQLdb`
There is no segmentation fault for now (what indicates there can be bug in
older python interpreter) but:
the following line worked fine for 2+ years:
colVals = unicode(", ".join(stringList), 'utf-8')
however now I got the error:
2019-11-26 23:25:55,273 [INFO]: Beginning incremental ingest of epf_video_price
(200589 records)
Traceback (most recent call last):
File "EPFImporter2.py", line 453, in
main()
File "EPFImporter2.py", line 436, in main
fieldDelim=fieldSep)
File "EPFImporter2.py", line 221, in doImport
ing.ingest(skipKeyViolators=skipKeyViolators)
File "/Users/sebastian/Documents/test2/EPFIngester.py", line 111, in ingest
self.ingestIncremental(skipKeyViolators=skipKeyViolators)
File "/Users/sebastian/Documents/test2/EPFIngester.py", line 206, in
ingestIncremental
skipKeyViolators=skipKeyViolators)
File "/Users/sebastian/Documents/test2/EPFIngester.py", line 375, in
_populateTable
colVals = unicode(", ".join(stringList), 'utf-8')
TypeError: decoding Unicode is not supported
So the questions:
1. why decoding Unicode is not supported if previously was and worked fine?
2. is it python thing or some pymysql enforcing rules ?
For reference I attached populateTable function
------
components: macOS
files: populateTable.txt
messages: 357537
nosy: Sebastian Szwarc, ned.deily, ronaldoussoren
priority: normal
severity: normal
status: open
title: Decoding unicode not supported after upd to 2.7.17 [possible pymysql
related?]
type: behavior
versions: Python 2.7
Added file: https://bugs.python.org/file48745/populateTable.txt
___
Python tracker
<https://bugs.python.org/issue38925>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38889] Segmentation fault when using EPF Importer
Sebastian Szwarc added the comment: If someone really want to test The test procedure should be as follows: Get the EPFImporter tool https://affiliate.itunes.apple.com/resources/documentation/epfimporter/ Set up your database and put relevant login information in EPFConfig Get the simple minimal dump from here - https://drive.google.com/file/d/1s1VmE-7NGsUoiBjvBQ1iaalUjYSNPh9w/view?usp=sharing try to import EPFImport.py full/* these are only things I can provide at the moment,hope this helps explaining a little more. On Fri, Nov 22, 2019 at 10:26 PM Sebastian Szwarc wrote: > > > Sebastian Szwarc added the comment: > > I strongly disagree. Python 2.7 is 2.7 -> if some new errors appeared > after upgrading between minor version this is not expected behaviour, > and therefore it means there is error in interpreter itself. > upgrading from 2.7 to 2.7 is not the same as upgrading from swift 3 to swift > 4. > > And as I said in another comment - I dont understand your tendency to > "minimal example" - minimal example solves nothing because minimal != > production. > On production there is of course 3rd party code - tool is written by > Apple and MysqlDB module by another 3rd party vendor. How can you even > expect to provide minimal example in such case? > > Not to mention I got no errors in code - just SEGMENTATION FAULT which > indicates python interpreter after upgrade doing something very bad in > memory management ---> this is python issue. > Or give me solution to install specific version of 2.7 that was > available one year ago on Ubuntu. > > On Fri, Nov 22, 2019 at 1:22 AM Eric V. Smith wrote: > > > > > > Eric V. Smith added the comment: > > > > I agree this doesn't look like a python bug. > > > > However, if the original poster can reproduce it with a short example with > > no third party code, we could take another look. If so, please re-open this > > issue. > > > > And just because the code worked on a different version of python doesn't > > mean there's no bug in the code. I've written plenty of code where errors > > were exposed in my code when updating python. > > > > -- > > nosy: +eric.smith > > resolution: -> third party > > stage: -> resolved > > status: open -> closed > > > > ___ > > Python tracker > > <https://bugs.python.org/issue38889> > > ___ > > -- > > ___ > Python tracker > <https://bugs.python.org/issue38889> > ___ -- ___ Python tracker <https://bugs.python.org/issue38889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38889] Segmentation fault when using EPF Importer
Sebastian Szwarc added the comment: I strongly disagree. Python 2.7 is 2.7 -> if some new errors appeared after upgrading between minor version this is not expected behaviour, and therefore it means there is error in interpreter itself. upgrading from 2.7 to 2.7 is not the same as upgrading from swift 3 to swift 4. And as I said in another comment - I dont understand your tendency to "minimal example" - minimal example solves nothing because minimal != production. On production there is of course 3rd party code - tool is written by Apple and MysqlDB module by another 3rd party vendor. How can you even expect to provide minimal example in such case? Not to mention I got no errors in code - just SEGMENTATION FAULT which indicates python interpreter after upgrade doing something very bad in memory management ---> this is python issue. Or give me solution to install specific version of 2.7 that was available one year ago on Ubuntu. On Fri, Nov 22, 2019 at 1:22 AM Eric V. Smith wrote: > > > Eric V. Smith added the comment: > > I agree this doesn't look like a python bug. > > However, if the original poster can reproduce it with a short example with no > third party code, we could take another look. If so, please re-open this > issue. > > And just because the code worked on a different version of python doesn't > mean there's no bug in the code. I've written plenty of code where errors > were exposed in my code when updating python. > > -- > nosy: +eric.smith > resolution: -> third party > stage: -> resolved > status: open -> closed > > ___ > Python tracker > <https://bugs.python.org/issue38889> > ___ -- ___ Python tracker <https://bugs.python.org/issue38889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38889] Segmentation fault when using EPF Importer
Sebastian Szwarc added the comment: Previous python version didnt do segmentation fault. Code is the same as before and it worked fine previously ergo code is correct and this is python interpreter issue On Thu, Nov 21, 2019 at 11:45 PM STINNER Victor wrote: > > > STINNER Victor added the comment: > > It looks like a bug in EPF Importer: in ingestIncremental(), line 206 of > EPFIngester.py. > > I don't think that it's a bug in Python. I suggest to clos ethe issue. > > -- > nosy: +vstinner > > ___ > Python tracker > <https://bugs.python.org/issue38889> > ___ -- ___ Python tracker <https://bugs.python.org/issue38889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38889] Segmentation fault when using EPF Importer
Sebastian Szwarc added the comment: PYTHONFAULTHANDLER=1 python EPFImporter_debug.py incremental/* 2019-11-21 23:34:09,787 [INFO]: Beginning import for the following directories: incremental/itunes20191120 incremental/pricing20191120 2019-11-21 23:34:09,787 [INFO]: Importing files in incremental/itunes20191120 2019-11-21 23:34:09,788 [INFO]: Starting import of /home/sebastian/appromocje/incremental/itunes20191120... 2019-11-21 23:34:09,813 [INFO]: Beginning incremental ingest of epf_artist_video (31664 records) Fatal Python error: Segmentation fault Current thread 0x7f51058df740 (most recent call first): File "/home/sebastian/appromocje/EPFIngester.py", line 206 in ingestIncremental File "/home/sebastian/appromocje/EPFIngester.py", line 111 in ingest File "EPFImporter_debug.py", line 222 in doImport File "EPFImporter_debug.py", line 437 in main File "EPFImporter_debug.py", line 454 in Segmentation fault -- ___ Python tracker <https://bugs.python.org/issue38889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38889] Segmentation fault when using EPF Importer
New submission from Sebastian Szwarc : Python 2.7 on Ubuntu 18.04 LTS is not in latest version. Both version 2.7.14 and 15 RC1 bringing segmentation fault error. Code is the same and previously there was no error. COde is EPFImporter.py tool written by Apple to handle importing of their database dumps. -- components: Interpreter Core messages: 357229 nosy: Sebastian Szwarc priority: normal severity: normal status: open title: Segmentation fault when using EPF Importer type: crash versions: Python 2.7 ___ Python tracker <https://bugs.python.org/issue38889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
