[issue38889] Segmentation fault when using EPF Importer

[Sebastian Szwarc]

Sebastian Szwarc <seba.szwarc at gmail.com> 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
<report at bugs.python.org> wrote:
>
>
> Sebastian Szwarc <seba.szwarc at gmail.com> 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 <report at bugs.python.org> wrote:
> >
> >
> > Eric V. Smith <eric at trueblade.com> 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 <report at bugs.python.org>
> > <https://bugs.python.org/issue38889>
> > _______________________________________
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38889>
> _______________________________________

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38889>
_______________________________________