Closed sabre6 closed 4 years ago
Hi there, this looks like an m3u parsing exception rather than it being EPG / xml related. The error is sourcing from here:
https://github.com/jjssoftware/m3u-epg-editor/blob/master/m3u-epg-editor.py#L58
This means that one or more lines in the m3u file that's being read / parsed appears to not have one of the normally present attributes:
It's hard to say any more without being able to see the file but you could take a look and try and workout what's missing / where it's failing.
Hi,
Yes, the file seems to be missing a lot.
Here is a sample line – seems rather bare compared to prior ones I have seen.
http://XXXXX.YYY:8080/load/##########/73551.mpegts
Not sure how it would work missing so much. Thanks
From: Joe notifications@github.com Sent: Tuesday, October 8, 2019 1:40 PM To: jjssoftware/m3u-epg-editor m3u-epg-editor@noreply.github.com Cc: sabre6 coscob84@yahoo.com; Author author@noreply.github.com Subject: Re: [jjssoftware/m3u-epg-editor] [Support] question for error (#34)
Hi there, this looks like an m3u parsing exception rather than it being EPG / xml related. The error is sourcing from here: https://github.com/jjssoftware/m3u-epg-editor/blob/master/m3u-epg-editor.py#L58 This means that one or more lines in the m3u file that's being read / parsed appears to not have one of the normally present attributes:
I think this issue is caused by there being no fixed formal specification for what the lines within an m3u file should contain. As far as this python script is concerned, it currently makes assumptions that m3u file lines will always contain a set of well known attributes and for the most part, these attributes are usually present. In this case however they're not there and perhaps this is a question for the service / source m3u provider.
If we're able to reach the point where we believe that there's a general need for loosening the m3u parsing rules that are currently implemented in the script, I might be able to make some sort of change to cope with this sort of data.
Thank you. Lets see if they improve the structure of the files. It might take some time.
From: Joe notifications@github.com Sent: Tuesday, October 8, 2019 1:58 PM To: jjssoftware/m3u-epg-editor m3u-epg-editor@noreply.github.com Cc: sabre6 coscob84@yahoo.com; Author author@noreply.github.com Subject: Re: [jjssoftware/m3u-epg-editor] [Support] question for error (#34)
I think this issue is caused by there being no fixed formal specification for what the lines within an m3u file should contain. As far as this python script is concerned, it currently makes assumptions that m3u file lines will always contain a set of well known attributes and for the most part, these attributes are usually present. In this case however they're not there and perhaps this is a question for the service / source m3u provider. If we're able to reach the point where we believe that there's a general need for loosening the m3u parsing rules that are currently implemented in the script, I might be able to make some sort of change to cope with this sort of data. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jjssoftware/m3u-epg-editor/issues/34?email_source=notifications&email_token=AIL37SH5IRCI3WWAGVIPZ2TQNTC3VA5CNFSM4I6S3OEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAVBZGY#issuecomment-539630747 , or mute the thread https://github.com/notifications/unsubscribe-auth/AIL37SEF3W3TYRSO3MX5FUDQNTC3VANCNFSM4I6S3OEA . https://github.com/notifications/beacon/AIL37SBB2EMRPCH3YY6TT2TQNTC3VA5CNFSM4I6S3OEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAVBZGY.gif
There's nothing more to say here other than the content of the m3u file isn't complete. Closing.
Hi again,
My provider has rebuilt their playlist, and points to new location. I can play the streams from the original.xml, but when i put thru the editor, i get many lines of error saying
2019-10-08T10:48:54.123456 m3u file parse AttributeError: 'NoneType' object has no attribute 'group'
The new .xml is much more condensed than prior and may expand, but does this indicate anything that could be overcome? Thank you.