🌐 Mailman 3 August 2020 - Python-list - python.org

Video file to subtitles file
by Muskan Sanghai Aug. 27, 2020

Aug. 27, 2020

I would be really thankful if someone can suggest me how can I generate subtitles file (srt format) from a video or audio without using Google cloud and AWS.

2 1

Re: Another 2 to 3 mail encoding problem
by Chris Green Aug. 27, 2020

Aug. 27, 2020

Karsten Hilbert <Karsten.Hilbert(a)gmx.net> wrote: > > Terry Reedy <tjreedy(a)udel.edu> wrote: > > > On 8/26/2020 11:10 AM, Chris Green wrote: > > > > > > > I have a simple[ish] local mbox mail delivery module as follows:- > > > ... > > > > It has run faultlessly for many years under Python 2. I've now > > > > changed the calling program to Python 3 and while it handles most > > > > E-Mail OK I have just got the following error:- > > > > > > > > Traceback (most recent call last): > > > > File "/home/chris/.mutt/bin/filter.py", line 102, in <module> > > > > mailLib.deliverMboxMsg(dest, msg, log) > > > ... > > > > File "/usr/lib/python3.8/email/generator.py", line 406, in write > > > > self._fp.write(s.encode('ascii', 'surrogateescape')) > > > > UnicodeEncodeError: 'ascii' codec can't encode character '\ufeff' in > > > position 4: ordinal not in range(128) > > > > > > '\ufeff' is the Unicode byte-order mark. It should not be present in an > > > ascii-only 3.x string and would not normally be present in general > > > unicode except in messages like this that talk about it. Read about it, > > > for instance, at > > > https://en.wikipedia.org/wiki/Byte_order_mark > > > > > > I would catch the error and print part or all of string s to see what is > > > going on with this particular message. Does it have other non-ascii chars? > > > > > I can provoke the error simply by sending myself an E-Mail with > > accented characters in it. I'm pretty sure my Linux system is set up > > correctly for UTF8 characters, I certainly seem to be able to send and > > receive these to others and I even get to see messages in other > > scripts such as arabic, chinese, etc. > > > > The code above works perfectly in Python 2 delivering messages with > > accented (and other extended) characters with no problems at all. > > Sending myself E-Mails with accented characters works OK with the code > > running under Python 2. > > > > While an E-Mail body possibly *shouldn't* have non-ASCII characters in > > it one must be able to handle them without errors. In fact haven't > > the RFCs changed such that the message body should be 8-bit clean? > > Anyway I think the Python 3 mail handling libraries need to be able to > > pass extended characters through without errors. > > Well, '\ufeff' is not a *character* at all in much of any > sense of that word in unicode. > > It's a marker. Whatever puts it into the stream is wrong. I guess the > best one can (and should) do is to catch the exception and dump > the offending stream somewhere binary-capable and pass on a notice. What > you are receiving there very much isn't a (well-formed) e-mail message. > > I would then attempt to backwards-crawl the delivery chain to > find out where it came from. > The error seems to occur with any non-7-bit-ASCII, e.g. my accented characters gave:- File "/usr/lib/python3.8/email/generator.py", line 406, in write self._fp.write(s.encode('ascii', 'surrogateescape')) UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 34: ordinal not in range(128) It just happened that the first example was an escape. -- Chris Green ·

2 1

Re: Another 2 to 3 mail encoding problem
by Chris Green Aug. 27, 2020

Aug. 27, 2020

Richard Damon <Richard(a)damon-family.org> wrote: > On 8/27/20 4:31 AM, Chris Green wrote: > > While an E-Mail body possibly *shouldn't* have non-ASCII characters in > > it one must be able to handle them without errors. In fact haven't > > the RFCs changed such that the message body should be 8-bit clean? > > Anyway I think the Python 3 mail handling libraries need to be able to > > pass extended characters through without errors. > > Email message a fully allowed to use non-ASCII characters in them as > long as the headers indicate this. They can be encoded either as raw 8 > bit bytes on systems that are 8-bit clean, or for systems that are not, > they will need to be encoded either as base-64 or using quote-printable > encoding. These characters are to interpreted in the character set > defined (or presumed) in the header, or even some other binary object > like and image or executable if the content type isn't text. > > Because of this, the Python 3 str type is not suitable to store an email > message, since it insists on the string being Unicode encoded, but the > Python 2 str class could hold it. > Which sounds like the core of my problem[s]! :-) As I said my system (ignoring the Python issues) is all UTF8 and all seems to work well so I think it's pretty much correctly configured. When I send mail that has accented and other extended characters in it the E-Mail headers have:- Content-Type: text/plain; charset=utf-8 If I save a message like the above sent to myself it's stored using the UTF8 characters directly, I can open it with my text editor (which is also UTF8 aware) and see the characters as I entered them, there's no encoding because my system is 8-bit clean and I'm talking to myself as it were. The above is using Python 2 to handle and filter my incoming mail which, as you say, works fine. However when I try switching to Python 3 I get the errors I've been asking about, even though this is 'talking to myself' and the E-Mail message is just UTF8. -- Chris Green ·

1 0

Re: Another 2 to 3 mail encoding problem
by Chris Green Aug. 27, 2020

Aug. 27, 2020

Terry Reedy <tjreedy(a)udel.edu> wrote: > On 8/26/2020 11:10 AM, Chris Green wrote: > > > I have a simple[ish] local mbox mail delivery module as follows:- > ... > > It has run faultlessly for many years under Python 2. I've now > > changed the calling program to Python 3 and while it handles most > > E-Mail OK I have just got the following error:- > > > > Traceback (most recent call last): > > File "/home/chris/.mutt/bin/filter.py", line 102, in <module> > > mailLib.deliverMboxMsg(dest, msg, log) > ... > > File "/usr/lib/python3.8/email/generator.py", line 406, in write > > self._fp.write(s.encode('ascii', 'surrogateescape')) > > UnicodeEncodeError: 'ascii' codec can't encode character '\ufeff' in > position 4: ordinal not in range(128) > > '\ufeff' is the Unicode byte-order mark. It should not be present in an > ascii-only 3.x string and would not normally be present in general > unicode except in messages like this that talk about it. Read about it, > for instance, at > https://en.wikipedia.org/wiki/Byte_order_mark > > I would catch the error and print part or all of string s to see what is > going on with this particular message. Does it have other non-ascii chars? > I can provoke the error simply by sending myself an E-Mail with accented characters in it. I'm pretty sure my Linux system is set up correctly for UTF8 characters, I certainly seem to be able to send and receive these to others and I even get to see messages in other scripts such as arabic, chinese, etc. The code above works perfectly in Python 2 delivering messages with accented (and other extended) characters with no problems at all. Sending myself E-Mails with accented characters works OK with the code running under Python 2. While an E-Mail body possibly *shouldn't* have non-ASCII characters in it one must be able to handle them without errors. In fact haven't the RFCs changed such that the message body should be 8-bit clean? Anyway I think the Python 3 mail handling libraries need to be able to pass extended characters through without errors. -- Chris Green ·

5 6

Re: Python installer hangs in Windows 7
by jtshah619＠gmail.com Aug. 27, 2020

Aug. 27, 2020

On Monday, February 6, 2017 at 10:46:24 AM UTC+5:30, Jean-Claude Roy wrote: > I am trying to install Python 3.6.0 on a Windows 7 computer. > The download of 29.1 MB is successful and I get the nextwindow. I choose the "install now" selection and thatopens the Setup Program window. > Now the trouble starts:I get "Installing:" and the Initialization progress...and nothing else. > There is no additional disk activity, no progress on initialization, andeverything appears dead. Even after 20 minutes there is zero progress. > I've repeated this as both a user and the administrator of this Windowscomputer. I get the same results in either case. > If I go to the task manager it shows that Python 3.6.0 (32-bit) setup is running. If I try to end the task Iget the message that the program is not responding. > Do you have any suggestions as to how I can get past this? > Thank you. Uncheck the install for all users part and it will work and log into each user individually and then install.

2 1

Re: How do I do this in Python 3 (string.join())?
by Chris Green Aug. 27, 2020

Aug. 27, 2020

Cameron Simpson <cs(a)cskk.id.au> wrote: > On 26Aug2020 15:09, Chris Green <cl(a)isbd.net> wrote: > >2QdxY4RzWzUUiLuE(a)potatochowder.com wrote: > >> Join bytes objects with a byte object: > >> > >> b"\n".join(popmsg[1]) > > > >Aaahhh! Thank you (and the other reply). > > But note: joining bytes like strings is uncommon, and may indicate that > you should be working in strings to start with. Eg you may want to > convert popmsg from bytes to str and do a str.join anyway. It depends on > exactly what you're dealing with: are you doing text work, or are you > doing "binary data" work? > > I know many network protocols are "bytes-as-text, but that is > accomplished by implying an encoding of the text, eg as ASCII, where > characters all fit in single bytes/octets. > Yes, I realise that making everything a string before I start might be the 'right' way to do things but one is a bit limited by what the mail handling modules in Python provide. E.g. in this case the only (well the only ready made) way to get a POP3 message is using poplib and this just gives you a list of lines made up of "bytes as text" :- popmsg = pop3.retr(i+1) I join the lines to feed them into mailbox.mbox() to create a mbox I can analyse and also a message which can be sent using SMTP. Should I be converting to string somewhere? I guess the POP3 and SMTP libraries will cope with strings as input. Can I convert to string after the join for example? If so, how? Can I just do:- msgbytes = b'\n'.join(popmsg[1]) msgstr = str(mshbytes) (Yes, I know it can be one line, I was just being explicit). ... or do I need to stringify the lines returned by popmsg() before joining them together? Thank you for all your help and comments! (I'm a C programmer at heart, preceded by being an assembler programmer. I started programming way back in the 1970s, I'm retired now and Python is for relaxation (?) in my dotage) -- Chris Green ·

2 1

Re: Fwd: [BUG] missing ')' causes syntax error on next line
by Greg Ewing Aug. 26, 2020

Aug. 26, 2020

On 23/07/20 12:23 pm, dn wrote: > You be sure to have a nice day, now! How do you feel about you be sure to have a nice day, now? -- Greg

1 0

Re: How do I do this in Python 3 (string.join())?
by Chris Green Aug. 26, 2020

Aug. 26, 2020

2QdxY4RzWzUUiLuE(a)potatochowder.com wrote: > On 2020-08-26 at 14:22:10 +0100, > Chris Green <cl(a)isbd.net> wrote: > > > I have the following line in Python 2:- > > > > msgstr = string.join(popmsg[1], "\n") # popmsg[1] is a list containing > the lines of the message > > > > ... so I changed it to:- > > > > s = "\n" > > msgstr = s.join(popmsg[1]) # popmsg[1] is a list containing the lines of the message > > > > However this still doesn't work because popmsg[1] isn't a list of > > strings, I get the error:- > > > > TypeError: sequence item 0: expected str instance, bytes found > > > > So how do I do this? I can see clumsy ways by a loop working through > > the list in popmsg[1] but surely there must be a way that's as neat > > and elegant as the Python 2 way was? > > Join bytes objects with a byte object: > > b"\n".join(popmsg[1]) Aaahhh! Thank you (and the other reply). -- Chris Green ·

2 1

Re: Another 2 to 3 mail encoding problem
by Python Aug. 26, 2020

Aug. 26, 2020

Alexa Oña wrote: > Don’t send me more emails > > Obtener Outlook para iOS<https://aka.ms/o0ukef> You are the one spamming the mailing list with unrelated posts. STOP.

1 0

How do I do this in Python 3 (string.join())?
by Chris Green Aug. 26, 2020

Aug. 26, 2020

I have the following line in Python 2:- msgstr = string.join(popmsg[1], "\n") # popmsg[1] is a list containing the lines of the message ... so I changed it to:- s = "\n" msgstr = s.join(popmsg[1]) # popmsg[1] is a list containing the lines of the message However this still doesn't work because popmsg[1] isn't a list of strings, I get the error:- TypeError: sequence item 0: expected str instance, bytes found So how do I do this? I can see clumsy ways by a loop working through the list in popmsg[1] but surely there must be a way that's as neat and elegant as the Python 2 way was? -- Chris Green ·

4 3