From PythonList at DancesWithMice.info Sun Oct 1 00:41:29 2023 From: PythonList at DancesWithMice.info (dn) Date: Sun, 1 Oct 2023 17:41:29 +1300 Subject: type annotation vs working code In-Reply-To: References: Message-ID: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> On 01/10/2023 11.25, Karsten Hilbert via Python-list wrote: > Am Sun, Oct 01, 2023 at 09:04:05AM +1300 schrieb dn via Python-list: > >>> class WorkingSingleton(Borg): >>> >>> def __init__(self): >>> print(self.__class__.__name__, ':') >>> try: >>> self.already_initialized >>> print('already initialized') >>> return >>> >>> except AttributeError: >>> print('initializing') >>> >>> self.already_initialized = True >>> self.special_value = 42 > >>> Where's the error in my thinking (or code) ? >> >> What is your thinking? >> Specifically, what is the purpose of testing self.already_initialized? Apologies, my tending to use the "Socratic Method" with trainees (and avoiding any concept of personal-fault with others), means it can be difficult to tell if (personal*) introspection is being invited, or if I don't know the answer (and want to). * personal cf Python code introspection (hah!) > The purpose is to check whether the singleton class has been > ... initialized :-) > > The line > > self.already_initialized = True > > is misleading as to the fact that it doesn't matter at all > what self.already_initialized is set to, as long as is > exists for the next time around. > >> Isn't it generally regarded as 'best practice' to declare (and define a value for) all >> attributes in __init__()? (or equivalent) In which case, it will (presumably) be defined >> as False; and the try-except reworded to an if-else. > > I fail to see how that can differentiate between first-call > and subsequent call. +1 >> Alternately, how about using hasattr()? eg >> >> if hasattr( self.already_initialized, 'attribute_name' ): > > That does work. I am using that idiom in other children of > Borg. But that's besides the point. I was wondering why it > does not work the same way with and without the type > annotation. Annotations are for describing the attribute. In Python we don't have different instructions for declaring an object and defining it, eg INTEGER COUNTER COUNTER = 0 Thus, Python conflates both into the latter, ie counter = 0 or counter:int = 0 (both have the same effect in the Python Interpreter, the latter aims to improve documentation/reading/code-checking) Typing defines (or rather labels) the object's type. Accordingly, occurs when the object is on the LHS (Left-hand Side) of an expression (which includes function-argument lists). In this 'test for existence': in the case of WorkingSingleton(), the code-line is effectively only a RHS - see 'illegal' (below). However, the annotation caused the code-line to be re-interpreted as some sort of LHS in FailingSingleton(). - as explained (@Mats) is understood as a 'typing expression' rather than 'Python code'. Apologies: fear this a rather clumsy analysis - will welcome improvement... >> try: >> self.already_initialized >> >> line is flagged by the assorted linters, etc, in my PyCharm as: >> >> Statement seems to have no effect. > > Well, the linter simply cannot see the purpose, which is > test-of-existence. > > Question: is it a legal expression (without the typing)? > > It borders on the illegal, I suppose, as the self- > introspection capabilities of the language are being > leveraged to achieve a legal purpose. ...and so we're addressing the important question: the try-test is for existence, cf for some value. This can also be achieved by using the attribute in a legal expression, eg: self.already_initialized == True When introspecting code, if type-checkers cannot determine the purpose, is there likely to be a 'surprise factor' when a human reads it? (that's Socratic! I already hold an opinion: right or wrong) Might this remove the confusion (ref: @Mats): self.already_initialized:bool == True (not Socratic, don't know, haven't tested) > Which seems akin constructs for generating compatibility > between versions. versions of ? > It seems the answer is being pointed to in Matts response. > > It just mightily surprised me. Me too! I am slightly confused (OK, OK!) and probably because I don't have a good handle on "Borg" beyond knowing it is a Star Wars?Trek reference (apologies to the reader sucking-in his/her breath at such an utterance!). What is the intent: a class where each instance is aware of every other instance - yet the word "Singleton" implies there's only one (cf a dict full of ...)? Second move (also, slightly) off-topic: I'm broadly in-favor of typing; additionally noting that trainees find it helpful whilst developing their code-reading skills. However, am not particularly zealous in my own code, particularly if the type-checker starts 'getting picky' with some construct and taking-up time/brain-power. (which is vitally-required for writing/testing Python code!) So, (original code-sample, second line), seeing we ended-up talking about a type-definition cf attribute-definition, do you (gentle reader, as well as @OP, if inclined) feel an excess of 'boiler-plate' in the likes of: _instances:dict = {} we write ":dict", yet doesn't the RHS's "{}" communicate exactly the same (to us, and to dev.tools)? NB for reasons described, I'll habitually type the typing! But... Thanks for the thought-provoking question! -- Regards, =dn From Karsten.Hilbert at gmx.net Sun Oct 1 07:57:10 2023 From: Karsten.Hilbert at gmx.net (Karsten Hilbert) Date: Sun, 1 Oct 2023 13:57:10 +0200 Subject: type annotation vs working code In-Reply-To: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: Sorry for having conflated the core of the matter with all the Borg shenanigans, that's where I found the problem in my real code, so there :-) Consider this: #---------------------------------------------------- class Surprise: def __init__(self, with_type_annotation=False): if with_type_annotation: try: self.does_not_exist:bool print('does_not_exist does exist') except AttributeError: print('does_not_exist does not exist') return try: self.does_not_exist print('does_not_exist does exist') except AttributeError: print('does_not_exist does not exist') Surprise(with_type_annotation = False) Surprise(with_type_annotation = True) #---------------------------------------------------- Is this how it is supposed to be ? > ...and so we're addressing the important question: the try-test is for existence, cf for > some value. > > This can also be achieved by using the attribute in a legal expression, eg: ... > Might this remove the confusion (ref: @Mats): > > self.already_initialized:bool == True Not for me as that would _create_ already_initialized on the instance. It would not allow me to test for it. > >Which seems akin constructs for generating compatibility > >between versions. > > versions of ? Of the language. Sometimes one tests for existence of a given class in a module and defines said class oneself if it does not exist. But that's leading astray. > What is the intent: a class where each instance is aware of every other instance - yet > the word "Singleton" implies there's only one (cf a dict full of ...)? The latter. Regards, Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B From rosuav at gmail.com Sun Oct 1 08:21:00 2023 From: rosuav at gmail.com (Chris Angelico) Date: Sun, 1 Oct 2023 23:21:00 +1100 Subject: type annotation vs working code In-Reply-To: References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: On Sun, 1 Oct 2023 at 22:58, Karsten Hilbert via Python-list wrote: > > Sorry for having conflated the core of the matter with all > the Borg shenanigans, that's where I found the problem in my > real code, so there :-) > > Consider this: > > #---------------------------------------------------- > class Surprise: > def __init__(self, with_type_annotation=False): > if with_type_annotation: > try: > self.does_not_exist:bool > print('does_not_exist does exist') > except AttributeError: > print('does_not_exist does not exist') > return > > try: > self.does_not_exist > print('does_not_exist does exist') > except AttributeError: > print('does_not_exist does not exist') > > Surprise(with_type_annotation = False) > Surprise(with_type_annotation = True) > #---------------------------------------------------- > > Is this how it is supposed to be ? The class isn't even significant here. What you're seeing is simply that an annotation does not evaluate the expression. https://peps.python.org/pep-0526/ It's basically a coincidence that your two versions appear nearly identical. They are quite different semantically. Note that annotating the expression "self.does_not_exist" is not particularly meaningful to Python, and I've no idea what different type checkers will do with it; you normally only annotate variables that you own - so, in a function, that's function-local variables. Instead, class and instance attributes should be annotated at the class level, which would remove this apparent similarity. This is a very good reason NOT to arbitrarily add type hints to code. Type hints do not inherently improve code, and making changes just for the sake of adding them risks making semantic changes that you didn't intend. Python uses a system of gradual typing for very good reason; you should be able to add hints only to the places where they're actually useful, leaving the rest of the code untouched. ChrisA From Richard at Damon-Family.org Sun Oct 1 14:33:21 2023 From: Richard at Damon-Family.org (Richard Damon) Date: Sun, 1 Oct 2023 14:33:21 -0400 Subject: type annotation vs working code In-Reply-To: References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: <46b06982-0a90-411f-85b7-72fd9b8af1c8@Damon-Family.org> My view of the issue is that the "trick" of "evaluating" a name to see if the object has been initialized is just a tad on the "tricky" side, and the annotation/value is really incorrect. The name at the point you are annotating it, isn't really a "bool" because a bool will always have either the value "True" or "False", while for this variable, you are really testing if it exists or not. Perhaps a better method would be rather than just using the name and catching the exception, use a real already_initialized flag (set to True when you initialize), and look it up with getattr() with a default value of False. -- Richard Damon From barry at barrys-emacs.org Sun Oct 1 18:08:52 2023 From: barry at barrys-emacs.org (Barry) Date: Sun, 1 Oct 2023 23:08:52 +0100 Subject: type annotation vs working code In-Reply-To: <46b06982-0a90-411f-85b7-72fd9b8af1c8@Damon-Family.org> References: <46b06982-0a90-411f-85b7-72fd9b8af1c8@Damon-Family.org> Message-ID: <26FEAE70-0719-4D92-9174-7DC2B83F8FE1@barrys-emacs.org> > On 1 Oct 2023, at 19:36, Richard Damon via Python-list wrote: > > Perhaps a better method would be rather than just using the name and catching the exception, use a real already_initialized flag (set to True when you initialize), and look it up with getattr() with a default value of False. I would use a class variable not an instance variable. class OnlyOne: sole_instance = None def __init__(self): assert OnlyOne.sole_instance is None OnlyOne.sole_instance = self Barry From rosuav at gmail.com Sun Oct 1 18:21:42 2023 From: rosuav at gmail.com (Chris Angelico) Date: Mon, 2 Oct 2023 09:21:42 +1100 Subject: type annotation vs working code In-Reply-To: <26FEAE70-0719-4D92-9174-7DC2B83F8FE1@barrys-emacs.org> References: <46b06982-0a90-411f-85b7-72fd9b8af1c8@Damon-Family.org> <26FEAE70-0719-4D92-9174-7DC2B83F8FE1@barrys-emacs.org> Message-ID: On Mon, 2 Oct 2023 at 09:10, Barry via Python-list wrote: > > > > > On 1 Oct 2023, at 19:36, Richard Damon via Python-list wrote: > > > > Perhaps a better method would be rather than just using the name and catching the exception, use a real already_initialized flag (set to True when you initialize), and look it up with getattr() with a default value of False. > I would use a class variable not an instance variable. > > class OnlyOne: > sole_instance = None > def __init__(self): > assert OnlyOne.sole_instance is None > OnlyOne.sole_instance = self > Agreed, except that this should be an if-raise rather than an assert. ChrisA From jenkris at tutanota.com Sun Oct 1 18:04:28 2023 From: jenkris at tutanota.com (Jen Kris) Date: Mon, 2 Oct 2023 00:04:28 +0200 (CEST) Subject: How to write list of integers to file with struct.pack_into? Message-ID: Iwant to write a list of 64-bit integers to a binary file. Everyexample I have seen in my research convertsit to .txt, but I want it in binary. I wrote this code,based on some earlier work I have done: buf= bytes((len(qs_array)) * 8) foroffset in range(len(qs_array)): item_to_write= bytes(qs_array[offset]) struct.pack_into(buf," Finally, it?s final! The final release of Python 3.12.0 (final) is here! https://www.python.org/downloads/release/python-3120/ This is the stable release of Python 3.12.0 Python 3.12.0 is the newest major release of the Python programming language, and it contains many new features and optimizations. Major new features of the 3.12 series, compared to 3.11 New features - More flexible f-string parsing , allowing many things previously disallowed (PEP 701 ). - Support for the buffer protocol in Python code (PEP 688 ). - A new debugging/profiling API (PEP 669 ). - Support for isolated subinterpreters with separate Global Interpreter Locks (PEP 684 ). - Even more improved error messages . More exceptions potentially caused by typos now make suggestions to the user. - Support for the Linux perf profiler to report Python function names in traces. - Many large and small performance improvements (like PEP 709 and support for the BOLT binary optimizer), delivering an estimated 5% overall performance improvement. Type annotations - New type annotation syntax for generic classes (PEP 695 ). - New override decorator for methods (PEP 698 ). Deprecations - The deprecated wstr and wstr_length members of the C implementation of unicode objects were removed, per PEP 623 . - In the unittest module, a number of long deprecated methods and classes were removed. (They had been deprecated since Python 3.1 or 3.2). - The deprecated smtpd and distutils modules have been removed (see PEP 594 and PEP 632 . The setuptools package continues to provide the distutils module. - A number of other old, broken and deprecated functions, classes and methods have been removed. - Invalid backslash escape sequences in strings now warn with SyntaxWarning instead of DeprecationWarning, making them more visible. (They will become syntax errors in the future.) - The internal representation of integers has changed in preparation for performance enhancements. (This should not affect most users as it is an internal detail, but it may cause problems for Cython-generated code.) For more details on the changes to Python 3.12, see What?s new in Python 3.12 . More resources - Online Documentation . - PEP 693 , the Python 3.12 Release Schedule. - Report bugs via GitHub Issues . - Help fund Python and its community . And now for something completely different They have no need of our help So do not tell me These haggard faces could belong to you or me Should life have dealt a different hand We need to see them for who they really are Chancers and scroungers Layabouts and loungers With bombs up their sleeves Cut-throats and thieves They are not Welcome here We should make them Go back to where they came from They cannot Share our food Share our homes Share our countries Instead let us Build a wall to keep them out It is not okay to say These are people just like us A place should only belong to those who are born there Do not be so stupid to think that The world can be looked at another way (now read from bottom to top) Refugees , by Brian Bilston . We hope you enjoy the new releases! Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation . Your release team, Thomas Wouters Ned Deily Steve Dower ?ukasz Langa -- Thomas Wouters From barry at barrys-emacs.org Mon Oct 2 12:08:35 2023 From: barry at barrys-emacs.org (Barry) Date: Mon, 2 Oct 2023 17:08:35 +0100 Subject: How to write list of integers to file with struct.pack_into? In-Reply-To: References: Message-ID: <72F653DA-5336-4500-86F1-E7163B7FA511@barrys-emacs.org> On 2 Oct 2023, at 16:02, Jen Kris via Python-list wrote: Iwant to write a list of 64-bit integers to a binary file. ?Everyexample I have seen in my research convertsit to .txt, but I want it in binary. ?I wrote this code,based on some earlier work I have done: buf= bytes((len(qs_array)) * 8) buf is not writable so cannot be used by pack_into. I think you need to use bytesarray not bytes. foroffset in range(len(qs_array)): item_to_write= bytes(qs_array[offset]) struct.pack_into(buf," Hi, I have an issue since about 5 months now. Python 3.12.0 venv not working with psycopg2 on Windows. I created 2 issues on GitHub but they were closed. I checked today with the new Python release but it's still not working. https://github.com/psycopg/psycopg2/issues/1578 https://github.com/python/cpython/issues/104830 Thanks, Uri. ???? uri at speedy.net From python at mrabarnett.plus.com Mon Oct 2 13:06:51 2023 From: python at mrabarnett.plus.com (MRAB) Date: Mon, 2 Oct 2023 18:06:51 +0100 Subject: How to write list of integers to file with struct.pack_into? In-Reply-To: References: Message-ID: On 2023-10-01 23:04, Jen Kris via Python-list wrote: > > Iwant to write a list of 64-bit integers to a binary file. Everyexample I have seen in my research convertsit to .txt, but I want it in binary. I wrote this code,based on some earlier work I have done: > > buf= bytes((len(qs_array)) * 8) > > foroffset in range(len(qs_array)): > > item_to_write= bytes(qs_array[offset]) > > struct.pack_into(buf," > ButI get the error "struct.error: embedded null character." > > Maybethere's a better way to do this? > You can't pack into a 'bytes' object because it's immutable. The simplest solution I can think of is: buf = struct.pack("<%sQ" % len(qs_array), *qs_array) From jenkris at tutanota.com Mon Oct 2 13:33:58 2023 From: jenkris at tutanota.com (Jen Kris) Date: Mon, 2 Oct 2023 19:33:58 +0200 (CEST) Subject: How to write list of integers to file with struct.pack_into? In-Reply-To: References: Message-ID: Thanks very much, MRAB.? I just tried that and it works.? What frustrated me is that every research example I found writes integers as strings.? That works -- sort of -- but it requires re-casting each string to integer when reading the file.? If I'm doing binary work I don't want the extra overhead, and it's more difficult yet if I'm using the Python integer output in a C program.? Your solution solves those problems.? Oct 2, 2023, 17:11 by python-list at python.org: > On 2023-10-01 23:04, Jen Kris via Python-list wrote: > >> >> Iwant to write a list of 64-bit integers to a binary file. Everyexample I have seen in my research convertsit to .txt, but I want it in binary. I wrote this code,based on some earlier work I have done: >> >> buf= bytes((len(qs_array)) * 8) >> >> foroffset in range(len(qs_array)): >> >> item_to_write= bytes(qs_array[offset]) >> >> struct.pack_into(buf,"> >> ButI get the error "struct.error: embedded null character." >> >> Maybethere's a better way to do this? >> > You can't pack into a 'bytes' object because it's immutable. > > The simplest solution I can think of is: > > buf = struct.pack("<%sQ" % len(qs_array), *qs_array) > -- > https://mail.python.org/mailman/listinfo/python-list > From dieter at handshake.de Mon Oct 2 13:47:30 2023 From: dieter at handshake.de (Dieter Maurer) Date: Mon, 2 Oct 2023 19:47:30 +0200 Subject: How to write list of integers to file with struct.pack_into? In-Reply-To: References: Message-ID: <25883.562.500892.142384@ixdm.fritz.box> Jen Kris wrote at 2023-10-2 00:04 +0200: >Iwant to write a list of 64-bit integers to a binary file. Everyexample I have seen in my research convertsit to .txt, but I want it in binary. I wrote this code,based on some earlier work I have done: > >buf= bytes((len(qs_array)) * 8) > >for offset in range(len(qs_array)): > item_to_write= bytes(qs_array[offset]) > struct.pack_into(buf," >But I get the error "struct.error: embedded null character." You made a lot of errors: * the signature of `struct.pack_into` is `(format, buffer, offset, v1, v2, ...)`. Especially: `format` is the first, `buffer` the second argument * In your code, `offset` is `0`, `1`, `2`, ... but it should be `0 *8`, `1 * 8`, `2 * 8`, ... * The `vi` should be something which fits with the format: integers in your case. But you pass bytes. Try `struct.pack_into(" References: <25883.562.500892.142384@ixdm.fritz.box> Message-ID: Dieter, thanks for your comment that: * In your code, `offset` is `0`, `1`, `2`, ... but it should be `0 *8`, `1 * 8`, `2 * 8`, ... But you concluded with essentially the same solution proposed by MRAB, so that would obviate the need to write item by item because it writes the whole buffer at once.? Thanks for your help.? Oct 2, 2023, 17:47 by dieter at handshake.de: > Jen Kris wrote at 2023-10-2 00:04 +0200: > >Iwant to write a list of 64-bit integers to a binary file. Everyexample I have seen in my research convertsit to .txt, but I want it in binary. I wrote this code,based on some earlier work I have done: > >> >> > >buf= bytes((len(qs_array)) * 8) > >> >> > >for offset in range(len(qs_array)): > >> item_to_write= bytes(qs_array[offset]) >> struct.pack_into(buf,"> > >But I get the error "struct.error: embedded null character." > > You made a lot of errors: > > * the signature of `struct.pack_into` is > `(format, buffer, offset, v1, v2, ...)`. > Especially: `format` is the first, `buffer` the second argument > > * In your code, `offset` is `0`, `1`, `2`, ... > but it should be `0 *8`, `1 * 8`, `2 * 8`, ... > > * The `vi` should be something which fits with the format: > integers in your case. But you pass bytes. > > Try `struct.pack_into(" instead of your loop. > > > Next time: carefully read the documentation and think carefully > about the types involved. > From hjp-python at hjp.at Mon Oct 2 15:49:28 2023 From: hjp-python at hjp.at (Peter J. Holzer) Date: Mon, 2 Oct 2023 21:49:28 +0200 Subject: Python 3.12.0 venv not working with psycopg2 In-Reply-To: References: Message-ID: <20231002194928.exfcytf2gofh3usw@hjp.at> On 2023-10-02 19:44:12 +0300, ???? via Python-list wrote: > I have an issue since about 5 months now. Python 3.12.0 venv not working > with psycopg2 on Windows. I created 2 issues on GitHub but they were > closed. I checked today with the new Python release but it's still not > working. > > https://github.com/psycopg/psycopg2/issues/1578 > https://github.com/python/cpython/issues/104830 You wil have to come up with a *minimal* test case which reproduces the problem. Expecting people to download and test your massive application is unreasonable. hp -- _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp at hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From jenkris at tutanota.com Mon Oct 2 11:06:08 2023 From: jenkris at tutanota.com (Jen Kris) Date: Mon, 2 Oct 2023 17:06:08 +0200 (CEST) Subject: How to write list of integers to file with struct.pack_into? Message-ID: My previous message just went up -- sorry for the mangled formatting.? Here it is properly formatted: I want to write a list of 64-bit integers to a binary file.? Every example I have seen in my research converts it to .txt, but I want it in binary.? I wrote this code, based on some earlier work I have done: ??? buf = bytes((len(qs_array)) * 8) ??? for offset in range(len(qs_array)): ??????? item_to_write = bytes(qs_array[offset]) ??????? struct.pack_into(buf, " References: Message-ID: Jen Kris via Python-list schreef op 2/10/2023 om 17:06: > My previous message just went up -- sorry for the mangled formatting.? Here it is properly formatted: > > I want to write a list of 64-bit integers to a binary file.? Every example I have seen in my research converts it to .txt, but I want it in binary.? I wrote this code, based on some earlier work I have done: > > ??? buf = bytes((len(qs_array)) * 8) > ??? for offset in range(len(qs_array)): > ??????? item_to_write = bytes(qs_array[offset]) > ??????? struct.pack_into(buf, " References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: On 02/10/2023 00.57, Karsten Hilbert via Python-list wrote: > Sorry for having conflated the core of the matter with all > the Borg shenanigans, that's where I found the problem in my > real code, so there :-) The first question when dealing with the Singleton Pattern is what to do when more than one instantiation is attempted: - silently return the first instance - raise an exception The 'problem' interpreting the original code was that the 'Borg Pattern', is not limited in number, but is where some class-attribute list (or dict) is used to enable all instances to be aware of each of the others (IIRC). Is choosing names as important as selecting/implementing smart algorithms? > Consider this: > > #---------------------------------------------------- > class Surprise: > def __init__(self, with_type_annotation=False): > if with_type_annotation: > try: > self.does_not_exist:bool > print('does_not_exist does exist') > except AttributeError: > print('does_not_exist does not exist') > return > > try: > self.does_not_exist > print('does_not_exist does exist') > except AttributeError: > print('does_not_exist does not exist') > > Surprise(with_type_annotation = False) > Surprise(with_type_annotation = True) > #---------------------------------------------------- > > Is this how it is supposed to be ? Wasn't this answered earlier? (@Mats) That self.does_not_exist:bool isn't interpreted by Python to mean the same as self.does_not_exist. >> ...and so we're addressing the important question: the try-test is for existence, cf for >> some value. >> >> This can also be achieved by using the attribute in a legal expression, eg: > ... >> Might this remove the confusion (ref: @Mats): >> >> self.already_initialized:bool == True > > Not for me as that would _create_ already_initialized on the > instance. It would not allow me to test for it. > >>> Which seems akin constructs for generating compatibility >>> between versions. >> >> versions of ? > > Of the language. Sometimes one tests for existence of a given > class in a module and defines said class oneself if it does > not exist. But that's leading astray. > >> What is the intent: a class where each instance is aware of every other instance - yet >> the word "Singleton" implies there's only one (cf a dict full of ...)? > > The latter. and so, returning to the matter of 'readability': - the name "Borg" de-railed comprehension - _instances:dict = {} implied the tracking of more than one - should the class have been called either; class SomethingSingleton(): or a Singleton() class defined, which is then sub-classed, ie class Something( Singleton ): in order to better communicate the coder's intent to the reader? - from there, plenty of 'templates' exist for Singletons, so why do something quite different/alien to the reader? (thus concurring with @Richard: "tricky" subverts 'readability') - is it better to use a technique which 'we' will recognise, or to ask 'us' to comprehend something 'new'? (unless the 'new' is taking-advantage of a recent extension to the language, eg switch; to justify 'trail-blazing' a new/improved/replacement 'best practice') - part of the 'tricky' seems to be an attempt to assess using an instance-attribute, rather than a class-attribute. If the :bool (or whichever) typing-annotation is added to a class-attribute (eg _instance), will the problem arise? - does the sequence _instance = False ... if not cls._instance: ie the explicit version if cls._instance == False: measure 'existence' or a value? - does the sequence _instance = None ... if not cls._instance: ie the explicit version: if cls._instance is None: measure 'existence' or identity? (indeed, are they more-or-less the same concept?) - do the *attr() functions test for 'existence'? (that said, most of the code-examples I spotted, in reading-up on this, use either None or False - et tu Brute!) Speaking of reading-up: - am wondering where PEP 661 - Sentinel Values is 'going'? - this article (https://python-patterns.guide/gang-of-four/singleton/) mentions that the original GoF Singleton Pattern preceded Python (particularly Python 3 classes). Also, that Python doesn't have complications present in C++. It further discusses "several drawbacks", which also champion 'readability' over 'trick' or 'sophistication'. I think you'll enjoy it! -- Regards, =dn From rosuav at gmail.com Wed Oct 4 02:41:24 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 4 Oct 2023 17:41:24 +1100 Subject: type annotation vs working code In-Reply-To: References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: On Wed, 4 Oct 2023 at 15:27, dn via Python-list wrote: > - should the class have been called either; > > class SomethingSingleton(): > > or a Singleton() class defined, which is then sub-classed, ie > > class Something( Singleton ): > > in order to better communicate the coder's intent to the reader? TBH, I don't think it's right to have a Singleton class which is subclassed by a bunch of different singletons. They aren't really subclasses of the same class. I could imagine Singleton being a metaclass, perhaps, but otherwise, they're not really similar to each other. ChrisA From greg.ewing at canterbury.ac.nz Wed Oct 4 02:44:19 2023 From: greg.ewing at canterbury.ac.nz (Greg Ewing) Date: Wed, 4 Oct 2023 19:44:19 +1300 Subject: type annotation vs working code In-Reply-To: References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: On 4/10/23 5:25 pm, dn wrote: > The first question when dealing with the Singleton Pattern is what to do > when more than one instantiation is attempted My preferred way of handling singletons is not to expose the class itself, but a function that creates an instance the first time it's called, and returns that instance subsequently. The problem then doesn't arise. -- Greg From rosuav at gmail.com Wed Oct 4 02:49:44 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 4 Oct 2023 17:49:44 +1100 Subject: type annotation vs working code In-Reply-To: References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: On Wed, 4 Oct 2023 at 17:47, Greg Ewing via Python-list wrote: > > On 4/10/23 5:25 pm, dn wrote: > > The first question when dealing with the Singleton Pattern is what to do > > when more than one instantiation is attempted > > My preferred way of handling singletons is not to expose the class > itself, but a function that creates an instance the first time it's > called, and returns that instance subsequently. The problem then > doesn't arise. > That's one option. Personally, I don't use them very much, but if I do, it's usually actually as a class that never gets instantiated: class PileOfAttributes: x = 1 y = 2 spam = "ham" ChrisA From PythonList at DancesWithMice.info Wed Oct 4 04:05:29 2023 From: PythonList at DancesWithMice.info (dn) Date: Wed, 4 Oct 2023 21:05:29 +1300 Subject: type annotation vs working code In-Reply-To: References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: <0a9e9d76-aeb4-4e68-84bb-927ffbd63859@DancesWithMice.info> On 04/10/2023 19.41, Chris Angelico via Python-list wrote: > On Wed, 4 Oct 2023 at 15:27, dn via Python-list wrote: >> - should the class have been called either; >> >> class SomethingSingleton(): >> >> or a Singleton() class defined, which is then sub-classed, ie >> >> class Something( Singleton ): >> >> in order to better communicate the coder's intent to the reader? > > TBH, I don't think it's right to have a Singleton class which is > subclassed by a bunch of different singletons. They aren't really > subclasses of the same class. I could imagine Singleton being a > metaclass, perhaps, but otherwise, they're not really similar to each > other. I'm with you on this - should have made Singleton() an ABC. Yes, would only be a skeleton around which concrete singleton classes could be built. Like you, I v.rarely use them - but which means that the ABC is useful because it would save me from having to remember the curly-bits all-over-again... -- Regards, =dn From roland.em0001 at googlemail.com Wed Oct 4 15:08:56 2023 From: roland.em0001 at googlemail.com (=?UTF-8?Q?Roland_M=c3=bcller?=) Date: Wed, 4 Oct 2023 22:08:56 +0300 Subject: Unable to completely remove Python 3.10.9 (64 bit) from Computer In-Reply-To: References: Message-ID: <21adf112-9045-e0ea-1c3f-12d97968de3b@googlemail.com> On 25.9.2023 19.58, Pau Vilchez via Python-list wrote: > Hello Python Team, > > > > I am somehow unable to completely remove Python 3.10.9 (64 Bit) from my > computer. I have tried deleting the Appdata folder then repairing and then > uninstalling but it still persists in the remove/add program function in > windows 10. I am just trying to reinstall it because I didn?t add it to > the path correctly, any help is greatly appreciated. > This is a Windows issue and not actually Python -specific. It may happen to every program you install. If something is installed by the normal way using the W10 installer it should be removable too. If not there should be some error. > > > Very Respectfully, > > > > Pau Vilchez > > From Karsten.Hilbert at gmx.net Wed Oct 4 17:38:40 2023 From: Karsten.Hilbert at gmx.net (Karsten Hilbert) Date: Wed, 4 Oct 2023 23:38:40 +0200 Subject: type annotation vs working code In-Reply-To: References: <4f1c9568-3850-4847-b357-740f79b0a79b@DancesWithMice.info> Message-ID: Am Wed, Oct 04, 2023 at 05:25:04PM +1300 schrieb dn via Python-list: > The first question when dealing with the Singleton Pattern is what to do when more than > one instantiation is attempted: > > - silently return the first instance This, in my case. > and so, returning to the matter of 'readability': > > - the name "Borg" de-railed comprehension > > - _instances:dict = {} implied the tracking of more than one Child classes, yes, each being a Singleton. > or a Singleton() class defined, which is then sub-classed, ie > > class Something( Singleton ): Could have been but the legacy codebase came with Borg ... > - from there, plenty of 'templates' exist for Singletons, ... which was taken from the Web ages ago. > - this article (https://python-patterns.guide/gang-of-four/singleton/) Reading. Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B From mats at wichmann.us Thu Oct 5 14:50:55 2023 From: mats at wichmann.us (Mats Wichmann) Date: Thu, 5 Oct 2023 12:50:55 -0600 Subject: Unable to completely remove Python 3.10.9 (64 bit) from Computer In-Reply-To: <21adf112-9045-e0ea-1c3f-12d97968de3b@googlemail.com> References: <21adf112-9045-e0ea-1c3f-12d97968de3b@googlemail.com> Message-ID: On 10/4/23 13:08, Roland M?ller via Python-list wrote: > > On 25.9.2023 19.58, Pau Vilchez via Python-list wrote: >> ??? Hello Python Team, >> >> >> ??? I am somehow unable to completely remove Python 3.10.9 (64 Bit) >> from my >> ??? computer. I have tried deleting the Appdata folder then repairing >> and then >> ??? uninstalling but it still persists in the remove/add program >> function in >> ??? windows 10. I am just trying to reinstall it because I didn?t add >> it to >> ??? the path correctly, any help is greatly appreciated. >> > This is a Windows issue and not actually Python -specific. It may happen > to every program you install. > > If something is installed by the normal way using the W10 installer it > should be removable too. If not there should be some error. Python seems somewhat prone to this on Windows, I recently had a case where the original version of two upgraded Pythons were still stuck sitting in the Programs (which I didn't notice originally), so it looked like 3.11.1 and 3.11.4 were *both* installed, as well as two 3.10 versions - this was an otherwise well-behaving system, so it was quite mystifying. You can run uninstall directly from the installer file (download it again if you need to). This may work better than selecting "modify" from the Programs applet - a "stuck" installation may still be missing some piece of information even if you tried to repair it. If things are *really* stuck Microsoft provide a tool which I've used with success on really messed up installation info. https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d From sripunyahorayangurabr at gmail.com Mon Oct 9 07:44:09 2023 From: sripunyahorayangurabr at gmail.com (=?UTF-8?B?4LiX4Lij4Li54Lin4Lit4Lil4LmA4Lil4LiXIOC5gOC4guC5ieC4suC4quC4ueC5iOC4o+C4sA==?= =?UTF-8?B?4Lia4Lia4LmA4Lin4LmH4Lia4LiV4Lij4LiH?=) Date: Mon, 9 Oct 2023 04:44:09 -0700 (PDT) Subject: Fatal Python error: Py_Initialize: can't initialize sys standard streams Message-ID: Fatal Python error: Py_Initialize: can't initialize sys standard streams ? ???????????? https://bit.ly/cup88sb?43oqf=register ? ??????????? https://bit.ly/cup88rb?43oqf=register ? ????????? https://bit.ly/cup88lb?43oqf=register ? ???????????? https://bit.ly/cup88pb?43oqf=register From sowmya.thri06 at gmail.com Mon Oct 9 12:26:21 2023 From: sowmya.thri06 at gmail.com (Thri sowmya.G) Date: Mon, 9 Oct 2023 21:56:21 +0530 Subject: regarding installation of python version Message-ID: <06EC9CEF-020F-4A7D-8CCE-27AC8BDEC126@hxcore.ol> ? The problem is how many times I have uninstalled the python version but always it is showing the ?same version ?after the installation ?of new version too ?.But in all control panel and file explorer at everywhere the system showing that the old ?version got uninstalled ?but again in command prompt or terminal it is in ?same old version. I hope I will get a solution from you. ??????????????????? ??????????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????Thank you. ? From jsf80238 at gmail.com Mon Oct 9 14:09:48 2023 From: jsf80238 at gmail.com (Jason Friedman) Date: Mon, 9 Oct 2023 12:09:48 -0600 Subject: Fatal Python error: Py_Initialize: can't initialize sys standard streams In-Reply-To: References: Message-ID: > > > Fatal Python error: Py_Initialize: can't initialize sys standard streams > ? ???????????? > https://bit.ly/cup88sb?43oqf=register > > ? ??????????? > https://bit.ly/cup88rb?43oqf=register > > ? ????????? > https://bit.ly/cup88lb?43oqf=register > > ? ???????????? > https://bit.ly/cup88pb?43oqf=register > > Do any of these help? https://www.google.com/search?q=Fatal+Python+error%3A+Py_Initialize%3A+can%27t+initialize+sys+standard+streams&oq=Fatal+Python+error%3A+Py_Initialize%3A+can%27t+initialize+sys+standard+streams If not, I advise posting your actual code rather than links to your code. Many people are afraid to click on unknown links. And that advice is a subset of the advice posted at http://www.catb.org/~esr/faqs/smart-questions.html. From sravan.chitikesi at iprotechs.com Mon Oct 9 14:14:13 2023 From: sravan.chitikesi at iprotechs.com (Sravan Kumar Chitikesi) Date: Mon, 9 Oct 2023 23:44:13 +0530 Subject: regarding installation of python version In-Reply-To: <06EC9CEF-020F-4A7D-8CCE-27AC8BDEC126@hxcore.ol> References: <06EC9CEF-020F-4A7D-8CCE-27AC8BDEC126@hxcore.ol> Message-ID: I can help you On Mon, 9 Oct 2023, 11:15 pm Thri sowmya.G via Python-list, < python-list at python.org> wrote: > > > The problem is how many times I have uninstalled the python version but > always it is showing the same version after the installation of new > version too .But in all control panel and file explorer at everywhere > the > system showing that the old version got uninstalled but again in > command > prompt or terminal it is in same old version. I hope I will get a > solution from you. > > > > > > Thank you. > > > -- > https://mail.python.org/mailman/listinfo/python-list > From miked at dewhirst.com.au Mon Oct 9 18:16:08 2023 From: miked at dewhirst.com.au (Mike Dewhirst) Date: Tue, 10 Oct 2023 09:16:08 +1100 Subject: regarding installation of python version In-Reply-To: <06EC9CEF-020F-4A7D-8CCE-27AC8BDEC126@hxcore.ol> Message-ID: <4S4DD752pLznVHc@mail.python.org> Look in Windows Settings, About, Advanced system settings, Environment variables and you will see two sets of variables. One for the system and one set for yourself.Select Path and click [Edit]Carefully remove all references to Python in both sets.In theory you can now install a new Python and it will update your environment variables and that will be the Python you use.Otherwise, find the Python executable (python.exe) you wish to use and call it in your terminal using its full path.Good luckMike--(Unsigned mail from my phone) -------- Original message --------From: "Thri sowmya.G via Python-list" Date: 10/10/23 04:43 (GMT+10:00) To: python-list at python.org Subject: regarding installation of python version ?? ??? The problem is how many times I have uninstalled the python version but?? always it is showing the ?same version ?after the installation ?of new?? version too ?.But in all control panel and file explorer at everywhere the?? system showing that the old ?version got uninstalled ?but again in command?? prompt or terminal it is in ?same old version. I hope I will get a?? solution from you.?? ????????????????????? ????????????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????Thank you.?? ?-- https://mail.python.org/mailman/listinfo/python-list From cl at isbd.net Thu Oct 12 05:21:07 2023 From: cl at isbd.net (Chris Green) Date: Thu, 12 Oct 2023 10:21:07 +0100 Subject: Is a Python event polled or interrupt driven? Message-ID: <3dqkvj-vblf3.ln1@esprimo.zbmc.eu> In the following code is the event polled by the Python process running the code or is there something cleverer going on such that Python sees an interrupt when the input goes high (or low)? import Adafruit_BBIO.GPIO as GPIO Pin = "P8_8" GPIO.setup(Pin, GPIO.IN) # set GPIO25 as input (button) def my_callback(channel): if GPIO.input(Pin): print "Rising edge detected on 25" else: # if port 25 != 1 print "Falling edge detected on 25" GPIO.add_event_detect(Pin, GPIO.BOTH, my_callback, 1) -- Chris Green ? From rosuav at gmail.com Thu Oct 12 11:07:14 2023 From: rosuav at gmail.com (Chris Angelico) Date: Fri, 13 Oct 2023 02:07:14 +1100 Subject: Is a Python event polled or interrupt driven? In-Reply-To: <3dqkvj-vblf3.ln1@esprimo.zbmc.eu> References: <3dqkvj-vblf3.ln1@esprimo.zbmc.eu> Message-ID: On Fri, 13 Oct 2023 at 01:48, Chris Green via Python-list wrote: > > In the following code is the event polled by the Python process > running the code or is there something cleverer going on such that > Python sees an interrupt when the input goes high (or low)? > This isn't something inherent to Python; it's the specific behaviour of the library you're using. So I dug through that library a bit, and ended up here: https://github.com/adafruit/adafruit-beaglebone-io-python/blob/cf306ed7f9f24111d0949dd60ac232e81241bffe/source/event_gpio.c#L753 which starts a thread: https://github.com/adafruit/adafruit-beaglebone-io-python/blob/cf306ed7f9f24111d0949dd60ac232e81241bffe/source/event_gpio.c#L662 which appears to make use of epoll for efficient event handling. Edge detection itself seems to be done here: https://github.com/adafruit/adafruit-beaglebone-io-python/blob/cf306ed7f9f24111d0949dd60ac232e81241bffe/source/event_gpio.c#L522 I don't know enough about the architecture of the BeagleBone to be certain, but my reading of it is that most of the work of edge detection is done by the OS kernel, which then sends the Adafruit handler a notification via a file descriptor. The secondary thread waits for those messages (which can be done very efficiently), and in turn calls the Python callbacks. In other words, the "something cleverer" is all inside the OS kernel, and yes, in effect, it's an interrupt. ChrisA From cl at isbd.net Thu Oct 12 13:27:31 2023 From: cl at isbd.net (Chris Green) Date: Thu, 12 Oct 2023 18:27:31 +0100 Subject: Is a Python event polled or interrupt driven? References: <3dqkvj-vblf3.ln1@esprimo.zbmc.eu> Message-ID: <3tmlvj-i0dh3.ln1@esprimo.zbmc.eu> Chris Angelico wrote: > On Fri, 13 Oct 2023 at 01:48, Chris Green via Python-list > wrote: > > > > In the following code is the event polled by the Python process > > running the code or is there something cleverer going on such that > > Python sees an interrupt when the input goes high (or low)? > > > > This isn't something inherent to Python; it's the specific behaviour > of the library you're using. So I dug through that library a bit, and > ended up here: > > https://github.com/adafruit/adafruit-beaglebone-io-python/blob/cf306ed7f9f24111d0949dd60ac232e81241bffe/source/event_gpio.c#L753 > > > which starts a thread: > > https://github.com/adafruit/adafruit-beaglebone-io-python/blob/cf306ed7f9f24111d0949dd60ac232e81241bffe/source/event_gpio.c#L662 > > > which appears to make use of epoll for efficient event handling. Edge > detection itself seems to be done here: > > https://github.com/adafruit/adafruit-beaglebone-io-python/blob/cf306ed7f9f24111d0949dd60ac232e81241bffe/source/event_gpio.c#L522 > > > I don't know enough about the architecture of the BeagleBone to be > certain, but my reading of it is that most of the work of edge > detection is done by the OS kernel, which then sends the Adafruit > handler a notification via a file descriptor. The secondary thread > waits for those messages (which can be done very efficiently), and in > turn calls the Python callbacks. > > In other words, the "something cleverer" is all inside the OS kernel, > and yes, in effect, it's an interrupt. > Wow! Thanks for doing all that research. It sounds as if it may be more efficient than I thought so may be fast enough. I guess I'll just have to try some actual code (and hardware) and see how it goes. Thanks again! -- Chris Green ? From thomas at python.org Fri Oct 13 08:33:16 2023 From: thomas at python.org (Thomas Wouters) Date: Fri, 13 Oct 2023 14:33:16 +0200 Subject: Python 3.13.0 alpha 1 now available. Message-ID: It?s not a very exciting release (yet), but it?s time for the first alpha of Python 3.13 anyway! https://www.python.org/downloads/release/python-3130a1/ *This is an early developer preview of Python 3.13* Major new features of the 3.13 series, compared to 3.12 Python 3.13 is still in development. This release, 3.13.0a1 is the first of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2024-05-07) and, if necessary, may be modified or deleted up until the release candidate phase (2024-07-30). Please keep in mind that this is a preview release and its use is *not* recommended for production environments. Many new features for Python 3.13 are still being planned and written. The most notable change so far are new deprecations , most of which are scheduled for removal from Python 3.15 or 3.16 (Hey, *fellow core developer,* if a feature you find important is missing from this list, let Thomas know .) The next pre-release of Python 3.13 will be 3.13.0a2, currently scheduled for 2023-11-21. More resources - Online Documentation - PEP 719 , 3.13 Release Schedule - Report bugs at https://github.com/python/cpython/issues. - Help fund Python and its community . Enjoy the new releases Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. Regards from lovely Czechia, Your release team, Thomas Wouters Ned Deily Steve Dower ?ukasz Langa -- Thomas Wouters From bongoferno at gmail.com Mon Oct 16 19:35:26 2023 From: bongoferno at gmail.com (Bongo Ferno) Date: Mon, 16 Oct 2023 16:35:26 -0700 (PDT) Subject: Where I do ask for a new feature Message-ID: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> Where I can ask python developers for a new feature? This feature would allow us to create short aliases for long object paths, similar to the with statement. This would make code more readable and maintainable. For example, if we have a long object like "MyObject.stuff.longStuff.SubObject", we could create a short alias for it like this: aliasView my_object.stuff.long_stuff.sub_object as short_view #Now, we can operate with the nested object using the short alias: print(short_view.some_method()) This is much more concise and readable than having to write out the full object path every time. From rosuav at gmail.com Mon Oct 16 21:57:25 2023 From: rosuav at gmail.com (Chris Angelico) Date: Tue, 17 Oct 2023 12:57:25 +1100 Subject: Where I do ask for a new feature In-Reply-To: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> Message-ID: On Tue, 17 Oct 2023 at 12:55, Bongo Ferno via Python-list wrote: > > Where I can ask python developers for a new feature? > > This feature would allow us to create short aliases for long object paths, similar to the with statement. This would make code more readable and maintainable. > > For example, if we have a long object like "MyObject.stuff.longStuff.SubObject", we could create a short alias for it like this: > > > aliasView my_object.stuff.long_stuff.sub_object as short_view > #Now, we can operate with the nested object using the short alias: > print(short_view.some_method()) > > This is much more concise and readable than having to write out the full object path every time. > You can actually just do that with simple assignment! short_view = my_object.stuff.long_stuff.sub_object print(short_view.some_method()) It'll work! ChrisA From david at uilix.com Tue Oct 17 14:31:05 2023 From: david at uilix.com (David Carmichael) Date: Tue, 17 Oct 2023 19:31:05 +0100 Subject: FlaskCon 2023 CFP Message-ID: Hello All! I'd like to inform you that FlaskCon 2023 is currently calling for proposals, and you are invited to submit. *Submission Details:* Deadline: 31st Oct Submit Your Proposal: https://flaskcon.com/ Any submissions would be greatly appreciated. Best regards, *David Carmichael* From janis_papanagnou+ng at hotmail.com Wed Oct 18 18:09:23 2023 From: janis_papanagnou+ng at hotmail.com (Janis Papanagnou) Date: Thu, 19 Oct 2023 00:09:23 +0200 Subject: Simple webserver Message-ID: I am pondering about writing a client/server software with websockets as communication protocol. The clients will run in browser as Javascript programs and the server may be in any (any sensible) programming language running standalone to be connected remotely by the browser-based JS clients. I found a Python sample[*] but I am neither familiar with Python nor with the 'simple_websocket_server' package that is used in that sample code. But the code looks so simple that I'm considering to learn and use Python for the task. The requirements I have are quite simple; I want to get the client "address"/identifier from an incoming message, store it in a list, and send responses to all active clients for which addresses have been stored. Can anyone tell me whether a simple extension of that "echo incoming message" sample[*] would be easily possible with Python and with that 'simple_websocket_server' package used? Thanks for any hints (or search keywords, or code samples)! Janis [*] https://pypi.org/project/simple-websocket-server/ From carruthm at gmail.com Wed Oct 18 18:12:38 2023 From: carruthm at gmail.com (Matthew Carruth) Date: Wed, 18 Oct 2023 15:12:38 -0700 (PDT) Subject: Any possible type alias that can also set a default value for a function arg? Message-ID: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> We have the `Optional[T]` type as a short-hand for Union[T | None] and telling us that said argument may not be present. However, I find that a majority of the time, we also want to set a default value of None on the argument so that it can be evaluated without doing a getattr() check first. iow, a lot of `foo: Optional[str] = None` in method signatures. I'd love to see a companion to the Optional type, I'll call it Default, so that it can take a default value as a second arg, with a default of that being None. For example: foo: Default[str] would be equivalent to foo: Optional[str] = None foo: Default[str, "bar"] would be equivalent to foo: Optional[str] = "bar" or something like that. Basically, any way to avoid writing `= None` over and over again. From rosuav at gmail.com Wed Oct 18 19:23:41 2023 From: rosuav at gmail.com (Chris Angelico) Date: Thu, 19 Oct 2023 10:23:41 +1100 Subject: Simple webserver In-Reply-To: References: Message-ID: On Thu, 19 Oct 2023 at 10:07, Janis Papanagnou via Python-list wrote: > > I am pondering about writing a client/server software with > websockets as communication protocol. The clients will run > in browser as Javascript programs and the server may be in > any (any sensible) programming language running standalone > to be connected remotely by the browser-based JS clients. > > I found a Python sample[*] but I am neither familiar with > Python nor with the 'simple_websocket_server' package that > is used in that sample code. But the code looks so simple > that I'm considering to learn and use Python for the task. > > The requirements I have are quite simple; I want to get the > client "address"/identifier from an incoming message, store > it in a list, and send responses to all active clients for > which addresses have been stored. > > Can anyone tell me whether a simple extension of that "echo > incoming message" sample[*] would be easily possible with > Python and with that 'simple_websocket_server' package used? > > Thanks for any hints (or search keywords, or code samples)! Oooh you've touched on one of my favourite topics. I *love* networking and communication, and websockets are one of my well-used technologies. Let's do this!! I've never used the "simple_websocket_server" you mentioned, but I've used this one in a few projects: https://pypi.org/project/websockets/ Be aware that it is designed with asyncio in mind, so if you prefer different concurrency models, you may need to look elsewhere. But I've had good success with this one. Broadly speaking, your ideas are great. Any programming language CAN be used for the server (and I've used several, not just Python). My personal preference is to build a protocol on top of websockets, for example: * All messages are "text", and are JSON-encoded * All messages represent objects (in Python, dictionaries) with a "cmd" attribute * The first message sent by the client has cmd "init" and specifies a "type" and "group". * The server tracks all connected clients by their groups, and can broadcast messages to everyone in a group. Here's one example, actually one of my brother's projects but I contributed to the websocket aspects: https://github.com/stephenangelico/BioBox/blob/master/browser.py And here's one that doesn't actually use Python, but uses all the same ideas; this is the JS end: https://github.com/Rosuav/StilleBot/blob/master/httpstatic/ws_sync.js (It has quite a bit more sophistication than you'll need to get started with, but shows how the protocol can expand as needed.) So! Tying this back in with your goals: > The requirements I have are quite simple; I want to get the > client "address"/identifier from an incoming message, store > it in a list, and send responses to all active clients for > which addresses have been stored. Sounds to me like the best way would be for the socket group to be the identifier of the client. You could augment the "init" message to include some sort of authentication, or alternatively, rely on other forms of authentication; a websocket established to the same origin as the page itself can take advantage of regular browser credentials. Once that's established, you can have a message from one client result in the server sending out that message to all clients for the recipient's address. The reason I'm talking about "groups" here instead of simply having one client per address is that it scales well to one person having multiple tabs open, or having the app on their phone as well as their computer, or anything like that. Messages will arrive on all of them. Hope that's enough to get you started! I'd be delighted to help further if you run into difficulties. ChrisA From rosuav at gmail.com Wed Oct 18 19:30:30 2023 From: rosuav at gmail.com (Chris Angelico) Date: Thu, 19 Oct 2023 10:30:30 +1100 Subject: Any possible type alias that can also set a default value for a function arg? In-Reply-To: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> References: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> Message-ID: On Thu, 19 Oct 2023 at 10:11, Matthew Carruth via Python-list wrote: > > We have the `Optional[T]` type as a short-hand for Union[T | None] and telling us that said argument may not be present. > > However, I find that a majority of the time, we also want to set a default value of None on the argument so that it can be evaluated without doing a getattr() check first. > > iow, a lot of `foo: Optional[str] = None` in method signatures. > > I'd love to see a companion to the Optional type, I'll call it Default, so that it can take a default value as a second arg, with a default of that being None. > > For example: > > foo: Default[str] would be equivalent to foo: Optional[str] = None > foo: Default[str, "bar"] would be equivalent to foo: Optional[str] = "bar" > > or something like that. Basically, any way to avoid writing `= None` over and over again. Fundamentally no, at least not without some shenanigans. Type hints do not affect the regular running of the code, so they can't add defaults. You could do it the other way around and have the default imply that it is optional, and I believe that used to be the way that MyPy calculated things, but it was ultimately rejected. (I may have the details wrong on that though, don't quote me.) Ahh, but shenanigans? What kind of shenanigans is that? Glad you asked! So, uhh, you could decorate a function and mess with its defaults. >>> from typing import Optional >>> def spam(n: Optional[int]): ... if n is None: print("Default spamminess") ... else: print("Spam " * n) ... >>> spam(5) Spam Spam Spam Spam Spam >>> spam(None) Default spamminess >>> spam() Traceback (most recent call last): File "", line 1, in TypeError: spam() missing 1 required positional argument: 'n' >>> spam.__defaults__ = (None,) >>> spam() Default spamminess So you could design a decorator that goes through all the arguments, finds the ones that say "Optional", and adds a default of None if one wasn't specified. Good luck with it though. First, you'll have to deal with the difficulties of aligning arguments (not insurmountable but a lot of work; don't forget that there are posonly and kwonly args to consider). Then, you'll have to deal with the much bigger difficulties of convincing people that this is a good thing. BTW, rather than a decorator, you could do this by iterating over every function in a module or class. That might work out easier. Not sure. Just be aware that, while Python provides you with all the tools necessary to shoot yourself in the foot, that isn't a guarantee that holes in feet are worthwhile. ChrisA From janis_papanagnou+ng at hotmail.com Wed Oct 18 21:04:40 2023 From: janis_papanagnou+ng at hotmail.com (Janis Papanagnou) Date: Thu, 19 Oct 2023 03:04:40 +0200 Subject: Simple webserver In-Reply-To: References: Message-ID: On 19.10.2023 01:23, Chris Angelico wrote: > [snip] > > Hope that's enough to get you started! I'd be delighted to help > further if you run into difficulties. Thanks for your quick reply, Chris! This is already great information! I'll dive into your resources soon, and I also appreciate your offer and will probably come back soon with a question... - Thanks again! Janis From Karsten.Hilbert at gmx.net Thu Oct 19 03:04:06 2023 From: Karsten.Hilbert at gmx.net (Karsten Hilbert) Date: Thu, 19 Oct 2023 09:04:06 +0200 Subject: Aw: Re: Any possible type alias that can also set a default value for a function arg? In-Reply-To: References: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> Message-ID: > > or something like that. Basically, any way to avoid writing `= None` over and over again. > > Fundamentally no, at least not without some shenanigans. Type hints do > not affect the regular running of the code, Except when they do ;-) ... depending on what counts as (valid) code ... In Python a distinction can be made between "runnable" and "valid" :-D Karsten From rosuav at gmail.com Thu Oct 19 03:12:33 2023 From: rosuav at gmail.com (Chris Angelico) Date: Thu, 19 Oct 2023 18:12:33 +1100 Subject: Any possible type alias that can also set a default value for a function arg? In-Reply-To: References: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> Message-ID: On Thu, 19 Oct 2023 at 18:04, Karsten Hilbert wrote: > > > > or something like that. Basically, any way to avoid writing `= None` over and over again. > > > > Fundamentally no, at least not without some shenanigans. Type hints do > > not affect the regular running of the code, > > Except when they do ;-) > > ... depending on what counts as (valid) code ... > > In Python a distinction can be made between "runnable" and "valid" :-D > Can you give a counter-example? I mean, yes, any code can be written that inspects the annotations at runtime and makes whatever changes it likes, but that's part of what I described as "shenanigans". ChrisA From Karsten.Hilbert at gmx.net Thu Oct 19 03:25:11 2023 From: Karsten.Hilbert at gmx.net (Karsten Hilbert) Date: Thu, 19 Oct 2023 09:25:11 +0200 Subject: Aw: Re: Re: Any possible type alias that can also set a default value for a function arg? In-Reply-To: References: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> Message-ID: > > > Fundamentally no, at least not without some shenanigans. Type hints do > > > not affect the regular running of the code, > > > > Except when they do ;-) > > > > ... depending on what counts as (valid) code ... > > > > In Python a distinction can be made between "runnable" and "valid" :-D > > > > Can you give a counter-example? As per my recent foray into abusing existence-checking for Singleton assurance along such lines as >>> try: self.initialized >>> except AttributeError: print('first instantiation'); self.initialized = True and then changing that to >>> try: self.initialized:bool Karsten From rosuav at gmail.com Thu Oct 19 04:27:20 2023 From: rosuav at gmail.com (Chris Angelico) Date: Thu, 19 Oct 2023 19:27:20 +1100 Subject: Any possible type alias that can also set a default value for a function arg? In-Reply-To: References: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> Message-ID: On Thu, 19 Oct 2023 at 18:25, Karsten Hilbert wrote: > > > > > Fundamentally no, at least not without some shenanigans. Type hints do > > > > not affect the regular running of the code, > > > > > > Except when they do ;-) > > > > > > ... depending on what counts as (valid) code ... > > > > > > In Python a distinction can be made between "runnable" and "valid" :-D > > > > > > > Can you give a counter-example? > > As per my recent foray into abusing existence-checking for Singleton assurance > along such lines as > > >>> try: self.initialized > >>> except AttributeError: print('first instantiation'); self.initialized = True > > and then changing that to > > >>> try: self.initialized:bool But that's not equivalent code. You might just as well say that the ellipsis here suddenly changes the code: self.initialized self.initialized = ... These are completely different, and they behave differently. Both are valid, but they mean different things. ChrisA From Karsten.Hilbert at gmx.net Thu Oct 19 04:34:34 2023 From: Karsten.Hilbert at gmx.net (Karsten Hilbert) Date: Thu, 19 Oct 2023 10:34:34 +0200 Subject: Aw: Re: Re: Re: Any possible type alias that can also set a default value for a function arg? In-Reply-To: References: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> Message-ID: > > As per my recent foray into abusing existence-checking for Singleton assurance > > along such lines as > > > > >>> try: self.initialized > > >>> except AttributeError: print('first instantiation'); self.initialized = True > > > > and then changing that to > > > > >>> try: self.initialized:bool > > But that's not equivalent code. I learned as much (RHS vs LHS). But it did not _intuitively_ resonate with the sentiment "type annotation does not change the running of code". Karsten From rosuav at gmail.com Thu Oct 19 05:02:08 2023 From: rosuav at gmail.com (Chris Angelico) Date: Thu, 19 Oct 2023 20:02:08 +1100 Subject: Any possible type alias that can also set a default value for a function arg? In-Reply-To: References: <241867da-1918-4396-b376-e027b55c68e7n@googlegroups.com> Message-ID: On Thu, 19 Oct 2023 at 19:34, Karsten Hilbert wrote: > > > > As per my recent foray into abusing existence-checking for Singleton assurance > > > along such lines as > > > > > > >>> try: self.initialized > > > >>> except AttributeError: print('first instantiation'); self.initialized = True > > > > > > and then changing that to > > > > > > >>> try: self.initialized:bool > > > > But that's not equivalent code. > > I learned as much (RHS vs LHS). > > But it did not _intuitively_ resonate with the sentiment > "type annotation does not change the running of code". Unfortunately, that simply means that your intuition was wrong. It doesn't change my prior statement. ChrisA From bongoferno at gmail.com Thu Oct 19 21:32:34 2023 From: bongoferno at gmail.com (Bongo Ferno) Date: Thu, 19 Oct 2023 18:32:34 -0700 (PDT) Subject: Where I do ask for a new feature In-Reply-To: References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> Message-ID: > You can actually just do that with simple assignment! > > short_view = my_object.stuff.long_stuff.sub_object > print(short_view.some_method()) but then have to delete the variable manually del short_view From avi.e.gross at gmail.com Thu Oct 19 22:26:20 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Thu, 19 Oct 2023 22:26:20 -0400 Subject: Where I do ask for a new feature In-Reply-To: References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> Message-ID: <005701da02fc$d094d580$71be8080$@gmail.com> Bongo, Variables in most programming languages either have to be removed manually or allowed to drift outside a boundary when they disappear for scoping reasons and perhaps are garbage collected at some point. There are many ways to make transient variables that disappear at some time and do we need yet another? Yes, you can create one of those ways but what is the big deal with deleting a variable when no longer used? Examples might be the "finally" clause or the "with" statement or just putting the variable in a nested scope. -----Original Message----- From: Python-list On Behalf Of Bongo Ferno via Python-list Sent: Thursday, October 19, 2023 9:33 PM To: python-list at python.org Subject: Re: Where I do ask for a new feature > You can actually just do that with simple assignment! > > short_view = my_object.stuff.long_stuff.sub_object > print(short_view.some_method()) but then have to delete the variable manually del short_view -- https://mail.python.org/mailman/listinfo/python-list From bongoferno at gmail.com Thu Oct 19 23:16:37 2023 From: bongoferno at gmail.com (Bongo Ferno) Date: Thu, 19 Oct 2023 20:16:37 -0700 (PDT) Subject: Where I do ask for a new feature In-Reply-To: References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> <005701da02fc$d094d580$71be8080$@gmail.com> Message-ID: On Thursday, October 19, 2023 at 11:26:52?PM UTC-3, avi.e... at gmail.com wrote: > There are many ways to make transient variables that disappear at some time > and do we need yet another? Yes, you can create one of those ways but what > is the big deal with deleting a variable when no longer used? Assigning a variable to something can be anything else than a temporal alias. A with statement makes clear that the alias is an alias and is local, and it automatically clears the variable after the block code is used. Python clutters the variable space with vars that are needed only on certain places, and an alias doesn't has a scope. Convenient alias are short names, and short names are limited in quantity. If the space is cluttered with short alias, it opens risks for wrong utilization. Its like writing a "for i" in a list comprehension and having to worry if "i" was already used in another place.. From cs at cskk.id.au Fri Oct 20 02:41:32 2023 From: cs at cskk.id.au (Cameron Simpson) Date: Fri, 20 Oct 2023 17:41:32 +1100 Subject: Where I do ask for a new feature In-Reply-To: References: Message-ID: On 19Oct2023 20:16, Bongo Ferno wrote: >A with statement makes clear that the alias is an alias and is local, >and it automatically clears the variable after the block code is used. No it doesn't: >>> with open('/dev/null') as f: ... print(f) ... <_io.TextIOWrapper name='/dev/null' mode='r' encoding='UTF-8'> >>> print(f) <_io.TextIOWrapper name='/dev/null' mode='r' encoding='UTF-8'> From roel at roelschroeven.net Fri Oct 20 03:55:12 2023 From: roel at roelschroeven.net (Roel Schroeven) Date: Fri, 20 Oct 2023 09:55:12 +0200 Subject: Where I do ask for a new feature In-Reply-To: References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> <005701da02fc$d094d580$71be8080$@gmail.com> Message-ID: <65ec9f76-be1a-4a0c-be74-9c7f4839679f@roelschroeven.net> Op 20/10/2023 om 5:16 schreef Bongo Ferno via Python-list: > On Thursday, October 19, 2023 at 11:26:52?PM UTC-3, avi.e... at gmail.com wrote: > > > There are many ways to make transient variables that disappear at some time > > and do we need yet another? Yes, you can create one of those ways but what > > is the big deal with deleting a variable when no longer used? > > Assigning a variable to something can be anything else than a temporal alias. > A with statement makes clear that the alias is an alias and is local, and it automatically clears the variable after the block code is used. > > Python clutters the variable space with vars that are needed only on certain places, and an alias doesn't has a scope. > Convenient alias are short names, and short names are limited in quantity. If the space is cluttered with short alias, it opens risks for wrong utilization. > > Its like writing a "for i" in a list comprehension and having to worry if "i" was already used in another place.. As long as functions are kept reasonably short, which is a good idea anyway, I don't really see any of that as a problem. -- "Experience is that marvelous thing that enables you to recognize a mistake when you make it again." -- Franklin P. Jones From janis_papanagnou+ng at hotmail.com Fri Oct 20 06:13:02 2023 From: janis_papanagnou+ng at hotmail.com (Janis Papanagnou) Date: Fri, 20 Oct 2023 12:13:02 +0200 Subject: Simple webserver In-Reply-To: References: Message-ID: On 19.10.2023 01:23, Chris Angelico wrote: > > Broadly speaking, your ideas are great. Any programming language CAN > be used for the server (and I've used several, not just Python). Out of curiosity; what where these languages? - If there's one I already know I might save some time implementing the server. :-) Janis From rosuav at gmail.com Fri Oct 20 07:34:32 2023 From: rosuav at gmail.com (Chris Angelico) Date: Fri, 20 Oct 2023 22:34:32 +1100 Subject: Simple webserver In-Reply-To: References: Message-ID: On Fri, 20 Oct 2023 at 22:31, Janis Papanagnou via Python-list wrote: > > On 19.10.2023 01:23, Chris Angelico wrote: > > > > Broadly speaking, your ideas are great. Any programming language CAN > > be used for the server (and I've used several, not just Python). > > Out of curiosity; what where these languages? - If there's one I > already know I might save some time implementing the server. :-) > I've done websocket servers in Python, Node.js, and Pike, and possibly others but I can't recall at the moment. Might have done one in Ruby, but that would have just been part of playing around and comparing features ("how easy is it to do in Ruby"). ChrisA From list1 at tompassin.net Fri Oct 20 08:32:02 2023 From: list1 at tompassin.net (Thomas Passin) Date: Fri, 20 Oct 2023 08:32:02 -0400 Subject: Where I do ask for a new feature In-Reply-To: References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> <005701da02fc$d094d580$71be8080$@gmail.com> Message-ID: <8d7c8ce0-9ff8-414c-aef3-f640cff73525@tompassin.net> On 10/19/2023 11:16 PM, Bongo Ferno via Python-list wrote: > On Thursday, October 19, 2023 at 11:26:52?PM UTC-3, avi.e... at gmail.com wrote: > >> There are many ways to make transient variables that disappear at some time >> and do we need yet another? Yes, you can create one of those ways but what >> is the big deal with deleting a variable when no longer used? > > Assigning a variable to something can be anything else than a temporal alias. > A with statement makes clear that the alias is an alias and is local, and it automatically clears the variable after the block code is used. > > Python clutters the variable space with vars that are needed only on certain places, and an alias doesn't has a scope. > Convenient alias are short names, and short names are limited in quantity. If the space is cluttered with short alias, it opens risks for wrong utilization. > > Its like writing a "for i" in a list comprehension and having to worry if "i" was already used in another place.. If a name is temporarily needed in a certain place and in a certain scope then reusing the name shouldn't be a problem. From verstotene at news.eternal-september.org Fri Oct 20 07:40:24 2023 From: verstotene at news.eternal-september.org (De ongekruisigde) Date: Fri, 20 Oct 2023 11:40:24 -0000 (UTC) Subject: Simple webserver References: Message-ID: On 2023-10-20, Chris Angelico wrote: > On Fri, 20 Oct 2023 at 22:31, Janis Papanagnou via Python-list > wrote: >> >> On 19.10.2023 01:23, Chris Angelico wrote: >> > >> > Broadly speaking, your ideas are great. Any programming language CAN >> > be used for the server (and I've used several, not just Python). >> >> Out of curiosity; what where these languages? - If there's one I >> already know I might save some time implementing the server. :-) >> > > I've done websocket servers in Python, Node.js, and Pike, and possibly > others but I can't recall at the moment. Might have done one in Ruby, > but that would have just been part of playing around and comparing > features ("how easy is it to do in Ruby"). > > ChrisA *Big list of http static server one-liners* Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely. From avi.e.gross at gmail.com Fri Oct 20 13:48:41 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Fri, 20 Oct 2023 13:48:41 -0400 Subject: Where I do ask for a new feature In-Reply-To: <65ec9f76-be1a-4a0c-be74-9c7f4839679f@roelschroeven.net> References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> <005701da02fc$d094d580$71be8080$@gmail.com> <65ec9f76-be1a-4a0c-be74-9c7f4839679f@roelschroeven.net> Message-ID: <005201da037d$aa5196c0$fef4c440$@gmail.com> I still see no great reason for a new feature here and the namespace issue has often been discussed. You can always opt to create your own namespace of some sort and make many of your variables within it and always refer to the variables explicitly so the only collisions that can happen are your own carelessness. I do note that reusing a variable like "i" is not uncommon and especially when it is merely used as a looping variable. Generally anything else using the same variable does not need to refer to the other use and is in another scope. May I politely ask if you can point to other languages that have the feature you want and what it looks like. How does it know when the variable can safely go away? Does it allow you to create your alias in something like a loop and re-assign it or is it more like a constant once set and so on? If you have a good use case with no other easy way to provide it, you still need to show it is more important than oodles of other feature requests before anyone would consider seriously doing it in some future release. I am wondering if your concept of an alias is more typographical than actual. I mean in languages like C, there was often a preprocessor that went through your code and made changes like: #DEFINE filename "/usr/me/dir/subdir/file.c" This could allow some shorter typing but would not have anything in the namespace on the compiler level which would just see the longer substitutions. Could Python include something like this by keeping a table of symbols and replacements or running a pre-processor first? Maybe. But as stated, it does not seem to be a NEED that some feel is important. Assigning a variable to hold a pointer of sorts does indeed add to the namespace but the resource involved is not a big deal. Python is an interpreted language that makes one pass but there are languages that make multiple passes through the code and allow things like defining a function after it has been called. That is not pythonic. -----Original Message----- From: Python-list On Behalf Of Roel Schroeven via Python-list Sent: Friday, October 20, 2023 3:55 AM To: python-list at python.org Subject: Re: Where I do ask for a new feature Op 20/10/2023 om 5:16 schreef Bongo Ferno via Python-list: > On Thursday, October 19, 2023 at 11:26:52?PM UTC-3, avi.e... at gmail.com wrote: > > > There are many ways to make transient variables that disappear at some time > > and do we need yet another? Yes, you can create one of those ways but what > > is the big deal with deleting a variable when no longer used? > > Assigning a variable to something can be anything else than a temporal alias. > A with statement makes clear that the alias is an alias and is local, and it automatically clears the variable after the block code is used. > > Python clutters the variable space with vars that are needed only on certain places, and an alias doesn't has a scope. > Convenient alias are short names, and short names are limited in quantity. If the space is cluttered with short alias, it opens risks for wrong utilization. > > Its like writing a "for i" in a list comprehension and having to worry if "i" was already used in another place.. As long as functions are kept reasonably short, which is a good idea anyway, I don't really see any of that as a problem. -- "Experience is that marvelous thing that enables you to recognize a mistake when you make it again." -- Franklin P. Jones -- https://mail.python.org/mailman/listinfo/python-list From torriem at gmail.com Fri Oct 20 14:48:30 2023 From: torriem at gmail.com (Michael Torrie) Date: Fri, 20 Oct 2023 12:48:30 -0600 Subject: Where I do ask for a new feature In-Reply-To: References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> Message-ID: On 10/19/23 19:32, Bongo Ferno via Python-list wrote: > >> You can actually just do that with simple assignment! >> >> short_view = my_object.stuff.long_stuff.sub_object >> print(short_view.some_method()) > > but then have to delete the variable manually > > del short_view Why? It's just a name in the namespace that you can bind to a function object. You can ignore it or rebind it later to something else. There's no need to del it, although you can. I'm not sure why you want to del it. It's not like a memory leak or something like that. I suspect we might also have a misunderstanding of what python variables are and how they work, which is why I did not use the word, "reassign" but rather "bind" or "rebind." From PythonList at DancesWithMice.info Fri Oct 20 16:44:23 2023 From: PythonList at DancesWithMice.info (dn) Date: Sat, 21 Oct 2023 09:44:23 +1300 Subject: Where I do ask for a new feature In-Reply-To: <8d7c8ce0-9ff8-414c-aef3-f640cff73525@tompassin.net> References: <708b6c8e-2196-4253-b508-283b4fb58c86n@googlegroups.com> <005701da02fc$d094d580$71be8080$@gmail.com> <8d7c8ce0-9ff8-414c-aef3-f640cff73525@tompassin.net> Message-ID: <08af746a-23ae-4ab1-8f10-42b4614704ac@DancesWithMice.info> On 21/10/2023 01.32, Thomas Passin via Python-list wrote: > On 10/19/2023 11:16 PM, Bongo Ferno via Python-list wrote: >> On Thursday, October 19, 2023 at 11:26:52?PM UTC-3, avi.e... at gmail.com >> wrote: >> >>> There are many ways to make transient variables that disappear at >>> some time >>> and do we need yet another? Yes, you can create one of those ways but >>> what >>> is the big deal with deleting a variable when no longer used? >> >> Assigning a variable to something can be anything else than a temporal >> alias. >> A with statement makes clear that the alias is an alias and is local, >> and it automatically clears the variable after the block code is used. >> >> Python clutters the variable space with vars that are needed only on >> certain places, and an alias doesn't has a scope. >> Convenient alias are short names, and short names are limited in >> quantity. If the space is cluttered with short alias, it opens risks >> for wrong utilization. >> >> Its like writing a "for i" in a list comprehension and having to worry >> if "i" was already used in another place.. > > If a name is temporarily needed in a certain place and in a certain > scope then reusing the name shouldn't be a problem. Agree. Surely, the only time we use a name like "i" is in a throw-away context? Under many circumstances Python will let us use "_" in place of a named-identifier - which enables both us and Python to remember its short-lived value/local-only use. Using an alias MERELY for the convenience of a shorter-name suggests two things: 1 lack of a competent editor/IDE, 2 lack of imagination in choosing names (perhaps one of THE skills of programming!) Yes, there are other languages which enforce a limited-scope on data-items created within or as part of a code-structure - and it IS a handy feature! On the other hand, Python's apposite stance can be useful too, eg trivial toy-example: # list_of_stuff = ... for n, element in list_of_stuff: if element == target: break # now element == target, so "element" is probably not that useful # but "n" is the index of the target-element, which may be # (there are other ways to accomplish same) Please take a look at the ideas behind "Modular Programming". This encourages the breaking-up of monolithic code and its "cluttered" global namespace, into potentially-independent code-units. The outlined-problem is solved by the independent scope of those code-units (in Python: modules, classes, functions, and "if __name__ == "__main__":". (to say nothing of the coder's virtues of "re-use", the "Single Responsibility Principle", "do one thing, and do it well", Law of Demeter, ...) Personal comment: my habit is to break specs into many classes and functions - sometimes more-so than others might prefer. Cannot recall when last had that hard-to-locate bug of unwittingly re-using a name/alias. (apologies: not a boast - a recommendation for going modular) -- Regards, =dn From larry.martell at gmail.com Sat Oct 21 09:01:18 2023 From: larry.martell at gmail.com (Larry Martell) Date: Sat, 21 Oct 2023 09:01:18 -0400 Subject: Running a subprocess in a venv Message-ID: I have a python script, and from that I want to run another script in a subprocess in a venv. What is the best way to do that? I could write a file that activates the venv then runs the script, then run that file, but that seems messy. Is there a better way? From mailman at hanez.org Sat Oct 21 09:49:38 2023 From: mailman at hanez.org (Johannes Findeisen) Date: Sat, 21 Oct 2023 15:49:38 +0200 Subject: Running a subprocess in a venv In-Reply-To: References: Message-ID: <20231021154938.752713ae@jupiter> On Sat, 21 Oct 2023 09:01:18 -0400 Larry Martell via Python-list wrote: > I have a python script, and from that I want to run another script in > a subprocess in a venv. What is the best way to do that? I could write > a file that activates the venv then runs the script, then run that > file, but that seems messy. Is there a better way? How do you do that? It sounds messy but not wrong... I would activate the venv and then run my Python script. In the Python script you can call another python script in a subprocess like this: import sys import subprocess # https://docs.python.org/3/library/subprocess.html#popen-constructor proc = subprocess.Popen([sys.executable, "/path/to/an/otherscript.py"]) # https://docs.python.org/3/library/subprocess.html#popen-objects # Do your process communication/handling... proc.communicate(), # proc.wait(), proc.terminate(), proc.kill() etc. Is this the answer you are looking for? Detailed docs: https://docs.python.org/3/library/subprocess.html Regards, Johannes From roel at roelschroeven.net Sat Oct 21 10:40:43 2023 From: roel at roelschroeven.net (Roel Schroeven) Date: Sat, 21 Oct 2023 16:40:43 +0200 Subject: Running a subprocess in a venv In-Reply-To: References: Message-ID: Larry Martell via Python-list schreef op 21/10/2023 om 15:01: > I have a python script, and from that I want to run another script in > a subprocess in a venv. What is the best way to do that? I could write > a file that activates the venv then runs the script, then run that > file, but that seems messy. Is there a better way? Activating a venv it is practical when you're working in a shell, but not actually needed. You can execute the python in the venv with the script as parameter. Have a look in the venv directory: there will be a Script subdirectory (on Windows) or bin subdirectory (on Unix-like systems). Within that directory are several executables, one of which will be python or python3. That's the one you need. So use something like ??? subprocess.run(['/path/to/venv/bin/python3', 'yourscript.py', possible other arguments]) -- "Binnen een begrensde ruimte ligt een kritiek punt, waar voorbij de vrijheid afneemt naarmate het aantal individuen stijgt. Dit gaat evenzeer op voor mensen in de begrensde ruimte van een planetair ecosysteem, als voor de gasmoleculen in een hermetisch gesloten vat. Bij mensen is het niet de vraag hoeveel er maximaal in leven kunnen blijven in het systeem, maar wat voor soort bestaan mogelijk is voor diegenen die in leven blijven. -- Pardot Kynes, eerste planetoloog van Arrakis" -- Frank Herbert, Duin From larry.martell at gmail.com Sat Oct 21 11:32:03 2023 From: larry.martell at gmail.com (Larry Martell) Date: Sat, 21 Oct 2023 11:32:03 -0400 Subject: Running a subprocess in a venv In-Reply-To: <20231021154938.752713ae@jupiter> References: <20231021154938.752713ae@jupiter> Message-ID: On Sat, Oct 21, 2023 at 9:49?AM Johannes Findeisen wrote: > > On Sat, 21 Oct 2023 09:01:18 -0400 > Larry Martell via Python-list wrote: > > > I have a python script, and from that I want to run another script in > > a subprocess in a venv. What is the best way to do that? I could write > > a file that activates the venv then runs the script, then run that > > file, but that seems messy. Is there a better way? > > How do you do that? How? Open a file and write the commands I need then invoke that. > It sounds messy but not wrong... > > I would activate the venv and then run my Python script. In the Python > script you can call another python script in a subprocess like this: > > import sys > import subprocess > > # https://docs.python.org/3/library/subprocess.html#popen-constructor > proc = subprocess.Popen([sys.executable, "/path/to/an/otherscript.py"]) > > # https://docs.python.org/3/library/subprocess.html#popen-objects > # Do your process communication/handling... proc.communicate(), > # proc.wait(), proc.terminate(), proc.kill() etc. > > Is this the answer you are looking for? > > Detailed docs: https://docs.python.org/3/library/subprocess.html I know how to use Popen. What I was missing was running the script using sys.executable. Thanks. From mailman at hanez.org Sat Oct 21 12:10:19 2023 From: mailman at hanez.org (Johannes Findeisen) Date: Sat, 21 Oct 2023 18:10:19 +0200 Subject: Running a subprocess in a venv In-Reply-To: References: <20231021154938.752713ae@jupiter> Message-ID: <20231021181019.61d1b3e0@jupiter> On Sat, 21 Oct 2023 11:32:03 -0400 Larry Martell wrote: > On Sat, Oct 21, 2023 at 9:49?AM Johannes Findeisen > wrote: > > > > On Sat, 21 Oct 2023 09:01:18 -0400 > > Larry Martell via Python-list wrote: > > > > > I have a python script, and from that I want to run another > > > script in a subprocess in a venv. What is the best way to do > > > that? I could write a file that activates the venv then runs the > > > script, then run that file, but that seems messy. Is there a > > > better way? > > > > How do you do that? > > How? Open a file and write the commands I need then invoke that. > > > It sounds messy but not wrong... > > > > I would activate the venv and then run my Python script. In the > > Python script you can call another python script in a subprocess > > like this: > > > > import sys > > import subprocess > > > > # > > https://docs.python.org/3/library/subprocess.html#popen-constructor > > proc = subprocess.Popen([sys.executable, > > "/path/to/an/otherscript.py"]) > > > > # https://docs.python.org/3/library/subprocess.html#popen-objects > > # Do your process communication/handling... proc.communicate(), > > # proc.wait(), proc.terminate(), proc.kill() etc. > > > > Is this the answer you are looking for? > > > > Detailed docs: https://docs.python.org/3/library/subprocess.html > > I know how to use Popen. What I was missing was running the script > using sys.executable. Thanks. sys.executable is the path to the actual Python binary, e.g. "/usr/bin/python". You could add "/usr/bin/python" there manually but this is not portable to Windows for example. When you add a shebang line to your other script and the file is executable, you may not need to add sys.executable as first argument to Popen but using sys.executable is the most reliable way to do this... ;) Regards, Johannes From larry.martell at gmail.com Sat Oct 21 12:19:55 2023 From: larry.martell at gmail.com (Larry Martell) Date: Sat, 21 Oct 2023 12:19:55 -0400 Subject: Running a subprocess in a venv In-Reply-To: <20231021181019.61d1b3e0@jupiter> References: <20231021154938.752713ae@jupiter> <20231021181019.61d1b3e0@jupiter> Message-ID: On Sat, Oct 21, 2023 at 12:10?PM Johannes Findeisen wrote: > > On Sat, 21 Oct 2023 11:32:03 -0400 > Larry Martell wrote: > > > On Sat, Oct 21, 2023 at 9:49?AM Johannes Findeisen > > wrote: > > > > > > On Sat, 21 Oct 2023 09:01:18 -0400 > > > Larry Martell via Python-list wrote: > > > > > > > I have a python script, and from that I want to run another > > > > script in a subprocess in a venv. What is the best way to do > > > > that? I could write a file that activates the venv then runs the > > > > script, then run that file, but that seems messy. Is there a > > > > better way? > > > > > > How do you do that? > > > > How? Open a file and write the commands I need then invoke that. > > > > > It sounds messy but not wrong... > > > > > > I would activate the venv and then run my Python script. In the > > > Python script you can call another python script in a subprocess > > > like this: > > > > > > import sys > > > import subprocess > > > > > > # > > > https://docs.python.org/3/library/subprocess.html#popen-constructor > > > proc = subprocess.Popen([sys.executable, > > > "/path/to/an/otherscript.py"]) > > > > > > # https://docs.python.org/3/library/subprocess.html#popen-objects > > > # Do your process communication/handling... proc.communicate(), > > > # proc.wait(), proc.terminate(), proc.kill() etc. > > > > > > Is this the answer you are looking for? > > > > > > Detailed docs: https://docs.python.org/3/library/subprocess.html > > > > I know how to use Popen. What I was missing was running the script > > using sys.executable. Thanks. > > sys.executable is the path to the actual Python binary, e.g. > "/usr/bin/python". You could add "/usr/bin/python" there manually but > this is not portable to Windows for example. > > When you add a shebang line to your other script and the file is > executable, you may not need to add sys.executable as first argument to > Popen but using sys.executable is the most reliable way to do this... ;) I need the path to whichever venv is being used so sys.executable works for me. From list1 at tompassin.net Sat Oct 21 12:25:51 2023 From: list1 at tompassin.net (Thomas Passin) Date: Sat, 21 Oct 2023 12:25:51 -0400 Subject: Running a subprocess in a venv In-Reply-To: References: <20231021154938.752713ae@jupiter> Message-ID: On 10/21/2023 11:32 AM, Larry Martell via Python-list wrote: > On Sat, Oct 21, 2023 at 9:49?AM Johannes Findeisen wrote: >> >> On Sat, 21 Oct 2023 09:01:18 -0400 >> Larry Martell via Python-list wrote: >> >>> I have a python script, and from that I want to run another script in >>> a subprocess in a venv. What is the best way to do that? I could write >>> a file that activates the venv then runs the script, then run that >>> file, but that seems messy. Is there a better way? >> >> How do you do that? > > How? Open a file and write the commands I need then invoke that. > >> It sounds messy but not wrong... >> >> I would activate the venv and then run my Python script. In the Python >> script you can call another python script in a subprocess like this: >> >> import sys >> import subprocess >> >> # https://docs.python.org/3/library/subprocess.html#popen-constructor >> proc = subprocess.Popen([sys.executable, "/path/to/an/otherscript.py"]) >> >> # https://docs.python.org/3/library/subprocess.html#popen-objects >> # Do your process communication/handling... proc.communicate(), >> # proc.wait(), proc.terminate(), proc.kill() etc. >> >> Is this the answer you are looking for? >> >> Detailed docs: https://docs.python.org/3/library/subprocess.html > > I know how to use Popen. What I was missing was running the script > using sys.executable. Thanks. A nice feature of using sys.executable is that you automatically use the same Python installation as your invoking program is running with. On a system that has several different Python installations, that's a very good thing. From janis_papanagnou+ng at hotmail.com Fri Oct 20 22:03:32 2023 From: janis_papanagnou+ng at hotmail.com (Janis Papanagnou) Date: Sat, 21 Oct 2023 04:03:32 +0200 Subject: Simple webserver In-Reply-To: <874jilypgs.fsf@nightsong.com> References: <874jilypgs.fsf@nightsong.com> Message-ID: On 20.10.2023 23:05, Paul Rubin wrote: > Janis Papanagnou writes: >> I found a Python sample[*] but I am neither familiar with >> Python nor with the 'simple_websocket_server' package that >> is used in that sample code. But the code looks so simple >> that I'm considering to learn and use Python for the task. > > I've generally used ThreadingServer(SocketServer) for this purpose > and I think threads are less confusing than async, and performance is > fine if the concurrency level is not too high. But, trying to write a > web server in Python if you don't know Python doesn't seem like a great > idea, except as a learning project. I have a couple decades experience with about a dozen programming languages (not counting assemblers). Asynchronous processing, IPC, multi-processing, client/server architectures, multi-threading, semaphores, etc. etc. are concepts that are not new to me. I'm not, literally, intending to write a web-server. It's a JS application that is running in (browser based) clients, and the server is just centrally coordinating the client applications. My expectation would be that any sophistically designed socket/ web-socket library would not impose any risk. And the intended server by itself has only very limited requirements; listening to incoming request, storing some client information, broadcasting to the attached clients. Basically just (informally written): init server forever: wait for request(s) -> queue handle requests from queue (sequentially): store specific information from new registered clients broadcast some information to all registered clients It seems to me that multi-threading or async I/O aren't necessary. I'd like to ask; where do you see the specific risks with Python (as language per se) and it's (web-socket-)libraries here? If the web-socket IPC is well supported the algorithmic parts in Python seem trivial to learn and implement. - Or am I missing something? (A brief search gave me the impression that for JS communication web-sockets would be the method to use. Otherwise I'd just use basic Unix domain sockets for the purpose and write it, say, in C or C++ that I already know. But I don't know whether (or how) plain sockets are used from JS running in a browser. Here I'm lacking experience. And that lead me to have a look at Python, since the web-sockets/server examples that I found looked simple.) Janis From rosuav at gmail.com Sat Oct 21 14:58:17 2023 From: rosuav at gmail.com (Chris Angelico) Date: Sun, 22 Oct 2023 05:58:17 +1100 Subject: Simple webserver In-Reply-To: References: <874jilypgs.fsf@nightsong.com> Message-ID: On Sun, 22 Oct 2023 at 04:13, Janis Papanagnou via Python-list wrote: > I have a couple decades experience with about a dozen programming > languages (not counting assemblers). Asynchronous processing, IPC, > multi-processing, client/server architectures, multi-threading, > semaphores, etc. etc. are concepts that are not new to me. Oh, sweet, sweet, then you should be fine with the library I suggested. It's certainly served me well (and I have similar experience, having learned networking mainly on OS/2 in the 1990s). > My expectation would be that any sophistically designed socket/ > web-socket library would not impose any risk. And the intended > server by itself has only very limited requirements; listening to > incoming request, storing some client information, broadcasting > to the attached clients. Basically just (informally written): > > init server > forever: > wait for request(s) -> queue > handle requests from queue (sequentially): > store specific information from new registered clients > broadcast some information to all registered clients > > It seems to me that multi-threading or async I/O aren't necessary. Technically that's true, but "wait for request(s)" has to handle (a) new incoming sockets, (b) messages from currently-connected sockets, and possibly (c) sockets now being writable when previously they blocked. So you have most of the work of async I/O. Since the library's been built specifically for asyncio, that's the easiest. > I'd like to ask; where do you see the specific risks with Python > (as language per se) and it's (web-socket-)libraries here? > > If the web-socket IPC is well supported the algorithmic parts in > Python seem trivial to learn and implement. - Or am I missing > something? Pretty trivial, yeah. You shouldn't have too much trouble here I expect. > (A brief search gave me the impression that for JS communication > web-sockets would be the method to use. Otherwise I'd just use > basic Unix domain sockets for the purpose and write it, say, in > C or C++ that I already know. But I don't know whether (or how) > plain sockets are used from JS running in a browser. Here I'm > lacking experience. And that lead me to have a look at Python, > since the web-sockets/server examples that I found looked simple.) Yes, that's correct. You can't use plain sockets from inside a web browser, mainly because they offer way way too much flexibility (JS code is untrusted and is now running on your computer, do you really want that to be able to telnet to anything on your LAN?). So websockets are the way to go. There are other similar technologies, but for this sort of "broadcast to connected clients" messaging system, websockets rule. ChrisA From mats at wichmann.us Sat Oct 21 15:08:03 2023 From: mats at wichmann.us (Mats Wichmann) Date: Sat, 21 Oct 2023 13:08:03 -0600 Subject: Running a subprocess in a venv In-Reply-To: References: Message-ID: <41383972-db38-4f2d-87aa-875b315a6681@wichmann.us> On 10/21/23 07:01, Larry Martell via Python-list wrote: > I have a python script, and from that I want to run another script in > a subprocess in a venv. What is the best way to do that? I could write > a file that activates the venv then runs the script, then run that > file, but that seems messy. Is there a better way? You don't need to "activate" a virtualenv. The activation script does some helpful things along the way (setup and cleanup) but none of them are required. The most important thing it does is basically: VIRTUAL_ENV='path-where-you-put-the-virtualenv' export VIRTUAL_ENV _OLD_VIRTUAL_PATH="$PATH" PATH="$VIRTUAL_ENV/bin:$PATH" export PATH and that's really only so that commands that belong to that virtualenv (python, pip, and things where you installed a package in the venv wich creates an "executable" in bin/) are in a directory first in your search path. As long as you deal with necessary paths yourself, you're fine without activating. So as mentioned elsewhere, just use the path to the virtualenv's Python and you're good to go. From phd at phdru.name Sun Oct 22 06:18:05 2023 From: phd at phdru.name (Oleg Broytman) Date: Sun, 22 Oct 2023 13:18:05 +0300 Subject: Cheetah 3.3.3 Message-ID: Hello! I'm pleased to announce version 3.3.3, the fourth release of branch 3.3 of CheetahTemplate3. What's new in CheetahTemplate3 ============================== Minor features: - Protect ``import cgi`` in preparation to Python 3.13. Tests: - Run tests with Python 3.12. CI: - GHActions: Ensure ``pip`` only if needed This is to work around a problem in conda with Python 3.7 - it brings in wrong version of ``setuptools`` incompatible with Python 3.7. What is CheetahTemplate3 ======================== Cheetah3 is a free and open source (MIT) Python template engine. It's a fork of the original CheetahTemplate library. Python 2.7 or 3.4+ is required. Where is CheetahTemplate3 ========================= Site: https://cheetahtemplate.org/ Download: https://pypi.org/project/CT3/3.3.3 News and changes: https://cheetahtemplate.org/news.html StackOverflow: https://stackoverflow.com/questions/tagged/cheetah Mailing lists: https://sourceforge.net/p/cheetahtemplate/mailman/ Development: https://github.com/CheetahTemplate3 Developer Guide: https://cheetahtemplate.org/dev_guide/ Example ======= Install:: $ pip install CT3 # (or even "ct3") Below is a simple example of some Cheetah code, as you can see it's practically Python. You can import, inherit and define methods just like in a regular Python module, since that's what your Cheetah templates are compiled to :) :: #from Cheetah.Template import Template #extends Template #set $people = [{'name' : 'Tom', 'mood' : 'Happy'}, {'name' : 'Dick', 'mood' : 'Sad'}, {'name' : 'Harry', 'mood' : 'Hairy'}] How are you feeling?
    #for $person in $people
  • $person['name'] is $person['mood']
    • #end for
Oleg. -- Oleg Broytman https://phdru.name/ phd at phdru.name Programmers don't die, they just GOSUB without RETURN. From antoon.pardon at vub.be Sun Oct 22 11:50:34 2023 From: antoon.pardon at vub.be (Antoon Pardon) Date: Sun, 22 Oct 2023 17:50:34 +0200 Subject: return type same as class gives NameError. Message-ID: I have the following small module: =-=-=-=-=-=-=-=-=-=-=-= 8< =-=-=-=-=-=-=-=-=-=-=-=-= from typing import NamedTuple, TypeAlias, Union from collections.abc import Sequence PNT: TypeAlias = tuple[float, float] class Pnt (NamedTuple): x: float y: float def __add__(self, other: PNT) -> Pnt: return Pnt(self[0] + other[0], self[1] + other[1]) =-=-=-=-=-=-=-=-=-=-=-= >8 =-=-=-=-=-=-=-=-=-=-=-=-= But when I import this, I get the following diagnostic: Traceback (most recent call last): File "", line 1, in File "/home/sisc/projecten/iudex/problem.py", line 10, in class Pnt (NamedTuple): File "/home/sisc/projecten/iudex/problem.py", line 14, in Pnt def __add__(self, other: PNT) -> Pnt: ^^^ NameError: name 'Pnt' is not defined. Did you mean: 'PNT'? Can someone explain what I am doing wrong? From PythonList at DancesWithMice.info Sun Oct 22 12:54:50 2023 From: PythonList at DancesWithMice.info (dn) Date: Mon, 23 Oct 2023 05:54:50 +1300 Subject: return type same as class gives NameError. In-Reply-To: References: Message-ID: On 23/10/2023 04.50, Antoon Pardon via Python-list wrote: > I have the following small module: > > =-=-=-=-=-=-=-=-=-=-=-= 8< =-=-=-=-=-=-=-=-=-=-=-=-= > > from typing import NamedTuple, TypeAlias, Union > from collections.abc import Sequence > > PNT: TypeAlias = tuple[float, float] > > class Pnt (NamedTuple): > ??? x: float > ??? y: float > > ??? def __add__(self, other: PNT) -> Pnt: > ??????? return Pnt(self[0] + other[0], self[1] + other[1]) > > =-=-=-=-=-=-=-=-=-=-=-= >8 =-=-=-=-=-=-=-=-=-=-=-=-= > > But when I import this, I get the following diagnostic: > > Traceback (most recent call last): > ? File "", line 1, in > ? File "/home/sisc/projecten/iudex/problem.py", line 10, in > ??? class Pnt (NamedTuple): > ? File "/home/sisc/projecten/iudex/problem.py", line 14, in Pnt > ??? def __add__(self, other: PNT) -> Pnt: > ???????????????????????????????????? ^^^ > NameError: name 'Pnt' is not defined. Did you mean: 'PNT'? > > > Can someone explain what I am doing wrong? What happens when the advice is followed? Not sure why declare type-alias and then don't use it, but if insist on using class-name will be making a "forward-reference" (because class has not yet been fully defined) - see https://mypy.readthedocs.io/en/stable/cheat_sheet_py3.html#forward-references -- Regards, =dn From dieter at handshake.de Sun Oct 22 13:35:13 2023 From: dieter at handshake.de (Dieter Maurer) Date: Sun, 22 Oct 2023 19:35:13 +0200 Subject: Simple webserver In-Reply-To: References: <874jilypgs.fsf@nightsong.com> Message-ID: <25909.23889.928949.930486@ixdm.fritz.box> Janis Papanagnou wrote at 2023-10-21 04:03 +0200: > ... >I'd like to ask; where do you see the specific risks with Python >(as language per se) and it's (web-socket-)libraries here? The web server in Python's runtime library is fairly simple, focusing only on the HTTP requirements. You might want additional things for an HTTP server exposed on the internet which should potentially handle high trafic: e.g. * detection of and (partial) protection against denial of service attacks, * load balancing, * virtual hosting * proxing * URL rewriting * high throughput, low latency Depending on your requirements, other web servers might be preferable. From cs at cskk.id.au Sun Oct 22 18:06:54 2023 From: cs at cskk.id.au (Cameron Simpson) Date: Mon, 23 Oct 2023 09:06:54 +1100 Subject: return type same as class gives NameError. In-Reply-To: References: Message-ID: On 22Oct2023 17:50, Antoon Pardon wrote: >I have the following small module: >=-=-=-=-=-=-=-=-=-=-=-= 8< =-=-=-=-=-=-=-=-=-=-=-=-= >class Pnt (NamedTuple): > x: float > y: float > > def __add__(self, other: PNT) -> Pnt: > return Pnt(self[0] + other[0], self[1] + other[1]) When this function is defined, the class "Pnt" has not yet been defined. That happens afterwards. You want a forward reference, eg: def __add__(self, other: PNT) -> "Pnt": A type checker will resolve this after the fact, when it encounters the string in the type annotation. This message: NameError: name 'Pnt' is not defined. Did you mean: 'PNT'? is unfortunate, because you have a very similar "PNT" name in scope. But it isn't what you want. Cheers, Cameron Simpson From o1bigtenor at gmail.com Tue Oct 24 08:22:22 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Tue, 24 Oct 2023 07:22:22 -0500 Subject: Question(s) Message-ID: Greetings (Sorry for a nebulous subject but dunno how to have a short title for a complex question.) I have been using computers for a long time but am only beginning my foray into the galaxy of programming. Have done little to this point besides collection of information on sensors and working on the logic of what I wish to accomplish. Have been reading code that accompanies other's projects in the process of self development. Is there a way to verify that a program is going to do what it is supposed to do even before all the hardware has been assembled and installed and tested? (Many years ago I remember an article (if not an issue) in Byte magazine about mathematically proven constructs a.k.a. programs - - - this idea is what I'm pursuing. The concept is that in non-trivial programs there are plenty of places where a poorly placed symbol or lack of a character will result in at best an inaccurate result and at worst - - - no result. This is the kind of thing (correct code) that I'm hoping to accomplish - - - to rephrase the question - - - how do I test for that?) TIA From pozzugno at gmail.com Tue Oct 24 12:01:39 2023 From: pozzugno at gmail.com (pozz) Date: Tue, 24 Oct 2023 18:01:39 +0200 Subject: Simple webserver In-Reply-To: References: Message-ID: Il 19/10/2023 00:09, Janis Papanagnou ha scritto: > I am pondering about writing a client/server software with > websockets as communication protocol. The clients will run > in browser as Javascript programs and the server may be in > any (any sensible) programming language running standalone > to be connected remotely by the browser-based JS clients. > > I found a Python sample[*] but I am neither familiar with > Python nor with the 'simple_websocket_server' package that > is used in that sample code. But the code looks so simple > that I'm considering to learn and use Python for the task. > > The requirements I have are quite simple; I want to get the > client "address"/identifier from an incoming message, store > it in a list, and send responses to all active clients for > which addresses have been stored. > > Can anyone tell me whether a simple extension of that "echo > incoming message" sample[*] would be easily possible with > Python and with that 'simple_websocket_server' package used? > > Thanks for any hints (or search keywords, or code samples)! > > Janis > > [*] https://pypi.org/project/simple-websocket-server/ I'm not sure, but MQTT protocol could help for this application. From dom.grigonis at gmail.com Tue Oct 24 15:49:00 2023 From: dom.grigonis at gmail.com (Dom Grigonis) Date: Tue, 24 Oct 2023 22:49:00 +0300 Subject: Question(s) In-Reply-To: References: Message-ID: I don?t think there i a simple answer to this, although if you find something interesting, please share. From my experience, industry is applying variety of testing methods. Starting from lowest level components and implementing unit tests, finishing with end-to-end testing platforms. https://www.atlassian.com/continuous-delivery/software-testing/types-of-software-testing Modular programming paradigm, IMO, is one of the solutions to this problem. Then, each component is a flexible program in itself that can be combined with others. This way, code is re-used by many people and code is well tested and issues are quick to surface. As far as I know, unix/linux has a big emphasis on modularity in contrast with monolithic approach of windows, which could be one of the big reasons why (at least from my perspective) working in unix environment is so much more pleasant. https://en.wikipedia.org/wiki/Unix_philosophy Regards, DG > On 24 Oct 2023, at 15:22, o1bigtenor via Python-list wrote: > > Greetings > > (Sorry for a nebulous subject but dunno how to have a short title for > a complex question.) > > I have been using computers for a long time but am only beginning my > foray into the > galaxy of programming. Have done little to this point besides > collection of information > on sensors and working on the logic of what I wish to accomplish. Have > been reading code that accompanies other's projects in the process of > self development. > > Is there a way to verify that a program is going to do what it is > supposed to do even > before all the hardware has been assembled and installed and tested? > > (Many years ago I remember an article (if not an issue) in Byte magazine about > mathematically proven constructs a.k.a. programs - - - this idea is > what I'm pursuing. > The concept is that in non-trivial programs there are plenty of places where a > poorly placed symbol or lack of a character will result in at best an inaccurate > result and at worst - - - no result. This is the kind of thing > (correct code) that I'm > hoping to accomplish - - - to rephrase the question - - - how do I > test for that?) > > TIA > -- > https://mail.python.org/mailman/listinfo/python-list From grant.b.edwards at gmail.com Tue Oct 24 14:39:51 2023 From: grant.b.edwards at gmail.com (Grant Edwards) Date: Tue, 24 Oct 2023 11:39:51 -0700 (PDT) Subject: Question(s) References: Message-ID: <65380f77.050a0220.88dc6.3e37@mx.google.com> On 2023-10-24, o1bigtenor via Python-list wrote: > Is there a way to verify that a program is going to do what it is > supposed to do even before all the hardware has been assembled and > installed and tested? It depends on what you mean by "verify ...". If you want to prove a program correct (in the mathematical sense), then the practical answer is no. It's possible to prove _some_ programs correct, but they tend to be uselessly trivial. For real programs, the best you can do is choose a good set of test cases and test them. If you can simulate the various inputs and collect the outputs, then you can do testing before you have real target hardware. From dan at djph.net Tue Oct 24 14:43:42 2023 From: dan at djph.net (Dan Purgert) Date: Tue, 24 Oct 2023 18:43:42 -0000 (UTC) Subject: Question(s) References: Message-ID: On 2023-10-24, o1bigtenor wrote: > Greetings > > (Sorry for a nebulous subject but dunno how to have a short title for > a complex question.) > [...] > Is there a way to verify that a program is going to do what it is > supposed to do even > before all the hardware has been assembled and installed and tested? In short, no. Reality is a mess, and even if you've programmed/perfectly/ to the datasheets (and passed our unit-tests that are also based on those datasheets), a piece of hardware may not actually conform to what's written. Maybe the sheet is wrong, maybe the hardware is faulty, etc. -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 From grant.b.edwards at gmail.com Tue Oct 24 17:51:56 2023 From: grant.b.edwards at gmail.com (Grant Edwards) Date: Tue, 24 Oct 2023 14:51:56 -0700 (PDT) Subject: Question(s) References: Message-ID: <65383c7c.020a0220.e1cf4.3d17@mx.google.com> On 2023-10-24, Dan Purgert via Python-list wrote: > On 2023-10-24, o1bigtenor wrote: >> Greetings >> >> (Sorry for a nebulous subject but dunno how to have a short title for >> a complex question.) >> [...] >> Is there a way to verify that a program is going to do what it is >> supposed to do even before all the hardware has been assembled and >> installed and tested? > > In short, no. > > Reality is a mess, and even if you've programmed/perfectly/ to the > datasheets (and passed our unit-tests that are also based on those > datasheets), a piece of hardware may not actually conform to what's > written. Maybe the sheet is wrong, maybe the hardware is faulty, etc. And the specified customer requirements are usually wrong too. Sure, the customer said it is supposed to do X, but what they actually needed was Y. And the protocol spec isn't quite right either. Sure, it says "when A is received reply with B", but what everybody really does is slighty different, and you need to do what everybody else does, or the widget you're talking to won't cooperate. And floating point doesn't really work the way you think it does. Sometimes it does, close-enough, for the test-cases you happened to choose... From barry at barrys-emacs.org Tue Oct 24 18:11:14 2023 From: barry at barrys-emacs.org (Barry) Date: Tue, 24 Oct 2023 23:11:14 +0100 Subject: Question(s) In-Reply-To: References: Message-ID: <6040327B-CFB3-4EED-80BC-5D50C7C1ED52@barrys-emacs.org> > On 24 Oct 2023, at 18:25, o1bigtenor via Python-list wrote: > > Is there a way to verify that a program is going to do what it is > supposed to do In the general case not proven to be not possible. Have a read about the halting problem https://en.wikipedia.org/wiki/Halting_problem It is common to simulate hardware that does not exist yet and run software in the simulated environment. Barry From o1bigtenor at gmail.com Tue Oct 24 18:41:01 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Tue, 24 Oct 2023 17:41:01 -0500 Subject: Question(s) In-Reply-To: <65383c7c.020a0220.e1cf4.3d17@mx.google.com> References: <65383c7c.020a0220.e1cf4.3d17@mx.google.com> Message-ID: On Tue, Oct 24, 2023 at 4:54?PM Grant Edwards via Python-list wrote: > > On 2023-10-24, Dan Purgert via Python-list wrote: > > On 2023-10-24, o1bigtenor wrote: > >> Greetings > >> > >> (Sorry for a nebulous subject but dunno how to have a short title for > >> a complex question.) > >> [...] > >> Is there a way to verify that a program is going to do what it is > >> supposed to do even before all the hardware has been assembled and > >> installed and tested? > > > > In short, no. > > > > Reality is a mess, and even if you've programmed/perfectly/ to the > > datasheets (and passed our unit-tests that are also based on those > > datasheets), a piece of hardware may not actually conform to what's > > written. Maybe the sheet is wrong, maybe the hardware is faulty, etc. > > And the specified customer requirements are usually wrong too. Sure, > the customer said it is supposed to do X, but what they actually > needed was Y. > > And the protocol spec isn't quite right either. Sure, it says "when A > is received reply with B", but what everybody really does is slighty > different, and you need to do what everybody else does, or the widget > you're talking to won't cooperate. > > And floating point doesn't really work the way you think it > does. Sometimes it does, close-enough, for the test-cases you happened > to choose... > Fascinating - - - except here I get to wear almost all of the hats. I'm putting together the hardware, I get to do the programming and I will be running the completed equipment. I am asking so that I'm not chasing my tail for inordinate amounts of time - - - grin! Interesting ideas so far. From list1 at tompassin.net Tue Oct 24 18:50:32 2023 From: list1 at tompassin.net (Thomas Passin) Date: Tue, 24 Oct 2023 18:50:32 -0400 Subject: Question(s) In-Reply-To: References: Message-ID: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> On 10/24/2023 8:22 AM, o1bigtenor via Python-list wrote: > Greetings > > (Sorry for a nebulous subject but dunno how to have a short title for > a complex question.) > > I have been using computers for a long time but am only beginning my > foray into the > galaxy of programming. Have done little to this point besides > collection of information > on sensors and working on the logic of what I wish to accomplish. Have > been reading code that accompanies other's projects in the process of > self development. > > Is there a way to verify that a program is going to do what it is > supposed to do even > before all the hardware has been assembled and installed and tested? > > (Many years ago I remember an article (if not an issue) in Byte magazine about > mathematically proven constructs a.k.a. programs - - - this idea is > what I'm pursuing. > The concept is that in non-trivial programs there are plenty of places where a > poorly placed symbol or lack of a character will result in at best an inaccurate > result and at worst - - - no result. This is the kind of thing > (correct code) that I'm > hoping to accomplish - - - to rephrase the question - - - how do I > test for that?) > > TIA By now you have read many responses that basically say that you cannot prove that a given program has no errors, even apart from the hardware question. Even if it could be done, the kind of specification that you would need would in itself be difficult to create, read, and understand, and would be subject to bugs itself. Something less ambitious than a full proof of correctness of an arbitrary program can sometimes be achieved. The programming team for the Apollo moon mission developed a system which, if you would write your requirements in a certain way, could generate correct C code for them. You won't be doing that. Here I want to point out something else. You say you are just getting into programming. You are going to be making many mistakes and errors, and there will be many things about programming you won't understand until you get some good solid experience. That's not anything to do with you personally, that's just how it will play out. So be prepared to learn from your mistakes and bugs. They are how you learn the nuts and bolts of the business of programming. From o1bigtenor at gmail.com Tue Oct 24 19:08:37 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Tue, 24 Oct 2023 18:08:37 -0500 Subject: Question(s) In-Reply-To: References: Message-ID: On Tue, Oct 24, 2023 at 5:28?PM Rob Cliffe wrote: > > There is no general way to prove that a program is "correct". Or even > whether it will terminate or loop endlessly. > These are of course theoretical statements of computer science. But > they can be rigorously proven. (Sorry if I'm just saying this to show > what a smart-ass I am. ?) > In practice, of course, there is often a great deal that can be done to > "verify" (a word whose meaning I intentionally leave vague) a program's > correctness. > In your case, it sounds as if you should > > Write programs or functions to simulate each piece of hardware and > generate random, but reasonably realistic, data. (Python and most other > programming languages provide means of generating random or > pseudo-random data.) > In your main program: > Replace the bits of code that accept data from the hardware by > bits of code that accept data from these simulation programs/functions. > Write the decisions it makes to a log file (or files). > Run the program as long as you can or until your patience is > exhausted, and check from the log file(s) that it is behaving as you > would expect. > > This is not guaranteed to catch all possible errors. (Nothing is.) E.g. > The original code to accept data from the hardware (code that you > remove in your test version of the program) might be wrong. Duh! > There might be specific sets of input data that happen not to arise > in your testing, but that your program logic does not cope with. > Nonetheless, this sort of testing (if done diligently) can give you a > high degree of confidence in your program. > And it is a good idea to do it. > When you come to run your program "for real", and you have to > troubleshoot it (as in real life you probably will?), you will have > eliminated simple bugs in your program, and can concentrate on the more > likely sources of problems (e.g. misbehaving hardware). > Interesting - - - hopefully taken in the same vein as your second statement - - I sorta sounds like programmers keep running around in the forest looking for trees. (Grin!) So how does one test software then? Tia From o1bigtenor at gmail.com Tue Oct 24 19:15:15 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Tue, 24 Oct 2023 18:15:15 -0500 Subject: Question(s) In-Reply-To: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On Tue, Oct 24, 2023 at 6:09?PM Thomas Passin via Python-list wrote: > snip > > By now you have read many responses that basically say that you cannot > prove that a given program has no errors, even apart from the hardware > question. Even if it could be done, the kind of specification that you > would need would in itself be difficult to create, read, and understand, > and would be subject to bugs itself. > > Something less ambitious than a full proof of correctness of an > arbitrary program can sometimes be achieved. The programming team for > the Apollo moon mission developed a system which, if you would write > your requirements in a certain way, could generate correct C code for them. > > You won't be doing that. > > Here I want to point out something else. You say you are just getting > into programming. You are going to be making many mistakes and errors, > and there will be many things about programming you won't understand > until you get some good solid experience. That's not anything to do > with you personally, that's just how it will play out. > > So be prepared to learn from your mistakes and bugs. They are how you > learn the nuts and bolts of the business of programming. > I am fully expecting to make mistakes (grin!). I have a couple trades tickets - - - I've done more than a touch of technical learning so mistakes are not scary. What is interesting about this is the absolute certainty that it is impossible to program so that that program is provably correct. Somehow - - - well - - to me that sounds that programming is illogical. If I set up a set of mathematical problems (linked) I can prove that the logic structure of my answer is correct. That's what I'm looking to do with the programming. (Is that different than the question(s) that I've asked - - - dunno.) Stimulating interaction for sure (grin!). From grant.b.edwards at gmail.com Tue Oct 24 19:37:22 2023 From: grant.b.edwards at gmail.com (Grant Edwards) Date: Tue, 24 Oct 2023 16:37:22 -0700 (PDT) Subject: Question(s) References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: <65385532.050a0220.a5f30.3ea2@mx.google.com> On 2023-10-24, Thomas Passin via Python-list wrote: > Something less ambitious than a full proof of correctness of an > arbitrary program can sometimes be achieved. The programming team > for the Apollo moon mission developed a system which, if you would > write your requirements in a certain way, could generate correct C > code for them. Er, what? C didnt' exist until after the Apollo program was done. FORTRAN, perhaps? From grant.b.edwards at gmail.com Tue Oct 24 19:40:30 2023 From: grant.b.edwards at gmail.com (Grant Edwards) Date: Tue, 24 Oct 2023 16:40:30 -0700 (PDT) Subject: Question(s) References: Message-ID: <653855ee.5e0a0220.2dc3.3d42@mx.google.com> On 2023-10-24, o1bigtenor via Python-list wrote: > So how does one test software then? That's what customers are for! [Actually, that's true more often than it should be.] From learn2program at gmail.com Tue Oct 24 19:58:02 2023 From: learn2program at gmail.com (Alan Gauld) Date: Wed, 25 Oct 2023 00:58:02 +0100 Subject: Question(s) In-Reply-To: <65383c7c.020a0220.e1cf4.3d17@mx.google.com> References: <65383c7c.020a0220.e1cf4.3d17@mx.google.com> Message-ID: <5743f5db-a1e0-9f14-a65a-1aa5a728a22c@yahoo.co.uk> On 24/10/2023 22:51, Grant Edwards via Python-list wrote: >>> Is there a way to verify that a program is going to do what it is >>> supposed to do even before all the hardware has been assembled and >>> installed and tested? > And the specified customer requirements are usually wrong too. Sure, > the customer said it is supposed to do X, but what they actually > needed was Y. And this is the hardest bit, specifying exactly what you want at a level that can be formally verified. I worked on some safety critical systems a while back(1990s) and we had to formally verify the core (non UI) code. We did this, but it still failed in some scenarios because we verified it against faulty specs which, in turn, were based on the customer's incorrectly stated requirements. Garbage-In-Garbage-Out still applies. Was the 3 months of formal analysis a waste of time? No, we still caught lots of subtle stuff that might have been missed, but it wasn't 100%. The bugs we did have were caught and identified during system tests. So far as I know, nobody has died as a result of any bugs in that system. But, to the OP, the effort in a) Learning the math and gaining experience for formal analysis and b) actually performing such an analysis of real design/code is simply not worth the effort for 99% of the programs you will write. It is much simpler and faster to just test. And test again. And again. Especially if you use automated testing tools which is the norm nowadays. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos From learn2program at gmail.com Tue Oct 24 20:13:37 2023 From: learn2program at gmail.com (Alan Gauld) Date: Wed, 25 Oct 2023 01:13:37 +0100 Subject: Question(s) In-Reply-To: References: Message-ID: <802cb94f-ad33-e298-37df-400da5f53845@yahoo.co.uk> On 25/10/2023 00:08, o1bigtenor via Python-list wrote: > So how does one test software then? Testing is very different to proving! As an industry we do a lot of testing at many different levels. On bigger projects you'll find: - Unit tests - testing small fragments of a bigger program - Integration tests - testing that sub modules of code work together (and code with hardware, if applicable) - System testing - checking that the code(and hardware) as a whole does what it should based on the specs (often done by an independent team) - Performance testing - checking the system runs as fast as it should, using only the memory it should, for as long as it should. - User testing - Can a real user drive it? - security testing - Does it stop the bad guys from messing it up or using it as a gateway? And there are more levels if you are really keen. Testing often(usually!) takes up more time than programming. And there are many, many books written about how to do it. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos From list1 at tompassin.net Tue Oct 24 21:10:13 2023 From: list1 at tompassin.net (Thomas Passin) Date: Tue, 24 Oct 2023 21:10:13 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On 10/24/2023 7:15 PM, o1bigtenor wrote: > On Tue, Oct 24, 2023 at 6:09?PM Thomas Passin via Python-list > wrote: >> > snip >> >> By now you have read many responses that basically say that you cannot >> prove that a given program has no errors, even apart from the hardware >> question. Even if it could be done, the kind of specification that you >> would need would in itself be difficult to create, read, and understand, >> and would be subject to bugs itself. >> >> Something less ambitious than a full proof of correctness of an >> arbitrary program can sometimes be achieved. The programming team for >> the Apollo moon mission developed a system which, if you would write >> your requirements in a certain way, could generate correct C code for them. >> >> You won't be doing that. >> >> Here I want to point out something else. You say you are just getting >> into programming. You are going to be making many mistakes and errors, >> and there will be many things about programming you won't understand >> until you get some good solid experience. That's not anything to do >> with you personally, that's just how it will play out. >> >> So be prepared to learn from your mistakes and bugs. They are how you >> learn the nuts and bolts of the business of programming. >> > > I am fully expecting to make mistakes (grin!). > I have a couple trades tickets - - - I've done more than a touch of technical > learning so mistakes are not scary. > > What is interesting about this is the absolute certainty that it is impossible > to program so that that program is provably correct. > Somehow - - - well - - to me that sounds that programming is illogical. > > If I set up a set of mathematical problems (linked) I can prove that the > logic structure of my answer is correct. In general, that's not the case - CF Godel's Theorem. There are true arithmetical statements that cannot be proven to be true within the axioms of arithmetic. There's a counterpart in programming called the halting problem. Can an arbitrary computer program be proven to ever finish - to come to a halt (meaning basically to spit out a computed result)? Not in general. If it will never halt you can never check its computation. This doesn't mean that no program can ever be proven to halt, nor that no program can never be proven correct by formal means. Will your program be one of those? The answer may never come ... > That's what I'm looking to do with the programming. > > (Is that different than the question(s) that I've asked - - - dunno.) > > Stimulating interaction for sure (grin!). > From avi.e.gross at gmail.com Tue Oct 24 21:19:17 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Tue, 24 Oct 2023 21:19:17 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: <062901da06e1$46a074e0$d3e15ea0$@gmail.com> Whoa! The question cannot be about whether it is possible to prove any abstract program will be correct and especially not on real hardware that can fail in various ways or have unexpected race conditions or interacts with other places such as over the internet. It has been quite well proven (think Kurt G?del) that any system as complex as just arithmetic can have propositions that can neither be proven as true or as false and could be either. So there will be logical setups, written perhaps into the form of programs, that cannot be proven to work right, or even just halt someday when done. The real question is way more detailed and complex. How does one create a complex program while taking care to minimize as well as you can the chances it is flawed under some conditions. There are walls of books written on such topics and they range from ways to write the software, perhaps in small modules that can be tested and then combined into larger subunits that can also be tested. There are compilers/interpreters/linters and sometimes ways of declaring your intentions to them, that can catch some kinds of possible errors, or force you to find another way to do things. You can hire teams of people to create test cases and try them or automate them. You can fill the code with all kinds of tests and conditionals even at run time that guarantee to handle any kinds of data/arguments handed to it and do something valid or fail with stated reasons. You can generate all kinds of logs to help establish the right things are happening or catch some errors. But all that gets you typically is fewer bugs and software that is very expensive to create and decades to produce and by that time, you have lost your market to others who settle for less. Consider an example of bit rot. I mean what if your CPU or hard disk has a location where you can write a byte and read it back multiple times and sometimes get the wrong result. To be really cautions, you might need your software to write something in multiple locations and when it reads it back in, check all of them and if most agree, ignore the one or two that don't while blocking that memory area off and moving your data elsewhere. Or consider a memory leak that happens rarely but if a program runs for years or decades, may end up causing an unanticipated error. You can only do so much. So once you have some idea what language you want to use and what development environment and so on, research what tools and methods are available and see what you can afford to do. But if you have also not chosen your target architecture and are being asked to GUARANTEE things from afar, that opens a whole new set of issues. I was on a project once where we had a sort of networked system of machines exchanging things like email and we tested it. A while later, we decided to buy and add more machines of a new kind and had a heterogeneous network. Unfortunately, some tests had not been done with messages of a size that turned out to not be allowed on one set of machines as too big but were allowed on the other that had a higher limit. We caught the error in the field when a message of that size was sent and then got caught in junkmail later as the receiving or intermediate machine was not expecting to be the one dealing with it. We then lowered the maximum allowed size on all architectures to the capacity of the weakest one. This reminds me a bit of questions about languages that are free and come pretty much without guarantees or support. Is it safe to use them? I mean could they be harboring back doors or spying on you? Will you get a guarantee they won't switch to a version 3.0 that is incompatible with some features your software used? The short answer is there are no guarantees albeit maybe you can purchase some assurances and services from some third party who might be able to help you with the open-source software. Unless your project accepts the realities, why start? -----Original Message----- From: Python-list On Behalf Of o1bigtenor via Python-list Sent: Tuesday, October 24, 2023 7:15 PM To: Thomas Passin Cc: python-list at python.org Subject: Re: Question(s) On Tue, Oct 24, 2023 at 6:09?PM Thomas Passin via Python-list wrote: > snip > > By now you have read many responses that basically say that you cannot > prove that a given program has no errors, even apart from the hardware > question. Even if it could be done, the kind of specification that you > would need would in itself be difficult to create, read, and understand, > and would be subject to bugs itself. > > Something less ambitious than a full proof of correctness of an > arbitrary program can sometimes be achieved. The programming team for > the Apollo moon mission developed a system which, if you would write > your requirements in a certain way, could generate correct C code for them. > > You won't be doing that. > > Here I want to point out something else. You say you are just getting > into programming. You are going to be making many mistakes and errors, > and there will be many things about programming you won't understand > until you get some good solid experience. That's not anything to do > with you personally, that's just how it will play out. > > So be prepared to learn from your mistakes and bugs. They are how you > learn the nuts and bolts of the business of programming. > I am fully expecting to make mistakes (grin!). I have a couple trades tickets - - - I've done more than a touch of technical learning so mistakes are not scary. What is interesting about this is the absolute certainty that it is impossible to program so that that program is provably correct. Somehow - - - well - - to me that sounds that programming is illogical. If I set up a set of mathematical problems (linked) I can prove that the logic structure of my answer is correct. That's what I'm looking to do with the programming. (Is that different than the question(s) that I've asked - - - dunno.) Stimulating interaction for sure (grin!). -- https://mail.python.org/mailman/listinfo/python-list From rosuav at gmail.com Tue Oct 24 21:32:46 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 25 Oct 2023 12:32:46 +1100 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On Wed, 25 Oct 2023 at 12:11, Thomas Passin via Python-list wrote: > This doesn't mean that no program can ever be proven to halt, nor that > no program can never be proven correct by formal means. Will your > program be one of those? The answer may never come ... Indeed, and I would go further and say that, in any non-trivial system, it is impossible to completely 100% prove that it is perfectly correct. Sometimes you might have perfect mathematics and software, but only subject to certain assumptions about the environment. Or about the users. More commonly, you build a system so that failure becomes vanishingly unlikely. Take space flight as an example. Computers have been vital to the safety of human lives in space pretty much since humans have been going to space at all. How do you make sure that the Apollo Guidance Computer works correctly when you need it to? Multiple layers of protection. Error correcting memory, redundant systems, and human monitoring, plus the ability to rewrite the guidance software on the fly if they needed to. Even when people are being sent to the moon, you can't completely guarantee that the software is perfect, so you add other layers to give greater protection. (And more recently, both India's "Chandrayaan 2" and Japan's "Hakuto-R" unmanned moon missions crash-landed due to software issues. A half century of improvements hasn't changed the fundamental fact that building a perfect system is basically impossible.) So is all hope lost? No. We learn from our mistakes, we add more layers. And ultimately, we test until we're reasonably confident, and then go with it, knowing that failures WILL happen. Your goal as a programmer isn't to prevent failure altogether - if it were, you would never be able to achieve anything. Your goal is to catch those failures before they cause major issues. 1. Catch the failure as you're typing in code. Done, fixed, that's what the Backspace key is for. 2. Catch the failure as you save. We have a lot of tools that can help you to spot bugs. 3. Catch the failure before you commit and push. Unit tests are great for this. 4. Catch the failure collaboratively. Other developers can help. Or you can use automated tests that run on a bot farm, checking your code on a variety of different systems (see for example Python's buildbots). 5. Catch the failure in alpha. Release to a small number of willing users first. They get rewarded with cool new features before everyone else does, in return for having fewer guarantees. 6. If all else fails, catch the failure before it kills someone. Design your system so that failures are contained. That's easier for some than others, but it's part of why I've been saying "system" here rather than "program". Eff up like it's your job. https://thedailywtf.com/articles/eff-up-like-it-s-your-job ChrisA From rosuav at gmail.com Tue Oct 24 21:41:10 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 25 Oct 2023 12:41:10 +1100 Subject: Question(s) In-Reply-To: <062901da06e1$46a074e0$d3e15ea0$@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <062901da06e1$46a074e0$d3e15ea0$@gmail.com> Message-ID: On Wed, 25 Oct 2023 at 12:20, AVI GROSS via Python-list wrote: > Consider an example of bit rot. I mean what if your CPU or hard disk has a location where you can write a byte and read it back multiple times and sometimes get the wrong result. To be really cautions, you might need your software to write something in multiple locations and when it reads it back in, check all of them and if most agree, ignore the one or two that don't while blocking that memory area off and moving your data elsewhere. Or consider a memory leak that happens rarely but if a program runs for years or decades, may end up causing an unanticipated error. > True, but there are FAR more efficient ways to do error correction :) Hamming codes give you single-bit correction and two-bit detection at a cost of log N bits, which is incredibly cheap - even if you were to go for a granularity of 64 bytes (one cache line in a modern Intel CPU), you would need just 11 bits of Hamming code for every 512 bits of data and you can guarantee to fix any single-bit error in any cache line. The "if most agree, ignore the one or two that don't" design implies that you're writing to an absolute minimum of three places, and in order to be able to ignore two that disagree, you'd probably need five copies of everything - that is to say, to store 512 bits of data, you would need 2560 bits of storage. But with a Hamming code, you need just 523 bits to store 512 reliably. Here's a great run-down on how efficiently this can be done, and how easily. https://www.youtube.com/watch?v=X8jsijhllIA Side note: If we assume that random bit flips occur at a rate of one every X storage bits, having redundant copies of data will increase the chances of a failure happening. For example, using a naive and horrendously wasteful "store 256 copies of everything" strategy, you would be 256 times more likely to have a random bitflip, which is insane :) You would also be able to guarantee detection of up to 128 random bitflips. But as you can see, this puts a maximum on your storage ratio. ChrisA From michw6 at gmail.com Tue Oct 24 20:58:25 2023 From: michw6 at gmail.com (Mike H) Date: Tue, 24 Oct 2023 17:58:25 -0700 (PDT) Subject: How to sort this without 'cmp=' in python 3? In-Reply-To: References: <716092e7-c9ab-4a8b-a157-c3c3357620fb@googlegroups.com> Message-ID: <831f18ce-eb79-48f8-8f4a-7f9033398988n@googlegroups.com> On Saturday, October 15, 2016 at 12:27:42?AM UTC-7, Peter Otten wrote: > 38016... at gmail.com wrote: > > > nums=['3','30','34','32','9','5'] > > I need to sort the list in order to get the largest number string: > > '953433230' > > > > nums.sort(cmp=lambda a,b: cmp(a+b, b+a), reverse=True) > > > > But how to do this in python 3? > > > > Thank you > While cmp_to_key is neat doing it by hand should also be instructive. > Essentially you move the comparison into a method of the key: > > $ cat translate_cmp.py > class Key(str): > def __lt__(a, b): > return a + b < b + a > > nums = ['3','30','34','32','9','5'] > print(nums) > nums.sort(key=Key, reverse=True) > print(nums) > print("".join(nums)) > > $ python3 translate_cmp.py > ['3', '30', '34', '32', '9', '5'] > ['9', '5', '34', '3', '32', '30'] > 953433230 > > The above works because in CPython list.sort() currently uses only the < > operator; adding __gt__() and __eq__() to make this portable is > straightforward even if you do not use the functools.total_ordering class > decorator. Is it possible to use lambda expression instead of defining a `Key` class? Something like `sorted(my_list, key = lambda x, y: x+y > y+x)`? From rosuav at gmail.com Tue Oct 24 22:12:01 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 25 Oct 2023 13:12:01 +1100 Subject: How to sort this without 'cmp=' in python 3? In-Reply-To: <831f18ce-eb79-48f8-8f4a-7f9033398988n@googlegroups.com> References: <716092e7-c9ab-4a8b-a157-c3c3357620fb@googlegroups.com> <831f18ce-eb79-48f8-8f4a-7f9033398988n@googlegroups.com> Message-ID: On Wed, 25 Oct 2023 at 13:02, Mike H via Python-list wrote: > Is it possible to use lambda expression instead of defining a `Key` class? Something like `sorted(my_list, key = lambda x, y: x+y > y+x)`? Look up functools.cmp_to_key. ChrisA From avi.e.gross at gmail.com Tue Oct 24 22:33:41 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Tue, 24 Oct 2023 22:33:41 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <062901da06e1$46a074e0$d3e15ea0$@gmail.com> Message-ID: <064f01da06eb$ab60a5d0$0221f170$@gmail.com> Agreed, Chris. There are many methods way better than the sort of RAID architecture I supplied as AN EXAMPLE easy to understand. But even so, if a hard disk or memory chip is fried or a nuclear bomb takes out all servers in or near a city, you would need some truly crazy architectures with info not only distributed across the globe but perhaps also to various space satellites or servers kept ever further out and eventually in hyperspace or within a black hole (might be write-only, alas). The point many of us keep saying is there can not easily or even with great difficult, any perfect scheme that guarantees nothing will go wrong with the software, hardware, the people using it and so on. And in the real world, as compared to the reel world, many programs cannot remain static. Picture a program that includes many tax laws and implementations that has to be changed at least yearly as laws change. Some near-perfect code now has to either be patched with lots of errors possible, or redesigned from scratch and if it takes long enough, will come out after yet more changes and thus be wrong. A decent question you can ask is if the language this forum is supposed to be on, is better in some ways to provide the kind of Teflon-coated code he wants. Are there features better avoided? How do you make sure updates to modules you use and trust are managed as they may break your code. Stuff like that is not as abstract. In my view, one consideration can be that when people can examine your source code in the original language, that can open up ways others might find ways to break it, more so than a compiled program that you only can read in a more opaque way. -----Original Message----- From: Python-list On Behalf Of Chris Angelico via Python-list Sent: Tuesday, October 24, 2023 9:41 PM To: python-list at python.org Subject: Re: Question(s) On Wed, 25 Oct 2023 at 12:20, AVI GROSS via Python-list wrote: > Consider an example of bit rot. I mean what if your CPU or hard disk has a location where you can write a byte and read it back multiple times and sometimes get the wrong result. To be really cautions, you might need your software to write something in multiple locations and when it reads it back in, check all of them and if most agree, ignore the one or two that don't while blocking that memory area off and moving your data elsewhere. Or consider a memory leak that happens rarely but if a program runs for years or decades, may end up causing an unanticipated error. > True, but there are FAR more efficient ways to do error correction :) Hamming codes give you single-bit correction and two-bit detection at a cost of log N bits, which is incredibly cheap - even if you were to go for a granularity of 64 bytes (one cache line in a modern Intel CPU), you would need just 11 bits of Hamming code for every 512 bits of data and you can guarantee to fix any single-bit error in any cache line. The "if most agree, ignore the one or two that don't" design implies that you're writing to an absolute minimum of three places, and in order to be able to ignore two that disagree, you'd probably need five copies of everything - that is to say, to store 512 bits of data, you would need 2560 bits of storage. But with a Hamming code, you need just 523 bits to store 512 reliably. Here's a great run-down on how efficiently this can be done, and how easily. https://www.youtube.com/watch?v=X8jsijhllIA Side note: If we assume that random bit flips occur at a rate of one every X storage bits, having redundant copies of data will increase the chances of a failure happening. For example, using a naive and horrendously wasteful "store 256 copies of everything" strategy, you would be 256 times more likely to have a random bitflip, which is insane :) You would also be able to guarantee detection of up to 128 random bitflips. But as you can see, this puts a maximum on your storage ratio. ChrisA -- https://mail.python.org/mailman/listinfo/python-list From list1 at tompassin.net Tue Oct 24 21:11:08 2023 From: list1 at tompassin.net (Thomas Passin) Date: Tue, 24 Oct 2023 21:11:08 -0400 Subject: Question(s) In-Reply-To: <65385532.050a0220.a5f30.3ea2@mx.google.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <65385532.050a0220.a5f30.3ea2@mx.google.com> Message-ID: <6f9792e5-5409-4f61-9884-dd45b66675a1@tompassin.net> On 10/24/2023 7:37 PM, Grant Edwards via Python-list wrote: > On 2023-10-24, Thomas Passin via Python-list wrote: > >> Something less ambitious than a full proof of correctness of an >> arbitrary program can sometimes be achieved. The programming team >> for the Apollo moon mission developed a system which, if you would >> write your requirements in a certain way, could generate correct C >> code for them. > > Er, what? > > C didnt' exist until after the Apollo program was done. > > FORTRAN, perhaps? > Sorry, I mixed myself up. The head of the team continued to develop the techniques and market them. It's todays's version that can output C (going from memory a few years old here). Sorry to have confused everyone and myself. From frank at chagford.com Wed Oct 25 03:57:17 2023 From: frank at chagford.com (Frank Millman) Date: Wed, 25 Oct 2023 09:57:17 +0200 Subject: Simple webserver In-Reply-To: <25909.23889.928949.930486@ixdm.fritz.box> References: <874jilypgs.fsf@nightsong.com> <25909.23889.928949.930486@ixdm.fritz.box> Message-ID: On 2023-10-22 7:35 PM, Dieter Maurer via Python-list wrote: > > The web server in Python's runtime library is fairly simple, > focusing only on the HTTP requirements. > > You might want additional things for an HTTP server > exposed on the internet which should potentially handle high trafic: > e.g. > > * detection of and (partial) protection against denial of service attacks, > * load balancing, > * virtual hosting > * proxing > * URL rewriting > * high throughput, low latency > > Depending on your requirements, other web servers might be preferable. Dieter's response was very timely for me, as it provides some answers to a question that I was thinking of posting. My use-case is reasonably on-topic for this thread, so I won't start a new one, if that is ok. I am writing a business/accounting application. The server uses Python and asyncio, the client is written in Javascript. The project is inching towards a point where I may consider releasing it. My concern was whether my home-grown HTTP server was too simplistic for production, and if so, whether I should be looking into using one of the more established frameworks. After some brief investigation into Dieter's list of additional requirements, here are my initial thoughts. Any comments will be welcome. I skimmed through the documentation for flask, Django, and FastAPI. As far as I can tell, none of them address the points listed above directly. Instead, they position themselves as one layer in a stack of technologies, and rely on other layers to provide additional functionality. If I read this correctly, there is nothing to stop me doing the same. Based on this, I am considering the following - 1. Replace my HTTP handler with Uvicorn. Functionality should be the same, but performance should be improved. 2. Instead of running as a stand-alone server, run my app as a reverse-proxy using Nginx. I tested this a few years ago using Apache, and it 'just worked', so I am fairly sure that it will work with Nginx as well. Nginx can then provide the additional functionality that Dieter has mentioned. My main concern is that, if I do release my app, I want it to be taken seriously and not dismissed as 'Mickey Mouse'. Do you think the above changes would assist with that? When I talk about releasing it, it is already available on Github here - https://github.com/FrankMillman/AccInABox. You are welcome to look at it, but it needs a lot of tidying up before it will be ready for a wider audience. Frank Millman From rosuav at gmail.com Wed Oct 25 04:56:20 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 25 Oct 2023 19:56:20 +1100 Subject: Simple webserver In-Reply-To: References: <874jilypgs.fsf@nightsong.com> <25909.23889.928949.930486@ixdm.fritz.box> Message-ID: On Wed, 25 Oct 2023 at 19:00, Frank Millman via Python-list wrote: > 2. Instead of running as a stand-alone server, run my app as a > reverse-proxy using Nginx. I tested this a few years ago using Apache, > and it 'just worked', so I am fairly sure that it will work with Nginx > as well. Nginx can then provide the additional functionality that Dieter > has mentioned. This, I would recommend. In general, tools like Django and Flask and such are aimed at the creation of web apps, but not necessarily web servers; it's convenient to have a high-performance web server like Nginx or Apache, and then it passes along requests to the application server. This provides a number of benefits: 1. Static files can be served directly, without involving the app 2. Need to scale horizontally? Run two or more copies of your app and have the web server share requests among them. 3. App crashed? The web server can return an HTTP 503 error so end users aren't left wondering what's going on. 4. DOS protection can be done in the web server (although it could also be done in a firewall, or any other level that's appropriate) > My main concern is that, if I do release my app, I want it to be taken > seriously and not dismissed as 'Mickey Mouse'. Do you think the above > changes would assist with that? You shouldn't be dismissed as Still-In-Copyright-Decades-Old-Rodent even if you don't make those changes. I've been hosting a number of servers, some fairly home-grade, and nobody's ever told me that it looks bad. If you want to be respected, the main thing is to have something that people find interesting - everything else is secondary. But there are a few points to consider: * Performance. People respect something that's snappy and responsive more than they respect something where a single HTTP request takes anywhere from 2.89 seconds to nearly 30 seconds. And no, I'm totally not still mindblown at having seen this kind of appalling performance from a published and very expensive API. * Have your own domain name. https://rosuav.github.io/AntiSocialMedia/ is a toy; https://devicat.art/ is a professional web site. (They're not related, and the first one really is just a toy that I whipped up in like half an hour.) * Have a proper SSL certificate. It looks *really bad* to have a broken or outdated certificate (or none at all, these days). LetsEncrypt can do that for you, no charge. * Put some effort into styling. Yeah, I know, most of my web sites are ugly, so I shouldn't talk. But things definitely look more professional if you take the time to style them up a bit. > When I talk about releasing it, it is already available on Github here - > https://github.com/FrankMillman/AccInABox. > > You are welcome to look at it, but it needs a lot of tidying up before > it will be ready for a wider audience. Cool! This is particularly of note to me personally. Back in the 90s, I was working in the family business, and we used a fairly clunky piece of professionally-written software (and if you want stories, ask me about overnight runs of report generation, or Ctrl-Alt-Shift and old mouse pedal importing, or 32-bit installers for 16-bit applications, or a bunch of other things). There was, for a while, a theory of us designing our own accounting system, but it turns out, that's a really REALLY big job, and it's less effort to keep using the thing you already have. Your README, dating from 9 years ago, says that you support/require Python 3.4 - that's kinda ancient now. If you want to take advantage of newer features, I think you should be safe bumping that up a long way. :) I wouldn't recommend sqlite3 for any production work here, but it's good for a demo. Postgres is a far better choice if you're going to be storing your vital information in this. You can list vital packages in a file called requirements.txt - this will be recognized by both people and automated tooling. .... huh. I'm listed as a contributor. I'll be quite honest, I do not remember this, but presumably you shared this previously! Looks like all I contributed was a minor suggestion and commit, but still, I have absolutely no memory. LOL. Looks pretty good there. I don't have time right now to download and install it for a proper test, but based on flipping through the code, looks like you have something decent going on. ChrisA From o1bigtenor at gmail.com Wed Oct 25 06:45:55 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 05:45:55 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: A post with useful ideas - - - - thanks (it generates some questions! interleaved) On Tue, Oct 24, 2023 at 8:35?PM Chris Angelico via Python-list wrote: > > On Wed, 25 Oct 2023 at 12:11, Thomas Passin via Python-list > wrote: > > This doesn't mean that no program can ever be proven to halt, nor that > > no program can never be proven correct by formal means. Will your > > program be one of those? The answer may never come ... > snip > So is all hope lost? No. We learn from our mistakes, we add more > layers. And ultimately, we test until we're reasonably confident, and > then go with it, knowing that failures WILL happen. Your goal as a > programmer isn't to prevent failure altogether - if it were, you would > never be able to achieve anything. Your goal is to catch those > failures before they cause major issues. > > 1. Catch the failure as you're typing in code. Done, fixed, that's > what the Backspace key is for. > 2. Catch the failure as you save. We have a lot of tools that can help > you to spot bugs. Tools like this for python please. > 3. Catch the failure before you commit and push. Unit tests are great for this. Where might I find such please. > 4. Catch the failure collaboratively. Other developers can help. Or > you can use automated tests that run on a bot farm, checking your code > on a variety of different systems (see for example Python's > buildbots). This is very interesting - - - grin - - - almost looks like another rabbit hole to climb into though. > 5. Catch the failure in alpha. Release to a small number of willing > users first. They get rewarded with cool new features before everyone > else does, in return for having fewer guarantees. For here its software for use here so I get to wear all the hats. > 6. If all else fails, catch the failure before it kills someone. > Design your system so that failures are contained. That's easier for > some than others, but it's part of why I've been saying "system" here > rather than "program". This will not be an issue here - - - at least not yet. This is software for collecting data to enhance management of things that aren't generally managed in most like outfits. (Or they utilize the 800# gorillas in the industries tools which are bloody pricey.) > > Eff up like it's your job. > https://thedailywtf.com/articles/eff-up-like-it-s-your-job > Very interesting article - - - thanks! TIA From o1bigtenor at gmail.com Wed Oct 25 06:52:46 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 05:52:46 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <062901da06e1$46a074e0$d3e15ea0$@gmail.com> Message-ID: On Tue, Oct 24, 2023 at 8:43?PM Chris Angelico via Python-list wrote: > > On Wed, 25 Oct 2023 at 12:20, AVI GROSS via Python-list > wrote: > > Consider an example of bit rot. I mean what if your CPU or hard disk has a location where you can write a byte and read it back multiple times and sometimes get the wrong result. To be really cautions, you might need your software to write something in multiple locations and when it reads it back in, check all of them and if most agree, ignore the one or two that don't while blocking that memory area off and moving your data elsewhere. Or consider a memory leak that happens rarely but if a program runs for years or decades, may end up causing an unanticipated error. > > > > True, but there are FAR more efficient ways to do error correction :) > Hamming codes give you single-bit correction and two-bit detection at > a cost of log N bits, which is incredibly cheap - even if you were to > go for a granularity of 64 bytes (one cache line in a modern Intel > CPU), you would need just 11 bits of Hamming code for every 512 bits > of data and you can guarantee to fix any single-bit error in any cache > line. The "if most agree, ignore the one or two that don't" design > implies that you're writing to an absolute minimum of three places, > and in order to be able to ignore two that disagree, you'd probably > need five copies of everything - that is to say, to store 512 bits of > data, you would need 2560 bits of storage. But with a Hamming code, > you need just 523 bits to store 512 reliably. > > Here's a great run-down on how efficiently this can be done, and how > easily. https://www.youtube.com/watch?v=X8jsijhllIA > > Side note: If we assume that random bit flips occur at a rate of one > every X storage bits, having redundant copies of data will increase > the chances of a failure happening. For example, using a naive and > horrendously wasteful "store 256 copies of everything" strategy, you > would be 256 times more likely to have a random bitflip, which is > insane :) You would also be able to guarantee detection of up to 128 > random bitflips. But as you can see, this puts a maximum on your > storage ratio. > Hmmmmmmmmmm - - - - now how can I combine 'Hamming codes' and a raid array? TIA From o1bigtenor at gmail.com Wed Oct 25 06:59:05 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 05:59:05 -0500 Subject: Question(s) In-Reply-To: <064f01da06eb$ab60a5d0$0221f170$@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <062901da06e1$46a074e0$d3e15ea0$@gmail.com> <064f01da06eb$ab60a5d0$0221f170$@gmail.com> Message-ID: On Tue, Oct 24, 2023 at 9:36?PM AVI GROSS via Python-list wrote: > > Agreed, Chris. There are many methods way better than the sort of RAID > architecture I supplied as AN EXAMPLE easy to understand. But even so, if a > hard disk or memory chip is fried or a nuclear bomb takes out all servers in > or near a city, you would need some truly crazy architectures with info not > only distributed across the globe but perhaps also to various space > satellites or servers kept ever further out and eventually in hyperspace or > within a black hole (might be write-only, alas). > > The point many of us keep saying is there can not easily or even with great > difficult, any perfect scheme that guarantees nothing will go wrong with the > software, hardware, the people using it and so on. And in the real world, as > compared to the reel world, many programs cannot remain static. Picture a > program that includes many tax laws and implementations that has to be > changed at least yearly as laws change. Some near-perfect code now has to > either be patched with lots of errors possible, or redesigned from scratch > and if it takes long enough, will come out after yet more changes and thus > be wrong. > > A decent question you can ask is if the language this forum is supposed to > be on, is better in some ways to provide the kind of Teflon-coated code he > wants. Are there features better avoided? How do you make sure updates to > modules you use and trust are managed as they may break your code. Stuff > like that is not as abstract. The above are very interesting questions - - - - anyone care to tackle one, or some? > > In my view, one consideration can be that when people can examine your > source code in the original language, that can open up ways others might > find ways to break it, more so than a compiled program that you only can > read in a more opaque way. > (Tongue in cheek) Except doesn't one make more $$$$ when software in hidden in an unreadable state? (That forces the user to go back to the original dev or group - - yes?) TIA From rosuav at gmail.com Wed Oct 25 07:18:21 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 25 Oct 2023 22:18:21 +1100 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On Wed, 25 Oct 2023 at 21:46, o1bigtenor wrote: > > 2. Catch the failure as you save. We have a lot of tools that can help > > you to spot bugs. > > Tools like this for python please. Various ones. Type checkers like MyPy fall into this category if you set your system up to run them when you save. Some editors do basic syntax checks too. > > 3. Catch the failure before you commit and push. Unit tests are great for this. > > Where might I find such please. The same tools, but run as a pre-commit hook. Any tool that can help you find bugs has the potential to be of value. It's all a question of how much time it saves with earlier detection of bugs versus how much it costs you in pacifying the tool. Some are better than others. ChrisA From rosuav at gmail.com Wed Oct 25 07:22:48 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 25 Oct 2023 22:22:48 +1100 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <062901da06e1$46a074e0$d3e15ea0$@gmail.com> Message-ID: On Wed, 25 Oct 2023 at 21:53, o1bigtenor wrote: > > Hmmmmmmmmmm - - - - now how can I combine 'Hamming codes' > and a raid array? > > TIA Normally you wouldn't. But let's say you're worried that a file might get randomly damaged. (I don't think single-bit errors are really a significant issue with mass storage, as you'd be more likely to have an entire sector unreadable, but this can certainly happen in transmission.) What you do is take a set of data bits, add an error correction code, and send them on their way. The more data bits per block, the more efficient, but if there are too many errors you will lose data. So there's a tradeoff. ChrisA From dieter at handshake.de Wed Oct 25 07:24:55 2023 From: dieter at handshake.de (Dieter Maurer) Date: Wed, 25 Oct 2023 13:24:55 +0200 Subject: Question(s) In-Reply-To: References: Message-ID: <25912.64263.558046.607705@ixdm.fritz.box> o1bigtenor wrote at 2023-10-24 07:22 -0500: > ... >Is there a way to verify that a program is going to do what it is >supposed to do even >before all the hardware has been assembled and installed and tested? Others have already noted that "verify" is a very strong aim. There are different kinds of errors. Some can be avoided by using an integrated development environment (e.g. misspellings, type mismatches, ...). Some can be found via tests. Look at Python's "unittest" package for learn how to write tests. "unittest.mock" can help you to mockup hardware you do not yet have. From dieter at handshake.de Wed Oct 25 07:26:34 2023 From: dieter at handshake.de (Dieter Maurer) Date: Wed, 25 Oct 2023 13:26:34 +0200 Subject: Simple webserver In-Reply-To: References: <874jilypgs.fsf@nightsong.com> <25909.23889.928949.930486@ixdm.fritz.box> Message-ID: <25912.64362.443753.902596@ixdm.fritz.box> Frank Millman wrote at 2023-10-25 09:57 +0200: > ... >Based on this, I am considering the following - > >1. Replace my HTTP handler with Uvicorn. Functionality should be the >same, but performance should be improved. > >2. Instead of running as a stand-alone server, run my app as a >reverse-proxy using Nginx. I tested this a few years ago using Apache, >and it 'just worked', so I am fairly sure that it will work with Nginx >as well. Nginx can then provide the additional functionality that Dieter >has mentioned. Good ideas. From o1bigtenor at gmail.com Wed Oct 25 07:35:49 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 06:35:49 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <062901da06e1$46a074e0$d3e15ea0$@gmail.com> Message-ID: On Wed, Oct 25, 2023 at 6:25?AM Chris Angelico via Python-list wrote: > > On Wed, 25 Oct 2023 at 21:53, o1bigtenor wrote: > > > > Hmmmmmmmmmm - - - - now how can I combine 'Hamming codes' > > and a raid array? > > > > TIA > > Normally you wouldn't. But let's say you're worried that a file might > get randomly damaged. (I don't think single-bit errors are really a > significant issue with mass storage, as you'd be more likely to have > an entire sector unreadable, but this can certainly happen in > transmission.) What you do is take a set of data bits, add an error > correction code, and send them on their way. The more data bits per > block, the more efficient, but if there are too many errors you will > lose data. So there's a tradeoff. > > Thank you Mr Chris! Cogent explanation that makes sense. So - - - no change needed to my storage systems. Great! Regards From o1bigtenor at gmail.com Wed Oct 25 07:44:55 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 06:44:55 -0500 Subject: Question(s) In-Reply-To: <25912.64263.558046.607705@ixdm.fritz.box> References: <25912.64263.558046.607705@ixdm.fritz.box> Message-ID: On Wed, Oct 25, 2023 at 6:24?AM Dieter Maurer wrote: > > o1bigtenor wrote at 2023-10-24 07:22 -0500: > > ... > >Is there a way to verify that a program is going to do what it is > >supposed to do even > >before all the hardware has been assembled and installed and tested? > > Others have already noted that "verify" is a very strong aim. I have worked in environments where everything was 100% tested. Errors were either corrected or one's attendance was uninvited. Powerful impetus to do a good job. > > There are different kinds of errors. > > Some can be avoided by using an integrated development environment > (e.g. misspellings, type mismatches, ...). Haven't heard of a python IDE - - - doesn't mean that there isn't such - - just that I haven't heard of such. Is there a python IDE? > > Some can be found via tests. > Look at Python's "unittest" package for learn how to write tests. > "unittest.mock" can help you to mockup hardware you do not yet have. Thanks - - -more to look into. Regards From rosuav at gmail.com Wed Oct 25 07:48:55 2023 From: rosuav at gmail.com (Chris Angelico) Date: Wed, 25 Oct 2023 22:48:55 +1100 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> Message-ID: On Wed, 25 Oct 2023 at 22:46, o1bigtenor via Python-list wrote: > > On Wed, Oct 25, 2023 at 6:24?AM Dieter Maurer wrote: > > > > o1bigtenor wrote at 2023-10-24 07:22 -0500: > > > ... > > >Is there a way to verify that a program is going to do what it is > > >supposed to do even > > >before all the hardware has been assembled and installed and tested? > > > > Others have already noted that "verify" is a very strong aim. > > I have worked in environments where everything was 100% tested. Errors > were either corrected or one's attendance was uninvited. Powerful impetus > to do a good job. Or powerful impetus to deny that the error was yours. Remember, 100% test coverage does NOT mean the code is perfect. It just means it's tested. ChrisA From o1bigtenor at gmail.com Wed Oct 25 07:51:20 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 06:51:20 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On Wed, Oct 25, 2023 at 6:20?AM Chris Angelico via Python-list wrote: > > On Wed, 25 Oct 2023 at 21:46, o1bigtenor wrote: > > > 2. Catch the failure as you save. We have a lot of tools that can help > > > you to spot bugs. > > > > Tools like this for python please. > > Various ones. Type checkers like MyPy fall into this category if you > set your system up to run them when you save. Some editors do basic > syntax checks too. I have been using geany as a plain text editor for some time. Searching for suggestions for error checking in python I find listed Pylint, Pyflakes and Pycodestyle. Looks like I have another area to investigate. (grin!) > > > > 3. Catch the failure before you commit and push. Unit tests are great for this. > > > > Where might I find such please. > > The same tools, but run as a pre-commit hook. > > Any tool that can help you find bugs has the potential to be of value. > It's all a question of how much time it saves with earlier detection > of bugs versus how much it costs you in pacifying the tool. Some are > better than others. > Any suggestions? TIA From dieter at handshake.de Wed Oct 25 08:00:05 2023 From: dieter at handshake.de (Dieter Maurer) Date: Wed, 25 Oct 2023 14:00:05 +0200 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> Message-ID: <25913.837.809451.477876@ixdm.fritz.box> o1bigtenor wrote at 2023-10-25 06:44 -0500: >On Wed, Oct 25, 2023 at 6:24?AM Dieter Maurer wrote: > ... >> There are different kinds of errors. >> >> Some can be avoided by using an integrated development environment >> (e.g. misspellings, type mismatches, ...). > >Haven't heard of a python IDE - - - doesn't mean that there isn't such - - >just that I haven't heard of such. Is there a python IDE? There are several. Python comes with "IDLE". There are several others, e.g. "ECLIPSE" can be used for Python development. Search for other alternatices. From o1bigtenor at gmail.com Wed Oct 25 08:50:54 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 07:50:54 -0500 Subject: Question(s) In-Reply-To: <25913.837.809451.477876@ixdm.fritz.box> References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> Message-ID: On Wed, Oct 25, 2023 at 7:00?AM Dieter Maurer wrote: > > o1bigtenor wrote at 2023-10-25 06:44 -0500: > >On Wed, Oct 25, 2023 at 6:24?AM Dieter Maurer wrote: > > ... > >> There are different kinds of errors. > >> > >> Some can be avoided by using an integrated development environment > >> (e.g. misspellings, type mismatches, ...). > > > >Haven't heard of a python IDE - - - doesn't mean that there isn't such - - > >just that I haven't heard of such. Is there a python IDE? > > There are several. > > Python comes with "IDLE". > Interesting - - - started looking into this. > There are several others, > e.g. "ECLIPSE" can be used for Python development. Is 'Eclipse' a Windows oriented IDE? (Having a hard time finding linux related information on the website.) > Search for other alternatices. Will do. Thanks for the assistance. From dieter at handshake.de Wed Oct 25 08:56:54 2023 From: dieter at handshake.de (Dieter Maurer) Date: Wed, 25 Oct 2023 14:56:54 +0200 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> Message-ID: <25913.4246.644009.815137@ixdm.fritz.box> o1bigtenor wrote at 2023-10-25 07:50 -0500: >> There are several others, >> e.g. "ECLIPSE" can be used for Python development. > >Is 'Eclipse' a Windows oriented IDE? No. ==> "https://en.wikipedia.org/wiki/Eclipse_(software)" From o1bigtenor at gmail.com Wed Oct 25 09:29:31 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Wed, 25 Oct 2023 08:29:31 -0500 Subject: Question(s) In-Reply-To: <25913.4246.644009.815137@ixdm.fritz.box> References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> <25913.4246.644009.815137@ixdm.fritz.box> Message-ID: On Wed, Oct 25, 2023 at 7:56?AM Dieter Maurer wrote: > > o1bigtenor wrote at 2023-10-25 07:50 -0500: > >> There are several others, > >> e.g. "ECLIPSE" can be used for Python development. > > > >Is 'Eclipse' a Windows oriented IDE? > > No. > ==> "https://en.wikipedia.org/wiki/Eclipse_(software)" It would appear that something has changed. Went to the Eclipse download page, downloaded and verified (using sha-512). Expanded software to # opt . There is absolutely NO mention of anything python - - - java, c and its permutations, 'scientific computing', and some others but nothing python. I may be missing something due to an extreme lack of knowledge. Please advise as to where I might find the 'python' environment in eclipse. TIA From grant.b.edwards at gmail.com Wed Oct 25 09:49:11 2023 From: grant.b.edwards at gmail.com (Grant Edwards) Date: Wed, 25 Oct 2023 06:49:11 -0700 (PDT) Subject: Question(s) References: <25912.64263.558046.607705@ixdm.fritz.box> Message-ID: <65391cd7.050a0220.7283e.3e7b@mx.google.com> On 2023-10-25, o1bigtenor via Python-list wrote: > Haven't heard of a python IDE - - - doesn't mean that there isn't such - - > just that I haven't heard of such. Is there a python IDE? Seriously? Now you're just trolling. google.com/search?q=python+ide&oq=python+ide -- Grant From list1 at tompassin.net Wed Oct 25 09:31:11 2023 From: list1 at tompassin.net (Thomas Passin) Date: Wed, 25 Oct 2023 09:31:11 -0400 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> Message-ID: <638480c4-2ded-4fe4-87bf-5aaa34a69ec2@tompassin.net> On 10/25/2023 9:21 AM, Thomas Passin wrote: > On 10/25/2023 8:50 AM, o1bigtenor via Python-list wrote: >> On Wed, Oct 25, 2023 at 7:00?AM Dieter Maurer >> wrote: >>> >>> o1bigtenor wrote at 2023-10-25 06:44 -0500: >>>> On Wed, Oct 25, 2023 at 6:24?AM Dieter Maurer >>>> wrote: >>>> ... >>>>> There are different kinds of errors. >>>>> >>>>> Some can be avoided by using an integrated development environment >>>>> (e.g. misspellings, type mismatches, ...). >>>> >>>> Haven't heard of a python IDE - - - doesn't mean that there isn't >>>> such - - >>>> just that I haven't heard of such. Is there a python IDE? >>> >>> There are several. >>> >>> Python comes with "IDLE". >>> >> Interesting - - - started looking into this. >> >>> There are several others, >>> e.g. "ECLIPSE" can be used for Python development. >> >> Is 'Eclipse' a Windows oriented IDE? >> (Having a hard time finding linux related? information on the >> website.) >> >>> Search for other alternatices. >> >> Will do. >> >> Thanks for the assistance. > > Pyzo is one possibility - https://pyzo.org The Leo editor is excellent, as long as you are prepared for a steep learning curve - https://github.com/leo-editor/leo-editor It's installable via pip (though there can be fixable install glitches on some Linux distros). From dieter at handshake.de Wed Oct 25 10:10:24 2023 From: dieter at handshake.de (Dieter Maurer) Date: Wed, 25 Oct 2023 16:10:24 +0200 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> <25913.4246.644009.815137@ixdm.fritz.box> Message-ID: <25913.8656.388538.474870@ixdm.fritz.box> o1bigtenor wrote at 2023-10-25 08:29 -0500: > ... >It would appear that something has changed. > >Went to the Eclipse download page, downloaded and verified (using sha-512). >Expanded software to # opt . >There is absolutely NO mention of anything python - - - java, c and >its permutations, >'scientific computing', and some others but nothing python. > >I may be missing something due to an extreme lack of knowledge. > >Please advise as to where I might find the 'python' environment in eclipse. I entered "eclipse python download" in my favorite search engine (=> "ecosia.org") and the second hit gave: "https://marketplace.eclipse.org/content/pydev-python-ide-eclipse". From dan at djph.net Wed Oct 25 05:23:28 2023 From: dan at djph.net (Dan Purgert) Date: Wed, 25 Oct 2023 09:23:28 -0000 (UTC) Subject: Question(s) References: Message-ID: On 2023-10-24, o1bigtenor wrote: > On Tue, Oct 24, 2023 at 5:28?PM Rob Cliffe wrote: >> >> There is no general way to prove that a program is "correct". Or even >> whether it will terminate or loop endlessly. >> [...] >> When you come to run your program "for real", and you have to >> troubleshoot it (as in real life you probably will?), you will have >> eliminated simple bugs in your program, and can concentrate on the more >> likely sources of problems (e.g. misbehaving hardware). >> > Interesting - - - hopefully taken in the same vein as your second > statement - - I sorta sounds like programmers keep running around in > the forest looking for trees. (Grin!) No, you tend to know what parts of the spec are "wrong(tm)" (either in the language you're working in, or the hardware). If it comes to working with customers (as mentioned in one response), you start to learn the questions to get at what they really want (but that's better left to the architect :) ) > > So how does one test software then? You write unit tests (usually scripts or other software that can interact with the main program to twiddle the knobs and such, and ensure it's doing what was specified). Alternatively, you have to program your hardware and test directly on that. -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 From michael.stemper at gmail.com Wed Oct 25 09:20:11 2023 From: michael.stemper at gmail.com (Michael F. Stemper) Date: Wed, 25 Oct 2023 08:20:11 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On 24/10/2023 17.50, Thomas Passin wrote: > The programming team for the Apollo moon mission developed a system which,> if you would write your requirements in a certain way, could generate correct > C code for them. Since the last Apollo mission was in 1972, when C was first being developed, I find this hard to believe. -- Michael F. Stemper Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. From michael.stemper at gmail.com Wed Oct 25 09:34:13 2023 From: michael.stemper at gmail.com (Michael F. Stemper) Date: Wed, 25 Oct 2023 08:34:13 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On 24/10/2023 18.15, o1bigtenor wrote: > What is interesting about this is the absolute certainty that it is impossible > to program so that that program is provably correct. Not entirely true. If I was to write a program to calculate Fibonacci numbers, or echo back user input, that program could be proven correct. But, there is a huge set of programs for which it is not possible to prove correctness. In fact, there is a huge (countably infinite) set of programs for which it is not even possible to prove that the program will halt. Somebody already pointed you at a page discussing "The Halting Problem". You really should read up on this. > Somehow - - - well - - to me that sounds that programming is illogical. > > If I set up a set of mathematical problems (linked) I can prove that the > logic structure of my answer is correct. Exactly the same situation. There are many (again, countably infinite) mathematical statements where it is not possible to prove that the statement is either true or false. I want to be clear that this is not the same as "we haven't figured out how to do it yet." It is a case of "it is mathematically possible to show that we can't either prove or disprove statement ." Look up Kurt G?del's work on mathematical incompleteness, and some of the statements that fall into this category, such as the Continuum Hypothesis or the Parallel Postulate. As I said at the beginning, there are a lot of programs that can be proven correct or incorrect. But, there are a lot more that cannot. -- Michael F. Stemper Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. From rsutton43 at comcast.net Wed Oct 25 10:19:43 2023 From: rsutton43 at comcast.net (rsutton) Date: Wed, 25 Oct 2023 10:19:43 -0400 Subject: Too Broad of an exception Message-ID: Hi all, I am fairly new to python (ie < 2 years). I have a question about pylint. I am running on windows 10/11, python 3.10.11. Here's what I'm trying to do: I am using robocopy to to copy a set of files to/from a LAN location and my desktop(s). Here is the partial code: p = subprocess.run(["robocopy.exe", STORE_LOCATION, NEWS_LOCATION, "/NFL", "/NDL", "/NJH", "/NJS", "/NP", "/XF", "msgFilterRules.dat", "xmsgFilterRules.dat"], check=False) # this is necessary because Windows Robocopy returns # various return codes for success. if p.returncode >= 8: raise Exception(f'Invalid result: {p.returncode}') It actually runs fine. But pylint is not having it. I get: win_get_put_tb_filters.py:61:12: W0719: Raising too general exception: Exception (broad-exception-raised) But the code I have written does exactly what I want. If the returncode is 7 or less, then I have success. If the returncode is 8 or above there is a failure and I want to see what the returncode is. Trying to read the python Exception docs is mind bending. Any help would be appreciated. Richard From mail at rkta.de Wed Oct 25 10:25:42 2023 From: mail at rkta.de (Rene Kita) Date: Wed, 25 Oct 2023 14:25:42 -0000 (UTC) Subject: Too Broad of an exception References: Message-ID: rsutton wrote: > Hi all, > I am fairly new to python (ie < 2 years). I have a question about > pylint. I am running on windows 10/11, python 3.10.11. [...] > if p.returncode >= 8: > raise Exception(f'Invalid result: {p.returncode}') > > It actually runs fine. But pylint is not having it. I get: > > win_get_put_tb_filters.py:61:12: W0719: Raising too general exception: > Exception (broad-exception-raised) pylint is just a linter, ignore it if the code works and you like it the way it is. pylint complains because you use Exception. Use e.g. RuntimeException to silence it. From torriem at gmail.com Wed Oct 25 11:17:34 2023 From: torriem at gmail.com (Michael Torrie) Date: Wed, 25 Oct 2023 09:17:34 -0600 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> On 10/25/23 05:51, o1bigtenor via Python-list wrote: > Looks like I have another area to investigate. (grin!) > Any suggestions? Seems to me you're trying to run before you have learned to walk. Slow down, go to the beginning and just learn python, write some code, see if it runs. Go through the tutorial at https://docs.python.org/3/tutorial/index.html Your first and most basic tool is the python interpreter. It will tell you when you try to run your code if you have syntax errors. It's true that some errors the linters will catch won't show up as syntax errors, but cross the bridge when you get to it. Once you have a basic grasp of Python syntax, you can begin using some of the tools Python has for organizing code: Functions and modules (eventually packages). Eventually when your logic is placed neatly into functions, you can then write other python programs that import those functions and feed different parameters to them and test that the output is what you expect. That is known as a test. Nothing wrong with geany as an editor. However, you might find the Python Idle IDE useful (it usually installs with Python), as it lets you work more interactively with your code, inspecting and interacting with live python objects in memory. It also integrates debugging functionality to let you step through your code one line at a time and watch variables and how they change. When you encounter isses with your code (syntax or logical) that you can't solve, you can come to the list, show your code and the full output of the interpreter that shows the complete error message and back trace and I think you'll get a lot of helpful responses. From avi.e.gross at gmail.com Wed Oct 25 12:07:47 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Wed, 25 Oct 2023 12:07:47 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <062901da06e1$46a074e0$d3e15ea0$@gmail.com> <064f01da06eb$ab60a5d0$0221f170$@gmail.com> Message-ID: <005b01da075d$65930da0$30b928e0$@gmail.com> I am replying to this which is heading into another topic: "(Tongue in cheek) Except doesn't one make more $$$$ when software in hidden in an unreadable state? (That forces the user to go back to the original dev or group - - yes?)" Like some of us, I come from a time when much software was compiled. Sure, you could play interactively with the BASIC interpreter, but much else could be delivered to you as an executable and it was not easy to know what it did without trying it and certainly it was not easy to make changes to it and resell it as your own. Where does python fit in? On the one hand, it is completely visible as the software and modules you use tend to be stored on the machine being used in a readable state. If you come up with some nifty algorithm, it is there for anyone to see and copy or even alter if they have permissions. You can freely search a corpus of code to pick up interesting tidbits and that can be a plus but if your livelihood is based on selling your code or services, ... So do some people do things to make that harder? Can you deliver only files already converted to bytecode, for example? Could you have an interpreter that has special changes such as being able to take encrypted code and decrypt before using or perhaps have read privileges that normal users will not have? Obviously if your code is on a server that users can only access indirectly and in a controlled manner, this is not as much of an issue. I will skip the anecdotes, but point out how sometimes compiled code may have a whole bunch of other problems, including when a user can sneak in your office and modify the source code behind your back or when a virus can insert itself. So to return to the main point, not that I am selling anything, what do developers using Python do to try to make sure they get properly paid and others do not just use their work without permission? -----Original Message----- From: o1bigtenor Sent: Wednesday, October 25, 2023 6:59 AM To: avi.e.gross at gmail.com Cc: Chris Angelico ; python-list at python.org Subject: Re: Question(s) On Tue, Oct 24, 2023 at 9:36?PM AVI GROSS via Python-list wrote: > > Agreed, Chris. There are many methods way better than the sort of RAID > architecture I supplied as AN EXAMPLE easy to understand. But even so, if a > hard disk or memory chip is fried or a nuclear bomb takes out all servers in > or near a city, you would need some truly crazy architectures with info not > only distributed across the globe but perhaps also to various space > satellites or servers kept ever further out and eventually in hyperspace or > within a black hole (might be write-only, alas). > > The point many of us keep saying is there can not easily or even with great > difficult, any perfect scheme that guarantees nothing will go wrong with the > software, hardware, the people using it and so on. And in the real world, as > compared to the reel world, many programs cannot remain static. Picture a > program that includes many tax laws and implementations that has to be > changed at least yearly as laws change. Some near-perfect code now has to > either be patched with lots of errors possible, or redesigned from scratch > and if it takes long enough, will come out after yet more changes and thus > be wrong. > > A decent question you can ask is if the language this forum is supposed to > be on, is better in some ways to provide the kind of Teflon-coated code he > wants. Are there features better avoided? How do you make sure updates to > modules you use and trust are managed as they may break your code. Stuff > like that is not as abstract. The above are very interesting questions - - - - anyone care to tackle one, or some? > > In my view, one consideration can be that when people can examine your > source code in the original language, that can open up ways others might > find ways to break it, more so than a compiled program that you only can > read in a more opaque way. > (Tongue in cheek) Except doesn't one make more $$$$ when software in hidden in an unreadable state? (That forces the user to go back to the original dev or group - - yes?) TIA From phd at phdru.name Wed Oct 25 12:39:14 2023 From: phd at phdru.name (Oleg Broytman) Date: Wed, 25 Oct 2023 19:39:14 +0300 Subject: SQLObject 3.10.3 Message-ID: Hello! I'm pleased to announce version 3.10.3, the 3rd bugfix release of branch 3.10 of SQLObject. What's new in SQLObject ======================= The contributors for this release are Igor Yudytskiy and shuffle (github.com/shuffleyxf). Thanks! Bug fixes --------- * Relaxed aliasing in ``SQLRelatedJoin`` introduced in 3.10.2 - aliasing is required only when the table joins with itself. When there're two tables to join aliasing prevents filtering -- wrong SQL is generated in ``relJoinCol.filter(thisClass.q.column)``. Drivers ------- * Fix(SQLiteConnection): Release connections from threads that are no longer active. This fixes memory leak in multithreaded programs in Windows. ``SQLite`` requires different connections per thread so ``SQLiteConnection`` creates and stores a connection per thread. When a thread finishes its connections should be closed. But if a program doesn't cooperate and doesn't close connections at the end of a thread SQLObject leaks memory as connection objects are stuck in ``SQLiteConnection``. On Linux the leak is negligible as Linux reuses thread IDs so new connections replace old ones and old connections are garbage collected. But Windows doesn't reuse thread IDs so old connections pile and never released. To fix the problem ``SQLiteConnection`` now enumerates threads and releases connections from non-existing threads. * Dropped ``supersqlite``. It seems abandoned. The last version 0.0.78 was released in 2018. Tests ----- * Run tests with Python 3.12. CI -- * GHActions: Ensure ``pip`` only if needed This is to work around a problem in conda with Python 3.7 - it brings in wrong version of ``setuptools`` incompatible with Python 3.7. For a more complete list, please see the news: http://sqlobject.org/News.html What is SQLObject ================= SQLObject is a free and open-source (LGPL) Python object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL/MariaDB (with a number of DB API drivers: ``MySQLdb``, ``mysqlclient``, ``mysql-connector``, ``PyMySQL``, ``mariadb``), PostgreSQL (``psycopg2``, ``PyGreSQL``, partially ``pg8000`` and ``py-postgresql``), SQLite (builtin ``sqlite``, ``pysqlite``); connections to other backends - Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB) - are less debugged). Python 2.7 or 3.4+ is required. Where is SQLObject ================== Site: http://sqlobject.org Download: https://pypi.org/project/SQLObject/3.10.3 News and changes: http://sqlobject.org/News.html StackOverflow: https://stackoverflow.com/questions/tagged/sqlobject Mailing lists: https://sourceforge.net/p/sqlobject/mailman/ Development: http://sqlobject.org/devel/ Developer Guide: http://sqlobject.org/DeveloperGuide.html Example ======= Install:: $ pip install sqlobject Create a simple class that wraps a table:: >>> from sqlobject import * >>> >>> sqlhub.processConnection = connectionForURI('sqlite:/:memory:') >>> >>> class Person(SQLObject): ... fname = StringCol() ... mi = StringCol(length=1, default=None) ... lname = StringCol() ... >>> Person.createTable() Use the object:: >>> p = Person(fname="John", lname="Doe") >>> p >>> p.fname 'John' >>> p.mi = 'Q' >>> p2 = Person.get(1) >>> p2 >>> p is p2 True Queries:: >>> p3 = Person.selectBy(lname="Doe")[0] >>> p3 >>> pc = Person.select(Person.q.lname=="Doe").count() >>> pc 1 Oleg. -- Oleg Broytman https://phdru.name/ phd at phdru.name Programmers don't die, they just GOSUB without RETURN. From michael.stemper at gmail.com Wed Oct 25 11:07:26 2023 From: michael.stemper at gmail.com (Michael F. Stemper) Date: Wed, 25 Oct 2023 10:07:26 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On 25/10/2023 05.45, o1bigtenor wrote: > On Tue, Oct 24, 2023 at 8:35?PM Chris Angelico via Python-list > wrote: >> 3. Catch the failure before you commit and push. Unit tests are great for this. > > Where might I find such please. You don't "find" unit tests; you write them. A unit test tests a specific function or program. Ideally, you write each unit test *before* you write the function that it tests. For instance, suppose that you were writing a function to calculate the distance between two points. We know the following things about distance: 1. The distance from a point to itself is zero. 2. The distance between two distinct points is positive. 3. The distance from A to B is equal to the distance from B to A. 4. The distance from A to B plus the distance from B to C is at least as large as the distance from A to C. You would write unit tests that generate random points and apply your distance function to them, checking that each of these conditions is satisfied. You'd also write a few tests of hard-coded points,such as: - Distance from (0,0) to (0,y) is y - Distance from (0,0) to (x,0) is x - Distance from (0,0) to (3,4) is 5 - Distance from (0,0) to (12,5) is 13 The python ecosystem provides many tools to simplify writing and running unit tests. Somebody has already mentioned "unittest". I use this one all of the time. There are also "doctest", "nose", "tox", and "py.test" (none of which I've used). -- Michael F. Stemper Life's too important to take seriously. From rsutton43 at comcast.net Wed Oct 25 11:49:12 2023 From: rsutton43 at comcast.net (rsutton) Date: Wed, 25 Oct 2023 11:49:12 -0400 Subject: Too Broad of an exception In-Reply-To: References: Message-ID: On 10/25/2023 11:06 AM, Stefan Ram wrote: > ram at zedat.fu-berlin.de (Stefan Ram) writes: >> outer quotation marks) prints some prominent exception types. After >> manually removing those that do not seem to apply, I am left with: >> "AssertionError", >> "ChildProcessError", > ... > > "Manually removing" above was meant to be a fast first pass, > where I only excluded exception types that were obviously > inappropriate. It is now to be followed by a search for the > appropriate exception types among those exception types left. > > @Rene & @Stefan, I really appreciate the guidance provided. By replacing Exception with RuntimeError, pylint seems happy! More specificity, I guess. I know that I could have ignored the pylint exceptions, but I want to use this as a learning experience. I looks like I have a lot of reading to do on exception handling. IMO all of the try/except code looks quite clumsy to me. It may be excellent for some tasks but to me, it looks quite inelegant. Like I said, I have a lot to learn. Thank you both for your guidance. Richard From learn2program at gmail.com Wed Oct 25 13:03:01 2023 From: learn2program at gmail.com (Alan Gauld) Date: Wed, 25 Oct 2023 18:03:01 +0100 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> Message-ID: <69bdf502-22af-881d-aef2-4891fe86c37a@yahoo.co.uk> On 25/10/2023 12:44, o1bigtenor via Python-list wrote: > Haven't heard of a python IDE - - - doesn't mean that there isn't such - - There are literally dozens with varying degrees of smartness. The big 4 all have Python plugins/environments: Eclipse, Netbeans, VisualStudio, IntelliJ And of course the Apple XCode toolset has a python environment. There are also several Python specific IDEs around too. Most of them are multi-platform: https://www.simplilearn.com/tutorials/python-tutorial/python-ide gives a small sample And of course the old favourites vi/vim and emacs both have comprehensive Python support. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos From list1 at tompassin.net Wed Oct 25 09:21:16 2023 From: list1 at tompassin.net (Thomas Passin) Date: Wed, 25 Oct 2023 09:21:16 -0400 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> Message-ID: On 10/25/2023 8:50 AM, o1bigtenor via Python-list wrote: > On Wed, Oct 25, 2023 at 7:00?AM Dieter Maurer wrote: >> >> o1bigtenor wrote at 2023-10-25 06:44 -0500: >>> On Wed, Oct 25, 2023 at 6:24?AM Dieter Maurer wrote: >>> ... >>>> There are different kinds of errors. >>>> >>>> Some can be avoided by using an integrated development environment >>>> (e.g. misspellings, type mismatches, ...). >>> >>> Haven't heard of a python IDE - - - doesn't mean that there isn't such - - >>> just that I haven't heard of such. Is there a python IDE? >> >> There are several. >> >> Python comes with "IDLE". >> > Interesting - - - started looking into this. > >> There are several others, >> e.g. "ECLIPSE" can be used for Python development. > > Is 'Eclipse' a Windows oriented IDE? > (Having a hard time finding linux related information on the > website.) > >> Search for other alternatices. > > Will do. > > Thanks for the assistance. Pyzo is one possibility - https://pyzo.org From kushal at locationd.net Wed Oct 25 13:41:09 2023 From: kushal at locationd.net (Kushal Kumaran) Date: Wed, 25 Oct 2023 10:41:09 -0700 Subject: Too Broad of an exception In-Reply-To: (rsutton's message of "Wed, 25 Oct 2023 11:49:12 -0400") References: Message-ID: <87y1fqwqfe.fsf@copper> On Wed, Oct 25 2023 at 11:49:12 AM, rsutton wrote: > On 10/25/2023 11:06 AM, Stefan Ram wrote: >> ram at zedat.fu-berlin.de (Stefan Ram) writes: >>> outer quotation marks) prints some prominent exception types. After >>> manually removing those that do not seem to apply, I am left with: >>> "AssertionError", >>> "ChildProcessError", >> ... >> "Manually removing" above was meant to be a fast first pass, >> where I only excluded exception types that were obviously >> inappropriate. It is now to be followed by a search for the >> appropriate exception types among those exception types left. >> > @Rene & @Stefan, > I really appreciate the guidance provided. By replacing Exception > with RuntimeError, pylint seems happy! More specificity, I guess. I > know that I could have ignored the pylint exceptions, but I want to > use this as a learning experience. I looks like I have a lot of > reading to do on exception handling. IMO all of the try/except code > looks quite clumsy to me. It may be excellent for some tasks but to > me, it looks quite inelegant. Like I said, I have a lot to learn. > >From what you've described of your problem, it seems like a small-ish utility program you're writing for your own use. You don't need any `try`...`except` blocks in such code. You just let the exception stop your program. -- regards, kushal From list1 at tompassin.net Wed Oct 25 12:26:31 2023 From: list1 at tompassin.net (Thomas Passin) Date: Wed, 25 Oct 2023 12:26:31 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: <1df731e5-ded7-4f80-a3ef-8916af73736d@tompassin.net> On 10/25/2023 9:20 AM, Michael F. Stemper via Python-list wrote: > On 24/10/2023 17.50, Thomas Passin wrote: > > >> ?? The programming team for the Apollo moon mission developed a system >> which,> if you would write your requirements in a certain way, could >> generate correct >> C code for them. > Since the last Apollo mission was in 1972, when C was first being > developed, I > find this hard to believe. Yes, sorry, see my previous post. It's the current-day evolution of the tools that can output C. From list1 at tompassin.net Wed Oct 25 13:50:39 2023 From: list1 at tompassin.net (Thomas Passin) Date: Wed, 25 Oct 2023 13:50:39 -0400 Subject: Too Broad of an exception In-Reply-To: References: Message-ID: <62012c67-6af3-41e3-9b5b-5ede6ff90f72@tompassin.net> On 10/25/2023 11:49 AM, rsutton via Python-list wrote: > On 10/25/2023 11:06 AM, Stefan Ram wrote: >> ram at zedat.fu-berlin.de (Stefan Ram) writes: >>> outer quotation marks) prints some prominent exception types. After >>> manually removing those that do not seem to apply, I am left with: >>> "AssertionError", >>> "ChildProcessError", >> ... >> >> ?? "Manually removing" above was meant to be a fast first pass, >> ?? where I only excluded exception types that were obviously >> ?? inappropriate. It is now to be followed by a search for the >> ?? appropriate exception types among those exception types left. >> >> > @Rene & @Stefan, > I really appreciate the guidance provided.? By replacing Exception with > RuntimeError, pylint seems happy!? More specificity, I guess.? I know > that I could have ignored the pylint exceptions, but I want to use this > as a learning experience.? I looks like I have a lot of reading to do on > exception handling. IMO all of the try/except code looks quite clumsy to > me.? It may be excellent for some tasks but to me, it looks quite > inelegant.? Like I said, I have a lot to learn. In this particular case you could probably just handle the return result from robocopy right there. Of course, it depends on the rest of the code. It probably doesn't really need an exception, and if you want to handle it in the calling function, you could just return the result as a boolean: return p.returncode < 8 # Reversed the test since a return of "True" # would make more sense as a return code > Thank you both for your guidance. > > Richard > From dan at djph.net Wed Oct 25 15:43:36 2023 From: dan at djph.net (Dan Purgert) Date: Wed, 25 Oct 2023 19:43:36 -0000 (UTC) Subject: Question(s) References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> Message-ID: On 2023-10-25, o1bigtenor wrote: > On Wed, Oct 25, 2023 at 7:00?AM Dieter Maurer wrote: >> [...] >> There are several others, >> e.g. "ECLIPSE" can be used for Python development. > > Is 'Eclipse' a Windows oriented IDE? > (Having a hard time finding linux related information on the > website.) Not at all. As I recall, it's entirely written in Java, so basically entirely platform-independent already. -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 From jschwar at sbcglobal.net Wed Oct 25 16:56:16 2023 From: jschwar at sbcglobal.net (Jim Schwartz) Date: Wed, 25 Oct 2023 15:56:16 -0500 Subject: Question(s) In-Reply-To: References: Message-ID: Does this link help? It seems to have a Linux package here. [1]Eclipse Packages | The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and [2]favicon.ico over 350 open source projects... eclipse.org Sent from my iPhone On Oct 25, 2023, at 7:55 AM, o1bigtenor via Python-list wrote: On Wed, Oct 25, 2023 at 7:00AM Dieter Maurer wrote: o1bigtenor wrote at 2023-10-25 06:44 -0500: On Wed, Oct 25, 2023 at 6:24?AM Dieter Maurer wrote: ... There are different kinds of errors. Some can be avoided by using an integrated development environment (e.g. misspellings, type mismatches, ...). Haven't heard of a python IDE - - - doesn't mean that there isn't such - - just that I haven't heard of such. Is there a python IDE? There are several. Python comes with "IDLE". Interesting - - - started looking into this. There are several others, e.g. "ECLIPSE" can be used for Python development. Is 'Eclipse' a Windows oriented IDE? (Having a hard time finding linux related information on the website.) Search for other alternatices. Will do. Thanks for the assistance. -- https://mail.python.org/mailman/listinfo/python-list References Visible links 1. https://www.eclipse.org/downloads/packages/ 2. https://www.eclipse.org/downloads/packages/ From avi.e.gross at gmail.com Wed Oct 25 21:25:58 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Wed, 25 Oct 2023 21:25:58 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: <002101da07ab$5fc5c6d0$1f515470$@gmail.com> Just want to add that even when you can prove that an algorithm works absolutely positively, it will often fail on our every finite computers. Consider families of algorithms that do hill climbing to find a minimum and maximum and are guaranteed to get ever closer to a solution given infinite time. In real life, using something like 64 bit or 128 bit floating point representations, you can end up with all kinds of rounding errors and inexactness on some inputs so it goes into a loop of constantly bouncing back and forth between the two sides and never gets any closer to the peak. It may work 99.99% of the time and then mysteriously lock up on some new data. Or consider an algorithm some use in places like Vegas that is absolutely 100% guaranteed to win. If you bet $1 and lose, simply double your bet as many times as needed and eventually, you should win. Of course, one little problem is that all you ever win is $1. And you might lose 50 times in a row and spend hours and risk ever larger amounts to just win that dollar. Sure, you could just start betting a larger amount like a million dollars and eventually win a million dollars but how long can anyone keep doubling before they have to stop and lose it all. After enough doublings the vet is for billions of dollars and soon thereafter, more than the worth of everything on the planet. The algorithm is mathematically sound but the result given other realities is not. A last analogy is the division by zero issue. If your algorithm deals with infinitesimally smaller numbers, it may simply be rounded or truncated to exactly zero. The next time the algorithm does a division, you get a serious error. So perhaps a PROOF that a real computer program will work would require quite a few constraints. Python already by default supports integers limited only in size by available memory. This can avoid some of the overflow problems when all you are allowed is 64 bits but it remains a constraint and a danger as even a fairly simple algorithm you can PROVE will work, will still fail if your program uses these large integers in ways that make multiple such large integers on machines not designed to extend their memory into whole farms of machines or generates numbers like Googolplex factorial divided by googolplex raised to the log(Googolplex ) power. Some problems like the above are manageable as in setting limits and simply returning failure without crashing. Many well-designed programs can be trusted to work well as long as certain assumptions are honored. But often it simply is not true and things can change. Python actually is a good choice for quite a bit and often will not fail where some other environment might but there are few guarantees and thus people often program defensively even in places they expect no problems. As an example, I have written programs that ran for DAYS and generated many millions of files as they chugged along in a simulation and then mysteriously died. I did not bother trying to find out why one program it called failed that rarely to produce a result. I simply wrapped the section that called the occasional offender in the equivalent try/catch for that language and when it happened, did something appropriate and continued. The few occasional errors were a bug in someone else's code that should have handled whatever weird data I threw at it gracefully but didn't, so I added my overhead so I could catch it. The rare event did not matter much given the millions that gave me the analysis I wanted. But the point is even if my code had been certified as guaranteed to be bug free, any time I stepped outside by calling code from anyone else in a library, or an external program, it is no longer guaranteed. We are now spending quite a bit of time educating someone who seems to have taken on a task without really being generally knowledgeable about much outside the core language and how much of the answer to making the code as reliable as it can be may lie somewhat outside the program as just seen by the interpreter. And unless this is a one-shot deal, in the real world, programs keep getting modified and new features ofteh added and just fixing one bug can break other parts so you would need to verify things over and over and then freeze. -----Original Message----- From: Python-list On Behalf Of Michael F. Stemper via Python-list Sent: Wednesday, October 25, 2023 9:34 AM To: python-list at python.org Subject: Re: Question(s) On 24/10/2023 18.15, o1bigtenor wrote: > What is interesting about this is the absolute certainty that it is impossible > to program so that that program is provably correct. Not entirely true. If I was to write a program to calculate Fibonacci numbers, or echo back user input, that program could be proven correct. But, there is a huge set of programs for which it is not possible to prove correctness. In fact, there is a huge (countably infinite) set of programs for which it is not even possible to prove that the program will halt. Somebody already pointed you at a page discussing "The Halting Problem". You really should read up on this. > Somehow - - - well - - to me that sounds that programming is illogical. > > If I set up a set of mathematical problems (linked) I can prove that the > logic structure of my answer is correct. Exactly the same situation. There are many (again, countably infinite) mathematical statements where it is not possible to prove that the statement is either true or false. I want to be clear that this is not the same as "we haven't figured out how to do it yet." It is a case of "it is mathematically possible to show that we can't either prove or disprove statement ." Look up Kurt G?del's work on mathematical incompleteness, and some of the statements that fall into this category, such as the Continuum Hypothesis or the Parallel Postulate. As I said at the beginning, there are a lot of programs that can be proven correct or incorrect. But, there are a lot more that cannot. -- Michael F. Stemper Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. -- https://mail.python.org/mailman/listinfo/python-list From PythonList at DancesWithMice.info Wed Oct 25 21:32:18 2023 From: PythonList at DancesWithMice.info (dn) Date: Thu, 26 Oct 2023 14:32:18 +1300 Subject: Too Broad of an exception In-Reply-To: References: Message-ID: <74cda9f7-2fcf-48f1-b227-bac8c558dcef@DancesWithMice.info> On 26/10/2023 04.49, rsutton via Python-list wrote: > On 10/25/2023 11:06 AM, Stefan Ram wrote: >> ram at zedat.fu-berlin.de (Stefan Ram) writes: >>> outer quotation marks) prints some prominent exception types. After ... >> ?? "Manually removing" above was meant to be a fast first pass, >> ?? where I only excluded exception types that were obviously >> ?? inappropriate. It is now to be followed by a search for the >> ?? appropriate exception types among those exception types left. >> >> > @Rene & @Stefan, > I really appreciate the guidance provided.? By replacing Exception with ... It would appear that (at least one message) did not make it to email - neither to the list-archive. People wishing to learn are unable to benefit a response, if it is not sent to the list! -- Regards, =dn From o1bigtenor at gmail.com Thu Oct 26 07:50:27 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Thu, 26 Oct 2023 06:50:27 -0500 Subject: Question(s) In-Reply-To: <25913.8656.388538.474870@ixdm.fritz.box> References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> <25913.4246.644009.815137@ixdm.fritz.box> <25913.8656.388538.474870@ixdm.fritz.box> Message-ID: On Wed, Oct 25, 2023 at 9:10?AM Dieter Maurer wrote: > > o1bigtenor wrote at 2023-10-25 08:29 -0500: > > ... > >It would appear that something has changed. > > > >Went to the Eclipse download page, downloaded and verified (using sha-512). > >Expanded software to # opt . > >There is absolutely NO mention of anything python - - - java, c and > >its permutations, > >'scientific computing', and some others but nothing python. > > > >I may be missing something due to an extreme lack of knowledge. > > > >Please advise as to where I might find the 'python' environment in eclipse. > > I entered "eclipse python download" in my favorite search engine > (=> "ecosia.org") and the second hit gave: > "https://marketplace.eclipse.org/content/pydev-python-ide-eclipse". Using Duckduckgo I had tried eclipse + python which I would have thought should have spit out something useful - - - but that just took me to the general page and the download - - - well it did NOT offer any python anything! Thank you for the tip! From o1bigtenor at gmail.com Thu Oct 26 08:34:25 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Thu, 26 Oct 2023 07:34:25 -0500 Subject: Question(s) In-Reply-To: <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> Message-ID: On Wed, Oct 25, 2023 at 10:19?AM Michael Torrie via Python-list wrote: > > On 10/25/23 05:51, o1bigtenor via Python-list wrote: > > Looks like I have another area to investigate. (grin!) > > Any suggestions? > > Seems to me you're trying to run before you have learned to walk. > > Slow down, go to the beginning and just learn python, write some code, > see if it runs. Go through the tutorial at > https://docs.python.org/3/tutorial/index.html Interesting - - - - ". . . see if it runs." - - - that's the issue! When the code is accessing sensors there isn't an easy way to check that the code is working until one has done the all of the physical construction. If I'm trying to control a pulsation system using square waves with distinct needs for timing etc I hadn't seen any way of 'stepping through the code' (phrase you use later). > > Your first and most basic tool is the python interpreter. It will tell > you when you try to run your code if you have syntax errors. It's true > that some errors the linters will catch won't show up as syntax errors, > but cross the bridge when you get to it. Once you have a basic grasp of > Python syntax, you can begin using some of the tools Python has for > organizing code: Functions and modules (eventually packages). > Eventually when your logic is placed neatly into functions, you can then > write other python programs that import those functions and feed > different parameters to them and test that the output is what you > expect. That is known as a test. > > Nothing wrong with geany as an editor. However, you might find the > Python Idle IDE useful (it usually installs with Python), as it lets you > work more interactively with your code, inspecting and interacting with > live python objects in memory. It also integrates debugging > functionality to let you step through your code one line at a time and > watch variables and how they change. I have been following this list for some time. Don't believe that I've ever seen anything where anyone was referred to 'Idle'. In reading other user group threads I have heard lots about java and its ide - - - don't remember, again, any re: an ide for python. Even in maker threads - - - say for arduino - - its 'use this cut and paste method of programming' with no mention of any kind of ide when it was microPython - - although being a subset of python it Idle may not work with it. > > When you encounter isses with your code (syntax or logical) that you > can't solve, you can come to the list, show your code and the full > output of the interpreter that shows the complete error message and back > trace and I think you'll get a lot of helpful responses. > -- That was the plan. My problem is that I'm needing to move quite quickly from 'hello, world' to something quite a bit more complex. Most of the instruction stuff I've run into assumes that one is programming only for the joy of learning to program where I've got things I want to do and - - - sadly - - - they're not sorta like the run of the mill stuff. Oh well - - - I am working on things! Thanks for the ideas and the assistance! Regards From o1bigtenor at gmail.com Thu Oct 26 08:46:54 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Thu, 26 Oct 2023 07:46:54 -0500 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On Wed, Oct 25, 2023 at 11:58?AM Michael F. Stemper via Python-list wrote: > > On 25/10/2023 05.45, o1bigtenor wrote: > > On Tue, Oct 24, 2023 at 8:35?PM Chris Angelico via Python-list > > wrote: > > >> 3. Catch the failure before you commit and push. Unit tests are great for this. > > > > Where might I find such please. > > You don't "find" unit tests; you write them. A unit test tests > a specific function or program. > > Ideally, you write each unit test *before* you write the function > that it tests. > > For instance, suppose that you were writing a function to calculate > the distance between two points. We know the following things about > distance: > 1. The distance from a point to itself is zero. > 2. The distance between two distinct points is positive. > 3. The distance from A to B is equal to the distance from B to A. > 4. The distance from A to B plus the distance from B to C is at > least as large as the distance from A to C. > > You would write unit tests that generate random points and apply > your distance function to them, checking that each of these > conditions is satisfied. You'd also write a few tests of hard-coded > points,such as: > - Distance from (0,0) to (0,y) is y > - Distance from (0,0) to (x,0) is x > - Distance from (0,0) to (3,4) is 5 > - Distance from (0,0) to (12,5) is 13 > > The python ecosystem provides many tools to simplify writing and > running unit tests. Somebody has already mentioned "unittest". I > use this one all of the time. There are also "doctest", "nose", > "tox", and "py.test" (none of which I've used). > Very useful information - - - thanks! From o1bigtenor at gmail.com Thu Oct 26 08:54:29 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Thu, 26 Oct 2023 07:54:29 -0500 Subject: Question(s) In-Reply-To: References: Message-ID: On Wed, Oct 25, 2023 at 3:56?PM Jim Schwartz wrote: > Does this link help? It seems to have a Linux package here. > > Eclipse Packages | The Eclipse Foundation - home to a global community, > the Eclipse IDE, Jakarta EE and over 350 open source projects... > > eclipse.org > [image: favicon.ico] > > > I was looking at this page and absoulutely couldn't find anything python related. A previous poster (between my ask and this) pointed out a better location. Thanks for the assistance. From list1 at tompassin.net Thu Oct 26 09:57:02 2023 From: list1 at tompassin.net (Thomas Passin) Date: Thu, 26 Oct 2023 09:57:02 -0400 Subject: Question(s) In-Reply-To: References: <25912.64263.558046.607705@ixdm.fritz.box> <25913.837.809451.477876@ixdm.fritz.box> <25913.4246.644009.815137@ixdm.fritz.box> <25913.8656.388538.474870@ixdm.fritz.box> Message-ID: <4448513a-53a9-4ea5-8791-31917e13498a@tompassin.net> On 10/26/2023 7:50 AM, o1bigtenor via Python-list wrote: > On Wed, Oct 25, 2023 at 9:10?AM Dieter Maurer wrote: >> >> o1bigtenor wrote at 2023-10-25 08:29 -0500: >>> ... >>> It would appear that something has changed. >>> >>> Went to the Eclipse download page, downloaded and verified (using sha-512). >>> Expanded software to # opt . >>> There is absolutely NO mention of anything python - - - java, c and >>> its permutations, >>> 'scientific computing', and some others but nothing python. >>> >>> I may be missing something due to an extreme lack of knowledge. >>> >>> Please advise as to where I might find the 'python' environment in eclipse. >> >> I entered "eclipse python download" in my favorite search engine >> (=> "ecosia.org") and the second hit gave: >> "https://marketplace.eclipse.org/content/pydev-python-ide-eclipse". > > Using Duckduckgo I had tried eclipse + python which I would have > thought should have spit out something useful - - - but that just took > me to the general page and the download - - - well it did NOT offer > any python anything! > > Thank you for the tip! Eclipse is a huge complicated ecosystem. I'd stay away from it and go with something smaller and simpler. (having said that, it's quite a few years since I gave up on Eclipse the last time). Something like pyzo, for instance. From mail at rkta.de Thu Oct 26 05:04:27 2023 From: mail at rkta.de (Rene Kita) Date: Thu, 26 Oct 2023 09:04:27 -0000 (UTC) Subject: Too Broad of an exception References: Message-ID: Rene Kita wrote: > rsutton wrote: >> Hi all, >> I am fairly new to python (ie < 2 years). I have a question about >> pylint. I am running on windows 10/11, python 3.10.11. > [...] >> if p.returncode >= 8: >> raise Exception(f'Invalid result: {p.returncode}') >> >> It actually runs fine. But pylint is not having it. I get: >> >> win_get_put_tb_filters.py:61:12: W0719: Raising too general exception: >> Exception (broad-exception-raised) > > pylint is just a linter, ignore it if the code works and you like it the > way it is. > > pylint complains because you use Exception. Use e.g. RuntimeException to > silence it. ^^^^^^^^^^^^^^^^ Ingrid says it's a RuntimeError, not RuntimeException. From torriem at gmail.com Thu Oct 26 12:41:33 2023 From: torriem at gmail.com (Michael Torrie) Date: Thu, 26 Oct 2023 10:41:33 -0600 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> Message-ID: <247d0267-f300-67f3-649f-5c932475e89e@gmail.com> On 10/26/23 06:34, o1bigtenor wrote: > Interesting - - - - ". . . see if it runs." - - - that's the issue! > When the code is accessing sensors there isn't an easy way to > check that the code is working until one has done the all of the > physical construction. If I'm trying to control a pulsation system > using square waves with distinct needs for timing etc I hadn't > seen any way of 'stepping through the code' (phrase you use later). Having dabbled in embedded electronics, all I can say is you will just have to build it and try to get it working. Failure is always an option. If I understand you correctly, this is for a hobby interest, so go at it and have fun. Stepping through code is a basic part of debugging in any language. They all have tools for it. Google for python debugging. "distinct needs for timing?" Did you forget to tell us you need to use MicroPython? Certainly MicroPython running on a microcontroller with help from hardware timers certainly can do it, but this mailing list is not the place to ask about it. Instead you'll have to visit a forum on MicroPython or CircuitPython. By the way you definitely can step through MicroPython code one line at a time with a remote debugger, say with Visual Studio Code. > I have been following this list for some time. Don't believe that I've ever > seen anything where anyone was referred to 'Idle'. In reading other user > group threads I have heard lots about java and its ide - - - don't remember, > again, any re: an ide for python. Idle has been mentioned on several occasions, but probably more on the python-tutor list. I find it hard to believe that searching for Python IDEs really came up blank. There are even IDEs for MicroPython and embedded devices. I found a nice list with a quick search. > Even in maker threads - - - say for arduino - - its 'use this cut and > paste method > of programming' with no mention of any kind of ide when it was microPython - - > although being a subset of python it Idle may not work with it. You keep dropping little details that, had you included them in the first post, would have helped avoid a lot of answers that ultimately aren't going to be useful to you. Are you working MicroPython or with regular Python on a PC? That makes a big difference in where you go to get help and what kind of help we can provide here. > Oh well - - - I am working on things! That is good. I wish you success. From torriem at gmail.com Thu Oct 26 12:45:01 2023 From: torriem at gmail.com (Michael Torrie) Date: Thu, 26 Oct 2023 10:45:01 -0600 Subject: Question(s) In-Reply-To: <247d0267-f300-67f3-649f-5c932475e89e@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> <247d0267-f300-67f3-649f-5c932475e89e@gmail.com> Message-ID: <8188173b-0973-45b2-82d2-97e22f264579@gmail.com> On 10/26/23 10:41, Michael Torrie wrote: > By the way you definitely can step > through MicroPython code one line at a time with a remote debugger, say > with Visual Studio Code. I meant to edit that bit out. After doing a bit more research, it appears remote debugging with MicroPython may not be possible or easy. But the MicroPython lists and forums will know more about that than I do. But there are some nice IDEs for developing code in MicroPython and deploying it to devices. From mats at wichmann.us Thu Oct 26 13:10:20 2023 From: mats at wichmann.us (Mats Wichmann) Date: Thu, 26 Oct 2023 11:10:20 -0600 Subject: Too Broad of an exception In-Reply-To: References: Message-ID: <1b484d6f-cdda-4fbf-9be1-fbedd0f82c48@wichmann.us> On 10/26/23 03:04, Rene Kita via Python-list wrote: > Rene Kita wrote: >> rsutton wrote: >>> Hi all, >>> I am fairly new to python (ie < 2 years). I have a question about >>> pylint. I am running on windows 10/11, python 3.10.11. >> [...] >>> if p.returncode >= 8: >>> raise Exception(f'Invalid result: {p.returncode}') >>> >>> It actually runs fine. But pylint is not having it. I get: >>> >>> win_get_put_tb_filters.py:61:12: W0719: Raising too general exception: >>> Exception (broad-exception-raised) >> >> pylint is just a linter, ignore it if the code works and you like it the >> way it is. >> >> pylint complains because you use Exception. Use e.g. RuntimeException to >> silence it. > ^^^^^^^^^^^^^^^^ > > Ingrid says it's a RuntimeError, not RuntimeException. Meanwhile, the purpose of this complaint from pylint (and notice it's a "warning", not an "error", so take that for what it's worth), is that you usually want to convey some information when you raise an exception. Of course, you can put that into the message you pass to the class instance you raise, but the type of exception is informational too. Raising just "Exception" is equivalent to saying "my car is broken", without specifying that the starter turns but won't "catch", or starts but the transmission won't engage, or the battery is dead, or .... so it's *advising* (not forcing) you to be more informative. From o1bigtenor at gmail.com Thu Oct 26 16:25:38 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Thu, 26 Oct 2023 15:25:38 -0500 Subject: Question(s) In-Reply-To: <247d0267-f300-67f3-649f-5c932475e89e@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> <247d0267-f300-67f3-649f-5c932475e89e@gmail.com> Message-ID: On Thu, Oct 26, 2023 at 11:43?AM Michael Torrie via Python-list wrote: > > On 10/26/23 06:34, o1bigtenor wrote: > > Interesting - - - - ". . . see if it runs." - - - that's the issue! > > When the code is accessing sensors there isn't an easy way to > > check that the code is working until one has done the all of the > > physical construction. If I'm trying to control a pulsation system > > using square waves with distinct needs for timing etc I hadn't > > seen any way of 'stepping through the code' (phrase you use later). > > Having dabbled in embedded electronics, all I can say is you will just > have to build it and try to get it working. Failure is always an > option. If I understand you correctly, this is for a hobby interest, so > go at it and have fun. > > Stepping through code is a basic part of debugging in any language. > They all have tools for it. Google for python debugging. > > "distinct needs for timing?" Did you forget to tell us you need to use > MicroPython? Certainly MicroPython running on a microcontroller with > help from hardware timers certainly can do it, but this mailing list is > not the place to ask about it. Instead you'll have to visit a forum on > MicroPython or CircuitPython. By the way you definitely can step > through MicroPython code one line at a time with a remote debugger, say > with Visual Studio Code. Its one of the reasons to use micropython - - - it is a subset of python. I didn't think I was asking about micropython here though. The project with the square wave stuff has lots going on so its more likely that regular python will be used. Part of the challenge is trying to figure out if I need to be running a real time kernel or even a real time OS. Independent information is quite hard to find - - - seems like most of the information is by someone with skin in the game and then without a background its hard to figure out if what they're saying tells enough so that I can make a good decision or not. > > > I have been following this list for some time. Don't believe that I've ever > > seen anything where anyone was referred to 'Idle'. In reading other user > > group threads I have heard lots about java and its ide - - - don't remember, > > again, any re: an ide for python. > > Idle has been mentioned on several occasions, but probably more on the > python-tutor list. I find it hard to believe that searching for Python > IDEs really came up blank. There are even IDEs for MicroPython and > embedded devices. I found a nice list with a quick search. I didn't say that I had done any searching for a python ide. I have only spent time looking for information on coding. There's lots on make a led blink and other simple stuff but when you want to get at least a couple orders more complicated - - - there is precious little and that's what I've been looking for (and finding any stuff very hard to find!). > > > Even in maker threads - - - say for arduino - - its 'use this cut and > > paste method > > of programming' with no mention of any kind of ide when it was microPython - - > > although being a subset of python it Idle may not work with it. > > You keep dropping little details that, had you included them in the > first post, would have helped avoid a lot of answers that ultimately > aren't going to be useful to you. Are you working MicroPython or with > regular Python on a PC? That makes a big difference in where you go to > get help and what kind of help we can provide here. > I didn't even really know how to ask the question(s). Likely I could have asked better but until I got some of the answers did it make sense for me to add further. I did not want an answer for one 'problem'. I was more looking for a way of doing things (which is quite different). > > Oh well - - - I am working on things! > > That is good. I wish you success. > Thank you. I'll likely be back with more questions (grin!). (Lost a great mentor some almost 4 years ago now so its a lot more flail around than if my buddy were still available.) Thanking you for your ideas and tips! From o1bigtenor at gmail.com Thu Oct 26 16:26:43 2023 From: o1bigtenor at gmail.com (o1bigtenor) Date: Thu, 26 Oct 2023 15:26:43 -0500 Subject: Question(s) In-Reply-To: <8188173b-0973-45b2-82d2-97e22f264579@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> <247d0267-f300-67f3-649f-5c932475e89e@gmail.com> <8188173b-0973-45b2-82d2-97e22f264579@gmail.com> Message-ID: On Thu, Oct 26, 2023 at 11:47?AM Michael Torrie via Python-list wrote: > > On 10/26/23 10:41, Michael Torrie wrote: > > By the way you definitely can step > > through MicroPython code one line at a time with a remote debugger, say > > with Visual Studio Code. > > I meant to edit that bit out. After doing a bit more research, it > appears remote debugging with MicroPython may not be possible or easy. > But the MicroPython lists and forums will know more about that than I > do. But there are some nice IDEs for developing code in MicroPython and > deploying it to devices. > -- Even here - - - I now have a first step and a direction! Thanks From list1 at tompassin.net Thu Oct 26 17:39:27 2023 From: list1 at tompassin.net (Thomas Passin) Date: Thu, 26 Oct 2023 17:39:27 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> <247d0267-f300-67f3-649f-5c932475e89e@gmail.com> Message-ID: <53f341ff-efb3-4867-9cc3-f87c0999b7b6@tompassin.net> On 10/26/2023 4:25 PM, o1bigtenor via Python-list wrote: > On Thu, Oct 26, 2023 at 11:43?AM Michael Torrie via Python-list > wrote: >> >> On 10/26/23 06:34, o1bigtenor wrote: >>> Interesting - - - - ". . . see if it runs." - - - that's the issue! >>> When the code is accessing sensors there isn't an easy way to >>> check that the code is working until one has done the all of the >>> physical construction. If I'm trying to control a pulsation system >>> using square waves with distinct needs for timing etc I hadn't >>> seen any way of 'stepping through the code' (phrase you use later). >> >> Having dabbled in embedded electronics, all I can say is you will just >> have to build it and try to get it working. Failure is always an >> option. If I understand you correctly, this is for a hobby interest, so >> go at it and have fun. >> >> Stepping through code is a basic part of debugging in any language. >> They all have tools for it. Google for python debugging. >> >> "distinct needs for timing?" Did you forget to tell us you need to use >> MicroPython? Certainly MicroPython running on a microcontroller with >> help from hardware timers certainly can do it, but this mailing list is >> not the place to ask about it. Instead you'll have to visit a forum on >> MicroPython or CircuitPython. By the way you definitely can step >> through MicroPython code one line at a time with a remote debugger, say >> with Visual Studio Code. > > Its one of the reasons to use micropython - - - it is a subset of python. > I didn't think I was asking about micropython here though. The project with > the square wave stuff has lots going on so its more likely that regular python > will be used. Part of the challenge is trying to figure out if I need to be > running a real time kernel or even a real time OS. Independent information > is quite hard to find - - - seems like most of the information is by someone > with skin in the game and then without a background its hard to figure out > if what they're saying tells enough so that I can make a good decision or > not. [snip] Maybe see - pyvisa (https://pyvisa.readthedocs.io/en/latest/) https://github.com/mick001/Instruments-Control http://justinbois.github.io/bootcamp/2021/lessons/l40_serial.html https://chaserhkj.gitbooks.io/ivi-book/content/ From dan at djph.net Thu Oct 26 17:42:28 2023 From: dan at djph.net (Dan Purgert) Date: Thu, 26 Oct 2023 21:42:28 -0000 (UTC) Subject: Question(s) References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> Message-ID: On 2023-10-26, o1bigtenor wrote: > On Wed, Oct 25, 2023 at 10:19?AM Michael Torrie via Python-list > wrote: >> >> On 10/25/23 05:51, o1bigtenor via Python-list wrote: >> > Looks like I have another area to investigate. (grin!) >> > Any suggestions? >> >> Seems to me you're trying to run before you have learned to walk. >> >> Slow down, go to the beginning and just learn python, write some code, >> see if it runs. Go through the tutorial at >> https://docs.python.org/3/tutorial/index.html > > Interesting - - - - ". . . see if it runs." - - - that's the issue! > When the code is accessing sensors there isn't an easy way to > check that the code is working until one has done the all of the > physical construction. If I'm trying to control a pulsation system > using square waves with distinct needs for timing etc I hadn't > seen any way of 'stepping through the code' (phrase you use later). You use a hardware debugger then ... and if you're talking hardware, chances are you're also not talking Python (yes, yes, I know "CircuitPython" is a thing, or was it MicroPython?) > [...] > Even in maker threads - - - say for arduino - - its 'use this cut and > paste method of programming' with no mention of any kind of ide when > it was microPython - - although being a subset of python it Idle may > not work with it. Bearing in mind, of course, that "Arduino" is basically "Programming for dummies" level of stuff usually (i.e. people just getting their feet wet). It's meant to be a relatively "easy" introduction for students / hobbiests / non-programmers into the world of programming for microcontrollers. > [...] > My problem is that I'm needing to move quite quickly from 'hello, world' to > something quite a bit more complex. Most of the instruction stuff I've run > into assumes that one is programming only for the joy of learning to > program where I've got things I want to do and - - - sadly - - - they're > not sorta like the run of the mill stuff. Sounds like you've been reading instructables :) -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 From avi.e.gross at gmail.com Thu Oct 26 18:36:08 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Thu, 26 Oct 2023 18:36:08 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> Message-ID: <005701da085c$d05de9c0$7119bd40$@gmail.com> I am not one for IDLE worship, Tenor. But if you have been getting a message here, it is that there are an amazing number of programs that support your use of python during the development phase and perhaps later. I actually often use an environment called RSTUDIO (now part of a new name of POSIT) because it has been expanded beyond supporting R and supports Python and a growing number of other languages or combos that combine word processing with inserts from multiple languages. I have not used it for other languages like C/C++ and Javascript but the point is that like some others, it is not specific to Python but provides support for it. And, somewhat amusingly, you can write programs that combine parts in R and in Python that inter-operate with each other. Since you are taking a fairly overwhelming challenge of trying to learn everything at once while also developing something you want to be perfect and with few if any flaws, it may make sense to start with more of an ASCII editor or something with a few features but a simple interface, and a bit later when some parts of your code are working and you have some experience, you can move the code up a few notches to tools that perform a lot more validation for you. Please consider that resources trying to teach you the language, besides often showing simpler scenarios, often are not going to tell you EVERYTHING else you may need or that is usable let alone teach you all available modules and so on. -----Original Message----- From: Python-list On Behalf Of o1bigtenor via Python-list Sent: Thursday, October 26, 2023 8:34 AM To: Michael Torrie Cc: python-list at python.org Subject: Re: Question(s) On Wed, Oct 25, 2023 at 10:19?AM Michael Torrie via Python-list wrote: > > On 10/25/23 05:51, o1bigtenor via Python-list wrote: > > Looks like I have another area to investigate. (grin!) > > Any suggestions? > > Seems to me you're trying to run before you have learned to walk. > > Slow down, go to the beginning and just learn python, write some code, > see if it runs. Go through the tutorial at > https://docs.python.org/3/tutorial/index.html Interesting - - - - ". . . see if it runs." - - - that's the issue! When the code is accessing sensors there isn't an easy way to check that the code is working until one has done the all of the physical construction. If I'm trying to control a pulsation system using square waves with distinct needs for timing etc I hadn't seen any way of 'stepping through the code' (phrase you use later). > > Your first and most basic tool is the python interpreter. It will tell > you when you try to run your code if you have syntax errors. It's true > that some errors the linters will catch won't show up as syntax errors, > but cross the bridge when you get to it. Once you have a basic grasp of > Python syntax, you can begin using some of the tools Python has for > organizing code: Functions and modules (eventually packages). > Eventually when your logic is placed neatly into functions, you can then > write other python programs that import those functions and feed > different parameters to them and test that the output is what you > expect. That is known as a test. > > Nothing wrong with geany as an editor. However, you might find the > Python Idle IDE useful (it usually installs with Python), as it lets you > work more interactively with your code, inspecting and interacting with > live python objects in memory. It also integrates debugging > functionality to let you step through your code one line at a time and > watch variables and how they change. I have been following this list for some time. Don't believe that I've ever seen anything where anyone was referred to 'Idle'. In reading other user group threads I have heard lots about java and its ide - - - don't remember, again, any re: an ide for python. Even in maker threads - - - say for arduino - - its 'use this cut and paste method of programming' with no mention of any kind of ide when it was microPython - - although being a subset of python it Idle may not work with it. > > When you encounter isses with your code (syntax or logical) that you > can't solve, you can come to the list, show your code and the full > output of the interpreter that shows the complete error message and back > trace and I think you'll get a lot of helpful responses. > -- That was the plan. My problem is that I'm needing to move quite quickly from 'hello, world' to something quite a bit more complex. Most of the instruction stuff I've run into assumes that one is programming only for the joy of learning to program where I've got things I want to do and - - - sadly - - - they're not sorta like the run of the mill stuff. Oh well - - - I am working on things! Thanks for the ideas and the assistance! Regards -- https://mail.python.org/mailman/listinfo/python-list From list1 at tompassin.net Thu Oct 26 18:50:01 2023 From: list1 at tompassin.net (Thomas Passin) Date: Thu, 26 Oct 2023 18:50:01 -0400 Subject: Question(s) In-Reply-To: <005701da085c$d05de9c0$7119bd40$@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> <005701da085c$d05de9c0$7119bd40$@gmail.com> Message-ID: On 10/26/2023 6:36 PM, AVI GROSS via Python-list wrote: > I am not one for IDLE worship, Tenor. But if you have been getting a message here, it is that there are an amazing number of programs that support your use of python during the development phase and perhaps later. I actually often use an environment called RSTUDIO (now part of a new name of POSIT) because it has been expanded beyond supporting R and supports Python and a growing number of other languages or combos that combine word processing with inserts from multiple languages. Excellent! I didn't know about this development. [snip] From avi.e.gross at gmail.com Thu Oct 26 22:52:25 2023 From: avi.e.gross at gmail.com (avi.e.gross at gmail.com) Date: Thu, 26 Oct 2023 22:52:25 -0400 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> <005701da085c$d05de9c0$7119bd40$@gmail.com> Message-ID: <00ff01da0880$9daf04e0$d90d0ea0$@gmail.com> Thomas, It looks like much of our discussion and attempts at help are not going to be that helpful to Tenor as we may be way off bass about what he wants to do and certainly RSTUDIO and quite a few other suggestions may not be available in his microcontroller. As I see it, some of his objective involves sampling a sensor in real time. I have not heard what he wants to do with the data gathered and this may be an example of where code needs to be running fast enough to keep up. Proving the code will work, especially if you add logging or print statements or run it in a monitored mode so you can follow what it is doing, presents special challenges. Now if he ever wants to read in a .CSV file and analyze the data and make graphs and so on, I might chime in. For now, I am dropping out. Avi -----Original Message----- From: Python-list On Behalf Of Thomas Passin via Python-list Sent: Thursday, October 26, 2023 6:50 PM To: python-list at python.org Subject: Re: Question(s) On 10/26/2023 6:36 PM, AVI GROSS via Python-list wrote: > I am not one for IDLE worship, Tenor. But if you have been getting a message here, it is that there are an amazing number of programs that support your use of python during the development phase and perhaps later. I actually often use an environment called RSTUDIO (now part of a new name of POSIT) because it has been expanded beyond supporting R and supports Python and a growing number of other languages or combos that combine word processing with inserts from multiple languages. Excellent! I didn't know about this development. [snip] -- https://mail.python.org/mailman/listinfo/python-list From list1 at tompassin.net Thu Oct 26 23:16:17 2023 From: list1 at tompassin.net (Thomas Passin) Date: Thu, 26 Oct 2023 23:16:17 -0400 Subject: Question(s) In-Reply-To: <00ff01da0880$9daf04e0$d90d0ea0$@gmail.com> References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> <2968ccb6-21e0-2e29-29c8-1c0803fe55e8@gmail.com> <005701da085c$d05de9c0$7119bd40$@gmail.com> <00ff01da0880$9daf04e0$d90d0ea0$@gmail.com> Message-ID: <63b10552-9796-408c-8743-60386a6b9eb4@tompassin.net> On 10/26/2023 10:52 PM, avi.e.gross at gmail.com wrote: > Thomas, > > It looks like much of our discussion and attempts at help are not going to > be that helpful to Tenor as we may be way off bass about what he wants to do > and certainly RSTUDIO and quite a few other suggestions may not be available > in his microcontroller. > > As I see it, some of his objective involves sampling a sensor in real time. > I have not heard what he wants to do with the data gathered and this may be > an example of where code needs to be running fast enough to keep up. Proving > the code will work, especially if you add logging or print statements or run > it in a monitored mode so you can follow what it is doing, presents special > challenges. > > Now if he ever wants to read in a .CSV file and analyze the data and make > graphs and so on, I might chime in. For now, I am dropping out. > Avi I'm there. It's like someone is insisting on being instructed how to drive a race car in a race when he's only got a learner's permit. You just have to go through the experience of actually driving on streets and in traffic first. There is no substitute. TomP > -----Original Message----- > From: Python-list On > Behalf Of Thomas Passin via Python-list > Sent: Thursday, October 26, 2023 6:50 PM > To: python-list at python.org > Subject: Re: Question(s) > > On 10/26/2023 6:36 PM, AVI GROSS via Python-list wrote: >> I am not one for IDLE worship, Tenor. But if you have been getting a > message here, it is that there are an amazing number of programs that > support your use of python during the development phase and perhaps later. I > actually often use an environment called RSTUDIO (now part of a new name of > POSIT) because it has been expanded beyond supporting R and supports Python > and a growing number of other languages or combos that combine word > processing with inserts from multiple languages. > > Excellent! I didn't know about this development. > > [snip] > > From greg.ewing at canterbury.ac.nz Fri Oct 27 04:17:51 2023 From: greg.ewing at canterbury.ac.nz (Greg Ewing) Date: Fri, 27 Oct 2023 21:17:51 +1300 Subject: Question(s) In-Reply-To: References: <58b56dbe-646c-4a94-8102-ac2cf6efe233@tompassin.net> Message-ID: On 25/10/23 2:32 pm, Chris Angelico wrote: > Error correcting memory, redundant systems, and human > monitoring, plus the ability to rewrite the guidance software on the > fly if they needed to. Although the latter couldn't actually be done with the AGC, as the software was in ROM. They could poke values into RAM to change its behaviour to some extent, and that got them out of trouble a few times, but they couldn't patch the code. It might have been possible with the Gemini computer, since it loaded its code from tape. I don't know if it was ever done, though. -- Greg From loris.bennett at fu-berlin.de Fri Oct 27 03:29:16 2023 From: loris.bennett at fu-berlin.de (Loris Bennett) Date: Fri, 27 Oct 2023 09:29:16 +0200 Subject: NameError: name '__version__' is not defined Message-ID: <87cyx04j77.fsf@zedat.fu-berlin.de> Hi, I have two applications. One uses the system version of Python, which is 3.6.8, whereas the other uses Python 3.10.8 installed in a non-system path. For both applications I am using poetry with a pyproject.toml file which contains the version information and __init__.py at the root which contains try: import importlib.metadata as importlib_metadata except ModuleNotFoundError: import importlib_metadata __version__ = importlib_metadata.version(__name__) For the application with the system Python this mechanism works, but for the non-system Python I get the error: NameError: name '__version__' is not defined For the 3.6 application I have PYTHONPATH=/nfs/local/lib/python3.6/site-packages PYTHONUSERBASE=/nfs/local PYTHON_VERSION=3.6 PYTHON_VIRTUALENV= and for the 3.10 application I have PYTHONPATH=/nfs/easybuild/software/Python/3.10.8-GCCcore-12.2.0/easybuild/python:/nfs/local/lib/python3.10/site-packages PYTHONUSERBASE=/nfs/local PYTHON_VERSION=3.10 PYTHON_VIRTUALENV= The applications are installed in /nfs/local/lib/python3.6/site-packages and /nfs/local/lib/python3.10/site-packages, respectively. Can anyone see where this is going wrong? I thought it should be enough that the packages with the metadata is available via PYTHONPATH, but this seems not to be sufficient. So I must be overseeing something. Cheers, Loris -- This signature is currently under constuction. From loris.bennett at fu-berlin.de Fri Oct 27 04:54:35 2023 From: loris.bennett at fu-berlin.de (Loris Bennett) Date: Fri, 27 Oct 2023 10:54:35 +0200 Subject: NameError: name '__version__' is not defined References: <87cyx04j77.fsf@zedat.fu-berlin.de> Message-ID: <8734xw4f90.fsf@zedat.fu-berlin.de> "Loris Bennett" writes: > Hi, > > I have two applications. One uses the system version of Python, which > is 3.6.8, whereas the other uses Python 3.10.8 installed in a non-system > path. For both applications I am using poetry with a pyproject.toml > file which contains the version information and __init__.py at the root > which contains > > try: > import importlib.metadata as importlib_metadata > except ModuleNotFoundError: > import importlib_metadata > > __version__ = importlib_metadata.version(__name__) > > For the application with the system Python this mechanism works, but for > the non-system Python I get the error: > > NameError: name '__version__' is not defined > > For the 3.6 application I have > > PYTHONPATH=/nfs/local/lib/python3.6/site-packages > PYTHONUSERBASE=/nfs/local > PYTHON_VERSION=3.6 > PYTHON_VIRTUALENV= > > and for the 3.10 application I have > > PYTHONPATH=/nfs/easybuild/software/Python/3.10.8-GCCcore-12.2.0/easybuild/python:/nfs/local/lib/python3.10/site-packages > PYTHONUSERBASE=/nfs/local > PYTHON_VERSION=3.10 > PYTHON_VIRTUALENV= > > The applications are installed in /nfs/local/lib/python3.6/site-packages > and /nfs/local/lib/python3.10/site-packages, respectively. > > Can anyone see where this is going wrong? I thought it should be > enough that the packages with the metadata is available via PYTHONPATH, > but this seems not to be sufficient. So I must be overseeing something. If in the 3.10 application I add print(f"__init__ Version: {__version__}") to __init__.py the correct version is printed. So the problem is that the variable is not available at the point I am trying access it. The relevant code (a far as I can tell) in main.py looks like this: import typer app = typer.Typer() @app.callback() def version_callback(value: bool): if value: typer.echo(f"Version: {__version__}") raise typer.Exit() @app.callback() def common( ctx: typer.Context, version: bool = typer.Option(None, "--version", help="Show version", callback=version_callback), ): pass if __name__ == "__main__": app() This is the first time I have used typer, so it is more than likely that I have made some mistakes. Cheers, Loris -- This signature is currently under constuction. From loris.bennett at fu-berlin.de Fri Oct 27 05:20:02 2023 From: loris.bennett at fu-berlin.de (Loris Bennett) Date: Fri, 27 Oct 2023 11:20:02 +0200 Subject: NameError: name '__version__' is not defined References: <87cyx04j77.fsf@zedat.fu-berlin.de> <8734xw4f90.fsf@zedat.fu-berlin.de> Message-ID: <87y1fo2zi5.fsf@zedat.fu-berlin.de> "Loris Bennett" writes: > "Loris Bennett" writes: > >> Hi, >> >> I have two applications. One uses the system version of Python, which >> is 3.6.8, whereas the other uses Python 3.10.8 installed in a non-system >> path. For both applications I am using poetry with a pyproject.toml >> file which contains the version information and __init__.py at the root >> which contains >> >> try: >> import importlib.metadata as importlib_metadata >> except ModuleNotFoundError: >> import importlib_metadata >> >> __version__ = importlib_metadata.version(__name__) >> >> For the application with the system Python this mechanism works, but for >> the non-system Python I get the error: >> >> NameError: name '__version__' is not defined >> >> For the 3.6 application I have >> >> PYTHONPATH=/nfs/local/lib/python3.6/site-packages >> PYTHONUSERBASE=/nfs/local >> PYTHON_VERSION=3.6 >> PYTHON_VIRTUALENV= >> >> and for the 3.10 application I have >> >> PYTHONPATH=/nfs/easybuild/software/Python/3.10.8-GCCcore-12.2.0/easybuild/python:/nfs/local/lib/python3.10/site-packages >> PYTHONUSERBASE=/nfs/local >> PYTHON_VERSION=3.10 >> PYTHON_VIRTUALENV= >> >> The applications are installed in /nfs/local/lib/python3.6/site-packages >> and /nfs/local/lib/python3.10/site-packages, respectively. >> >> Can anyone see where this is going wrong? I thought it should be >> enough that the packages with the metadata is available via PYTHONPATH, >> but this seems not to be sufficient. So I must be overseeing something. > > If in the 3.10 application I add > > print(f"__init__ Version: {__version__}") > > to __init__.py the correct version is printed. So the problem is that > the variable is not available at the point I am trying access it. The > relevant code (a far as I can tell) in main.py looks like this: > > import typer > > app = typer.Typer() > > > @app.callback() > def version_callback(value: bool): > if value: > typer.echo(f"Version: {__version__}") > raise typer.Exit() > > > @app.callback() > def common( > ctx: typer.Context, > version: bool = typer.Option(None, "--version", > help="Show version", > callback=version_callback), > ): > pass > > if __name__ == "__main__": > > app() > > This is the first time I have used typer, so it is more than likely that > I have made some mistakes. OK, I worked it out. Instead of typer.echo(f"Version: {__version__}") I need typer.echo(f"Version: {mypackage.__version__}") Thanks for the help :-) Even if no-one replies, it still helps me to have to formulate the problem for an audience of people who probably know more than I do. Cheers, Loris -- This signature is currently under constuction. From dieter at handshake.de Fri Oct 27 14:33:15 2023 From: dieter at handshake.de (Dieter Maurer) Date: Fri, 27 Oct 2023 20:33:15 +0200 Subject: NameError: name '__version__' is not defined In-Reply-To: <87cyx04j77.fsf@zedat.fu-berlin.de> References: <87cyx04j77.fsf@zedat.fu-berlin.de> Message-ID: <25916.619.96240.943905@ixdm.fritz.box> Loris Bennett wrote at 2023-10-27 09:29 +0200: > ... >For the application with the system Python this mechanism works, but for >the non-system Python I get the error: > > NameError: name '__version__' is not defined If you get exceptions (they usually end in `Error` (such as `NameError`)), look at the traceback. The traceback informs you about the calling context that led to the exception, espeically where in the code the exception occurred. If you cannot resolve the problem at your own, include the traceback in your call for assistence. From fabiofz at gmail.com Sun Oct 29 10:35:44 2023 From: fabiofz at gmail.com (Fabio Zadrozny) Date: Sun, 29 Oct 2023 11:35:44 -0300 Subject: PyDev 11.0.2 Released Message-ID: PyDev 11.0.2 Release Highlights Continuing with the updates to Python 3.12, the new release integrates the latest version of typeshed (so, *from typing import override* is now properly recognized). Also, it's now possible to specify vmargs in the python interpreter (and not just in the launch configuration). For Python 3.11 onwards, *-Xfrozen_modules=off* is now set in the vm arguments by default. About PyDev PyDev is an open-source Python IDE on top of Eclipse for Python (also available for Python on Visual Studio Code). It comes with goodies such as code completion, syntax highlighting, syntax analysis, code analysis, refactor, debug, interactive console, etc. It is also available as a standalone through LiClipse with goodies such as multiple cursors, theming and support for many other languages, such as Django Templates, Jinja2, Html, JavaScript, etc. Links: PyDev: http://pydev.org PyDev Blog: http://pydev.blogspot.com PyDev on VSCode: http://pydev.org/vscode LiClipse: http://www.liclipse.com PyVmMonitor - Python Profiler: http://www.pyvmmonitor.com/ Cheers, Fabio Zadrozny From cl at isbd.net Sat Oct 28 12:08:00 2023 From: cl at isbd.net (Chris Green) Date: Sat, 28 Oct 2023 17:08:00 +0100 Subject: How to find any documentation for smbus? Message-ID: <08ov0k-kpc23.ln1@esprimo.zbmc.eu> I am using the python3 smbus module, but it's hard work because of the lack of documentation. Web searches confirm that the documentation is somewhat thin! If you do the obvious this is what you get:- >>> import smbus >>> dir (smbus) ['SMBus', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__spec__'] >>> help(smbus) Help on module SMBus: NAME SMBus DESCRIPTION This module defines an object type that allows SMBus transactions on hosts running the Linux kernel. The host kernel must have I2C support, I2C device interface support, and a bus adapter driver. All of these can be either built-in to the kernel, or loaded from modules. Because the I2C device interface is opened R/W, users of this module usually must have root permissions. FILE /usr/lib/python3/dist-packages/smbus.cpython-39-arm-linux-gnueabihf.so Even a list of available methods would be handy! :-) Presumably python3's smbus is just a wrapper so if I could find the underlying C/C++ documentation it might help. -- Chris Green ? From kammamuri at libero.it Sat Oct 28 16:19:22 2023 From: kammamuri at libero.it (km) Date: Sat, 28 Oct 2023 20:19:22 -0000 (UTC) Subject: How to find any documentation for smbus? References: <08ov0k-kpc23.ln1@esprimo.zbmc.eu> Message-ID: Il Sat, 28 Oct 2023 17:08:00 +0100, Chris Green ha scritto: > I am using the python3 smbus module, but it's hard work because of the > lack of documentation. Web searches confirm that the documentation is > somewhat thin! > > If you do the obvious this is what you get:- > > >>> import smbus dir (smbus) > ['SMBus', '__doc__', '__file__', '__loader__', '__name__', > '__package__', '__spec__'] > >>> help(smbus) > > > Help on module SMBus: > > NAME > SMBus > > DESCRIPTION > This module defines an object type that allows SMBus > transactions on hosts running the Linux kernel. The host kernel > must have I2C support, I2C device interface support, and a bus > adapter driver. > All of these can be either built-in to the kernel, or loaded > from modules. > > Because the I2C device interface is opened R/W, users of this > module usually must have root permissions. > > FILE > /usr/lib/python3/dist-packages/smbus.cpython-39-arm-linux- gnueabihf.so > > > Even a list of available methods would be handy! :-) > > > Presumably python3's smbus is just a wrapper so if I could find the > underlying C/C++ > documentation it might help. https://pypi.org/project/smbus2/ smbus2 is designed to be a "drop-in replacement of smbus". SO you can look at its documentation for or use it instead of smbus. Disclaimer: I haven't any experience on this library From cl at isbd.net Sun Oct 29 09:46:19 2023 From: cl at isbd.net (Chris Green) Date: Sun, 29 Oct 2023 13:46:19 +0000 Subject: How to find any documentation for smbus? References: <08ov0k-kpc23.ln1@esprimo.zbmc.eu> Message-ID: km wrote: > Il Sat, 28 Oct 2023 17:08:00 +0100, Chris Green ha scritto: > > > I am using the python3 smbus module, but it's hard work because of the > > lack of documentation. Web searches confirm that the documentation is > > somewhat thin! > > > > If you do the obvious this is what you get:- > > > > >>> import smbus dir (smbus) > > ['SMBus', '__doc__', '__file__', '__loader__', '__name__', > > '__package__', '__spec__'] > > >>> help(smbus) > > > > > > Help on module SMBus: > > > > NAME > > SMBus > > > > DESCRIPTION > > This module defines an object type that allows SMBus > > transactions on hosts running the Linux kernel. The host kernel > > must have I2C support, I2C device interface support, and a bus > > adapter driver. > > All of these can be either built-in to the kernel, or loaded > > from modules. > > > > Because the I2C device interface is opened R/W, users of this > > module usually must have root permissions. > > > > FILE > > /usr/lib/python3/dist-packages/smbus.cpython-39-arm-linux- > gnueabihf.so > > > > > > Even a list of available methods would be handy! :-) > > > > > > Presumably python3's smbus is just a wrapper so if I could find the > > underlying C/C++ > > documentation it might help. > > https://pypi.org/project/smbus2/ > > smbus2 is designed to be a "drop-in replacement of smbus". SO you can look > at its documentation for or use it instead of smbus. > > Disclaimer: I haven't any experience on this library Ah, thank you, I had come across smbus2 but wanted to stay with smbus if I could as it's in the Debian repositories. However, as you say, it claims to be a "drop-in replacement of smbus" so the documentation should be some help at least. -- Chris Green ? From cl at isbd.net Sat Oct 28 12:50:51 2023 From: cl at isbd.net (Chris Green) Date: Sat, 28 Oct 2023 17:50:51 +0100 Subject: How to find any documentation for smbus? References: <08ov0k-kpc23.ln1@esprimo.zbmc.eu> Message-ID: Dan Purgert wrote: > On 2023-10-28, Chris Green wrote: > > I am using the python3 smbus module, but it's hard work because of the > > lack of documentation. Web searches confirm that the documentation is > > somewhat thin! > > > > The SMBus spec is available from http://smbus.org (or at least it used > to be ... watch it be hidden behind a paywall now). > That provides very detailed hardware information but virtually nothing at all about software libraries and such. Lots of interesting reading, for example there's an appendix detailing the differences between smbus and i2c, but nothing very helpful for a poor old application programmer like me! :-) -- Chris Green ? From dieter at handshake.de Mon Oct 30 12:55:33 2023 From: dieter at handshake.de (Dieter Maurer) Date: Mon, 30 Oct 2023 17:55:33 +0100 Subject: How to find any documentation for smbus? In-Reply-To: <08ov0k-kpc23.ln1@esprimo.zbmc.eu> References: <08ov0k-kpc23.ln1@esprimo.zbmc.eu> Message-ID: <25919.57349.716380.748196@ixdm.fritz.box> Chris Green wrote at 2023-10-28 17:08 +0100: >I am using the python3 smbus module, but it's hard work because of the >lack of documentation. Web searches confirm that the documentation is >somewhat thin! > >If you do the obvious this is what you get:- > > >>> import smbus > >>> dir (smbus) > ['SMBus', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__spec__'] > >>> help(smbus) > ... What does `help(smbus.SMBus`) tell you? Almost surely, `SMBus` is a class providing the main access methods. From ez609 at ncf.ca Mon Oct 30 15:19:27 2023 From: ez609 at ncf.ca (McDermott Family) Date: Mon, 30 Oct 2023 15:19:27 -0400 Subject: PyInstaller value error: Invalid Windows resource specifier Message-ID: <002201da0b66$00940000$01bc0000$@ncf.ca> Hello, I am trying to create a one file executable with pyinstaller 6.1.0 and auto-py-to-exe 2.41.0 using Python version 3.10.9 in a virtual environment. Some points before the output of pinstaller is shown. My resource .py file is there where it should be. Also I can fun my program from the command-line and it does work with the compiled resource file without a problem. Any help would be greatly appreciated. Thank you. Running auto-py-to-exe v2.41.0 Building directory: C:\Users\icnte\AppData\Local\Temp\tmpp870eytg Provided command: pyinstaller --noconfirm --onefile --windowed --icon "D:/Work/Python/cfepy310/xl/cfegui/Resources/Conform-e_48_1.ico" --name "Conform-e" --clean --log-level "DEBUG" --debug "all" --version-file "D:/Work/Python/cfepy310/xl/cfegui/cfe_versionfile.txt" --resource "D:/Work/Python/cfepy310/xl/cfegui/cfe_Resource_rc.py" "D:/Work/Python/cfepy310/xl/cfegui/cfe_MainForm.py" Recursion Limit is set to 5000 Executing: pyinstaller --noconfirm --onefile --windowed --icon D:/Work/Python/cfepy310/xl/cfegui/Resources/Conform-e_48_1.ico --name Conform-e --clean --log-level DEBUG --debug all --version-file D:/Work/Python/cfepy310/xl/cfegui/cfe_versionfile.txt --resource D:/Work/Python/cfepy310/xl/cfegui/cfe_Resource_rc.py D:/Work/Python/cfepy310/xl/cfegui/cfe_MainForm.py --distpath C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\application --workpath C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\build --specpath C:\Users\icnte\AppData\Local\Temp\tmpp870eytg 79547 INFO: PyInstaller: 6.1.0 79547 INFO: Python: 3.10.9 79564 INFO: Platform: Windows-10-10.0.22621-SP0 79578 INFO: wrote C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\Conform-e.spec 79580 DEBUG: Testing UPX availability ... 79595 DEBUG: UPX is not available. 79597 INFO: Removing temporary files and cleaning cache in C:\Users\icnte\AppData\Local\pyinstaller 79597 DEBUG: script: D:\Work\Python\cfepy310\xl\cfegui\cfe_MainForm.py 79611 INFO: Extending PYTHONPATH with paths ['D:\\Work\\Python\\cfepy310\\xl\\cfegui'] 79907 INFO: checking Analysis 79911 INFO: Building Analysis because Analysis-00.toc is non existent 79922 INFO: Initializing module dependency graph... 79945 INFO: Caching module graph hooks... 79983 INFO: Analyzing base_library.zip ... 79996 DEBUG: Collecting submodules for encodings 80425 DEBUG: collect_submodules - found submodules: ['encodings', 'encodings.aliases', 'encodings.ascii', 'encodings.base64_codec', 'encodings.big5', 'encodings.big5hkscs', 'encodings.bz2_codec', 'encodings.charmap', 'encodings.cp037', 'encodings.cp1006', 'encodings.cp1026', 'encodings.cp1125', 'encodings.cp1140', 'encodings.cp1250', 'encodings.cp1251', 'encodings.cp1252', 'encodings.cp1253', 'encodings.cp1254', 'encodings.cp1255', 'encodings.cp1256', 'encodings.cp1257', 'encodings.cp1258', 'encodings.cp273', 'encodings.cp424', 'encodings.cp437', 'encodings.cp500', 'encodings.cp720', 'encodings.cp737', 'encodings.cp775', 'encodings.cp850', 'encodings.cp852', 'encodings.cp855', 'encodings.cp856', 'encodings.cp857', 'encodings.cp858', 'encodings.cp860', 'encodings.cp861', 'encodings.cp862', 'encodings.cp863', 'encodings.cp864', 'encodings.cp865', 'encodings.cp866', 'encodings.cp869', 'encodings.cp874', 'encodings.cp875', 'encodings.cp932', 'encodings.cp949', 'encodings.cp950', 'encodings.euc_jis_2004', 'encodings.euc_jisx0213', 'encodings.euc_jp', 'encodings.euc_kr', 'encodings.gb18030', 'encodings.gb2312', 'encodings.gbk', 'encodings.hex_codec', 'encodings.hp_roman8', 'encodings.hz', 'encodings.idna', 'encodings.iso2022_jp', 'encodings.iso2022_jp_1', 'encodings.iso2022_jp_2', 'encodings.iso2022_jp_2004', 'encodings.iso2022_jp_3', 'encodings.iso2022_jp_ext', 'encodings.iso2022_kr', 'encodings.iso8859_1', 'encodings.iso8859_10', 'encodings.iso8859_11', 'encodings.iso8859_13', 'encodings.iso8859_14', 'encodings.iso8859_15', 'encodings.iso8859_16', 'encodings.iso8859_2', 'encodings.iso8859_3', 'encodings.iso8859_4', 'encodings.iso8859_5', 'encodings.iso8859_6', 'encodings.iso8859_7', 'encodings.iso8859_8', 'encodings.iso8859_9', 'encodings.johab', 'encodings.koi8_r', 'encodings.koi8_t', 'encodings.koi8_u', 'encodings.kz1048', 'encodings.latin_1', 'encodings.mac_arabic', 'encodings.mac_croatian', 'encodings.mac_cyrillic', 'encodings.mac_farsi', 'encodings.mac_greek', 'encodings.mac_iceland', 'encodings.mac_latin2', 'encodings.mac_roman', 'encodings.mac_romanian', 'encodings.mac_turkish', 'encodings.mbcs', 'encodings.oem', 'encodings.palmos', 'encodings.ptcp154', 'encodings.punycode', 'encodings.quopri_codec', 'encodings.raw_unicode_escape', 'encodings.rot_13', 'encodings.shift_jis', 'encodings.shift_jis_2004', 'encodings.shift_jisx0213', 'encodings.tis_620', 'encodings.undefined', 'encodings.unicode_escape', 'encodings.utf_16', 'encodings.utf_16_be', 'encodings.utf_16_le', 'encodings.utf_32', 'encodings.utf_32_be', 'encodings.utf_32_le', 'encodings.utf_7', 'encodings.utf_8', 'encodings.utf_8_sig', 'encodings.uu_codec', 'encodings.zlib_codec'] 80437 DEBUG: Collecting submodules for collections 80859 DEBUG: collect_submodules - found submodules: ['collections', 'collections.abc'] 81007 INFO: Loading module hook 'hook-heapq.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 81015 DEBUG: Suppressing import of 'doctest' from module 'heapq' due to excluded import 'doctest' specified in a hook for 'heapq' (or its parent package(s)). 81080 INFO: Loading module hook 'hook-encodings.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 81099 DEBUG: Collecting submodules for encodings 81523 DEBUG: collect_submodules - found submodules: ['encodings', 'encodings.aliases', 'encodings.ascii', 'encodings.base64_codec', 'encodings.big5', 'encodings.big5hkscs', 'encodings.bz2_codec', 'encodings.charmap', 'encodings.cp037', 'encodings.cp1006', 'encodings.cp1026', 'encodings.cp1125', 'encodings.cp1140', 'encodings.cp1250', 'encodings.cp1251', 'encodings.cp1252', 'encodings.cp1253', 'encodings.cp1254', 'encodings.cp1255', 'encodings.cp1256', 'encodings.cp1257', 'encodings.cp1258', 'encodings.cp273', 'encodings.cp424', 'encodings.cp437', 'encodings.cp500', 'encodings.cp720', 'encodings.cp737', 'encodings.cp775', 'encodings.cp850', 'encodings.cp852', 'encodings.cp855', 'encodings.cp856', 'encodings.cp857', 'encodings.cp858', 'encodings.cp860', 'encodings.cp861', 'encodings.cp862', 'encodings.cp863', 'encodings.cp864', 'encodings.cp865', 'encodings.cp866', 'encodings.cp869', 'encodings.cp874', 'encodings.cp875', 'encodings.cp932', 'encodings.cp949', 'encodings.cp950', 'encodings.euc_jis_2004', 'encodings.euc_jisx0213', 'encodings.euc_jp', 'encodings.euc_kr', 'encodings.gb18030', 'encodings.gb2312', 'encodings.gbk', 'encodings.hex_codec', 'encodings.hp_roman8', 'encodings.hz', 'encodings.idna', 'encodings.iso2022_jp', 'encodings.iso2022_jp_1', 'encodings.iso2022_jp_2', 'encodings.iso2022_jp_2004', 'encodings.iso2022_jp_3', 'encodings.iso2022_jp_ext', 'encodings.iso2022_kr', 'encodings.iso8859_1', 'encodings.iso8859_10', 'encodings.iso8859_11', 'encodings.iso8859_13', 'encodings.iso8859_14', 'encodings.iso8859_15', 'encodings.iso8859_16', 'encodings.iso8859_2', 'encodings.iso8859_3', 'encodings.iso8859_4', 'encodings.iso8859_5', 'encodings.iso8859_6', 'encodings.iso8859_7', 'encodings.iso8859_8', 'encodings.iso8859_9', 'encodings.johab', 'encodings.koi8_r', 'encodings.koi8_t', 'encodings.koi8_u', 'encodings.kz1048', 'encodings.latin_1', 'encodings.mac_arabic', 'encodings.mac_croatian', 'encodings.mac_cyrillic', 'encodings.mac_farsi', 'encodings.mac_greek', 'encodings.mac_iceland', 'encodings.mac_latin2', 'encodings.mac_roman', 'encodings.mac_romanian', 'encodings.mac_turkish', 'encodings.mbcs', 'encodings.oem', 'encodings.palmos', 'encodings.ptcp154', 'encodings.punycode', 'encodings.quopri_codec', 'encodings.raw_unicode_escape', 'encodings.rot_13', 'encodings.shift_jis', 'encodings.shift_jis_2004', 'encodings.shift_jisx0213', 'encodings.tis_620', 'encodings.undefined', 'encodings.unicode_escape', 'encodings.utf_16', 'encodings.utf_16_be', 'encodings.utf_16_le', 'encodings.utf_32', 'encodings.utf_32_be', 'encodings.utf_32_le', 'encodings.utf_7', 'encodings.utf_8', 'encodings.utf_8_sig', 'encodings.uu_codec', 'encodings.zlib_codec'] 83596 INFO: Loading module hook 'hook-pickle.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 83728 DEBUG: Suppressing import of 'doctest' from module 'pickle' due to excluded import 'doctest' specified in a hook for 'pickle' (or its parent package(s)). 83743 DEBUG: Suppressing import of 'argparse' from module 'pickle' due to excluded import 'argparse' specified in a hook for 'pickle' (or its parent package(s)). 87892 INFO: Caching module dependency graph... 87969 DEBUG: Adding python files to base_library.zip 88131 INFO: Running Analysis Analysis-00.toc 88147 INFO: Looking for Python shared library... 88156 INFO: Using Python shared library: C:\Users\icnte\AppData\Local\Programs\Python\Python310\python310.dll 88172 INFO: Analyzing D:\Work\Python\cfepy310\xl\cfegui\cfe_MainForm.py 88362 INFO: Processing pre-safe import module hook distutils from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\pre_saf e_import_module\\hook-distutils.py'. 88437 INFO: Processing pre-find module path hook distutils from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\pre_fin d_module_path\\hook-distutils.py'. 90518 DEBUG: distutils: provided by setuptools 90528 INFO: Loading module hook 'hook-distutils.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 90762 INFO: Loading module hook 'hook-sysconfig.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 90809 DEBUG: Suppressing import of '_osx_support' from module 'sysconfig' due to excluded import '_osx_support' specified in a hook for 'sysconfig' (or its parent package(s)). 90889 DEBUG: Suppressing import of '_osx_support' from module 'sysconfig' due to excluded import '_osx_support' specified in a hook for 'sysconfig' (or its parent package(s)). 91660 INFO: Loading module hook 'hook-platform.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 91680 DEBUG: Suppressing import of 'plistlib' from module 'platform' due to excluded import 'plistlib' specified in a hook for 'platform' (or its parent package(s)). 92037 INFO: Loading module hook 'hook-xml.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 92152 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 92740 INFO: Loading module hook 'hook-lib2to3.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 92783 DEBUG: Collecting data files for lib2to3 93042 DEBUG: collect_data_files - Found files: [('C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\lib\\lib2t o3\\tests\\data\\README', 'lib2to3\\tests\\data'), ('C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\lib\\lib2to 3\\PatternGrammar.txt', 'lib2to3'), ('C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\lib\\lib2to 3\\Grammar.txt', 'lib2to3')] 93295 INFO: Processing pre-safe import module hook six.moves from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\pre_saf e_import_module\\hook-six.moves.py'. 93437 INFO: Loading module hook 'hook-pygments.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 93456 DEBUG: Collecting submodules for pygments.formatters 94073 DEBUG: collect_submodules - found submodules: ['pygments.formatters', 'pygments.formatters._mapping', 'pygments.formatters.bbcode', 'pygments.formatters.groff', 'pygments.formatters.html', 'pygments.formatters.img', 'pygments.formatters.irc', 'pygments.formatters.latex', 'pygments.formatters.other', 'pygments.formatters.pangomarkup', 'pygments.formatters.rtf', 'pygments.formatters.svg', 'pygments.formatters.terminal', 'pygments.formatters.terminal256'] 94091 DEBUG: Collecting submodules for pygments.lexers 95300 DEBUG: collect_submodules - found submodules: ['pygments.lexers', 'pygments.lexers._ada_builtins', 'pygments.lexers._asy_builtins', 'pygments.lexers._cl_builtins', 'pygments.lexers._cocoa_builtins', 'pygments.lexers._csound_builtins', 'pygments.lexers._css_builtins', 'pygments.lexers._julia_builtins', 'pygments.lexers._lasso_builtins', 'pygments.lexers._lilypond_builtins', 'pygments.lexers._lua_builtins', 'pygments.lexers._mapping', 'pygments.lexers._mql_builtins', 'pygments.lexers._mysql_builtins', 'pygments.lexers._openedge_builtins', 'pygments.lexers._php_builtins', 'pygments.lexers._postgres_builtins', 'pygments.lexers._qlik_builtins', 'pygments.lexers._scheme_builtins', 'pygments.lexers._scilab_builtins', 'pygments.lexers._sourcemod_builtins', 'pygments.lexers._stan_builtins', 'pygments.lexers._stata_builtins', 'pygments.lexers._tsql_builtins', 'pygments.lexers._usd_builtins', 'pygments.lexers._vbscript_builtins', 'pygments.lexers._vim_builtins', 'pygments.lexers.actionscript', 'pygments.lexers.ada', 'pygments.lexers.agile', 'pygments.lexers.algebra', 'pygments.lexers.ambient', 'pygments.lexers.amdgpu', 'pygments.lexers.ampl', 'pygments.lexers.apdlexer', 'pygments.lexers.apl', 'pygments.lexers.archetype', 'pygments.lexers.arrow', 'pygments.lexers.asc', 'pygments.lexers.asm', 'pygments.lexers.automation', 'pygments.lexers.bare', 'pygments.lexers.basic', 'pygments.lexers.bdd', 'pygments.lexers.berry', 'pygments.lexers.bibtex', 'pygments.lexers.boa', 'pygments.lexers.business', 'pygments.lexers.c_cpp', 'pygments.lexers.c_like', 'pygments.lexers.capnproto', 'pygments.lexers.cddl', 'pygments.lexers.chapel', 'pygments.lexers.clean', 'pygments.lexers.comal', 'pygments.lexers.compiled', 'pygments.lexers.configs', 'pygments.lexers.console', 'pygments.lexers.cplint', 'pygments.lexers.crystal', 'pygments.lexers.csound', 'pygments.lexers.css', 'pygments.lexers.d', 'pygments.lexers.dalvik', 'pygments.lexers.data', 'pygments.lexers.devicetree', 'pygments.lexers.diff', 'pygments.lexers.dotnet', 'pygments.lexers.dsls', 'pygments.lexers.dylan', 'pygments.lexers.ecl', 'pygments.lexers.eiffel', 'pygments.lexers.elm', 'pygments.lexers.elpi', 'pygments.lexers.email', 'pygments.lexers.erlang', 'pygments.lexers.esoteric', 'pygments.lexers.ezhil', 'pygments.lexers.factor', 'pygments.lexers.fantom', 'pygments.lexers.felix', 'pygments.lexers.floscript', 'pygments.lexers.forth', 'pygments.lexers.fortran', 'pygments.lexers.foxpro', 'pygments.lexers.freefem', 'pygments.lexers.functional', 'pygments.lexers.futhark', 'pygments.lexers.gcodelexer', 'pygments.lexers.gdscript', 'pygments.lexers.go', 'pygments.lexers.grammar_notation', 'pygments.lexers.graph', 'pygments.lexers.graphics', 'pygments.lexers.graphviz', 'pygments.lexers.gsql', 'pygments.lexers.haskell', 'pygments.lexers.haxe', 'pygments.lexers.hdl', 'pygments.lexers.hexdump', 'pygments.lexers.html', 'pygments.lexers.idl', 'pygments.lexers.igor', 'pygments.lexers.inferno', 'pygments.lexers.installers', 'pygments.lexers.int_fiction', 'pygments.lexers.iolang', 'pygments.lexers.j', 'pygments.lexers.javascript', 'pygments.lexers.jmespath', 'pygments.lexers.jslt', 'pygments.lexers.julia', 'pygments.lexers.jvm', 'pygments.lexers.kuin', 'pygments.lexers.lilypond', 'pygments.lexers.lisp', 'pygments.lexers.macaulay2', 'pygments.lexers.make', 'pygments.lexers.markup', 'pygments.lexers.math', 'pygments.lexers.matlab', 'pygments.lexers.maxima', 'pygments.lexers.mcfunction', 'pygments.lexers.meson', 'pygments.lexers.mime', 'pygments.lexers.ml', 'pygments.lexers.modeling', 'pygments.lexers.modula2', 'pygments.lexers.monte', 'pygments.lexers.mosel', 'pygments.lexers.ncl', 'pygments.lexers.nimrod', 'pygments.lexers.nit', 'pygments.lexers.nix', 'pygments.lexers.oberon', 'pygments.lexers.objective', 'pygments.lexers.ooc', 'pygments.lexers.other', 'pygments.lexers.parasail', 'pygments.lexers.parsers', 'pygments.lexers.pascal', 'pygments.lexers.pawn', 'pygments.lexers.perl', 'pygments.lexers.php', 'pygments.lexers.pointless', 'pygments.lexers.pony', 'pygments.lexers.praat', 'pygments.lexers.procfile', 'pygments.lexers.prolog', 'pygments.lexers.promql', 'pygments.lexers.python', 'pygments.lexers.q', 'pygments.lexers.qlik', 'pygments.lexers.qvt', 'pygments.lexers.r', 'pygments.lexers.rdf', 'pygments.lexers.rebol', 'pygments.lexers.resource', 'pygments.lexers.ride', 'pygments.lexers.rita', 'pygments.lexers.rnc', 'pygments.lexers.roboconf', 'pygments.lexers.robotframework', 'pygments.lexers.ruby', 'pygments.lexers.rust', 'pygments.lexers.sas', 'pygments.lexers.savi', 'pygments.lexers.scdoc', 'pygments.lexers.scripting', 'pygments.lexers.sgf', 'pygments.lexers.shell', 'pygments.lexers.sieve', 'pygments.lexers.slash', 'pygments.lexers.smalltalk', 'pygments.lexers.smithy', 'pygments.lexers.smv', 'pygments.lexers.snobol', 'pygments.lexers.solidity', 'pygments.lexers.sophia', 'pygments.lexers.special', 'pygments.lexers.spice', 'pygments.lexers.sql', 'pygments.lexers.srcinfo', 'pygments.lexers.stata', 'pygments.lexers.supercollider', 'pygments.lexers.tal', 'pygments.lexers.tcl', 'pygments.lexers.teal', 'pygments.lexers.templates', 'pygments.lexers.teraterm', 'pygments.lexers.testing', 'pygments.lexers.text', 'pygments.lexers.textedit', 'pygments.lexers.textfmts', 'pygments.lexers.theorem', 'pygments.lexers.thingsdb', 'pygments.lexers.tnt', 'pygments.lexers.trafficscript', 'pygments.lexers.typoscript', 'pygments.lexers.ul4', 'pygments.lexers.unicon', 'pygments.lexers.urbi', 'pygments.lexers.usd', 'pygments.lexers.varnish', 'pygments.lexers.verification', 'pygments.lexers.web', 'pygments.lexers.webassembly', 'pygments.lexers.webidl', 'pygments.lexers.webmisc', 'pygments.lexers.whiley', 'pygments.lexers.x10', 'pygments.lexers.xorg', 'pygments.lexers.yang', 'pygments.lexers.zig'] 95312 DEBUG: Collecting submodules for pygments.styles 95862 DEBUG: collect_submodules - found submodules: ['pygments.styles', 'pygments.styles.abap', 'pygments.styles.algol', 'pygments.styles.algol_nu', 'pygments.styles.arduino', 'pygments.styles.autumn', 'pygments.styles.borland', 'pygments.styles.bw', 'pygments.styles.colorful', 'pygments.styles.default', 'pygments.styles.dracula', 'pygments.styles.emacs', 'pygments.styles.friendly', 'pygments.styles.friendly_grayscale', 'pygments.styles.fruity', 'pygments.styles.gh_dark', 'pygments.styles.gruvbox', 'pygments.styles.igor', 'pygments.styles.inkpot', 'pygments.styles.lilypond', 'pygments.styles.lovelace', 'pygments.styles.manni', 'pygments.styles.material', 'pygments.styles.monokai', 'pygments.styles.murphy', 'pygments.styles.native', 'pygments.styles.nord', 'pygments.styles.onedark', 'pygments.styles.paraiso_dark', 'pygments.styles.paraiso_light', 'pygments.styles.pastie', 'pygments.styles.perldoc', 'pygments.styles.rainbow_dash', 'pygments.styles.rrt', 'pygments.styles.sas', 'pygments.styles.solarized', 'pygments.styles.staroffice', 'pygments.styles.stata_dark', 'pygments.styles.stata_light', 'pygments.styles.tango', 'pygments.styles.trac', 'pygments.styles.vim', 'pygments.styles.vs', 'pygments.styles.xcode', 'pygments.styles.zenburn'] 96225 INFO: Loading module hook 'hook-pkg_resources.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 96341 DEBUG: Collecting submodules for pkg_resources._vendor 97240 DEBUG: collect_submodules - found submodules: ['pkg_resources._vendor', 'pkg_resources._vendor.importlib_resources', 'pkg_resources._vendor.importlib_resources._adapters', 'pkg_resources._vendor.importlib_resources._common', 'pkg_resources._vendor.importlib_resources._compat', 'pkg_resources._vendor.importlib_resources._itertools', 'pkg_resources._vendor.importlib_resources._legacy', 'pkg_resources._vendor.importlib_resources.abc', 'pkg_resources._vendor.importlib_resources.readers', 'pkg_resources._vendor.importlib_resources.simple', 'pkg_resources._vendor.jaraco', 'pkg_resources._vendor.jaraco.context', 'pkg_resources._vendor.jaraco.functools', 'pkg_resources._vendor.jaraco.text', 'pkg_resources._vendor.more_itertools', 'pkg_resources._vendor.more_itertools.more', 'pkg_resources._vendor.more_itertools.recipes', 'pkg_resources._vendor.packaging', 'pkg_resources._vendor.packaging._elffile', 'pkg_resources._vendor.packaging._manylinux', 'pkg_resources._vendor.packaging._musllinux', 'pkg_resources._vendor.packaging._parser', 'pkg_resources._vendor.packaging._structures', 'pkg_resources._vendor.packaging._tokenizer', 'pkg_resources._vendor.packaging.markers', 'pkg_resources._vendor.packaging.metadata', 'pkg_resources._vendor.packaging.requirements', 'pkg_resources._vendor.packaging.specifiers', 'pkg_resources._vendor.packaging.tags', 'pkg_resources._vendor.packaging.utils', 'pkg_resources._vendor.packaging.version', 'pkg_resources._vendor.platformdirs', 'pkg_resources._vendor.platformdirs.__main__', 'pkg_resources._vendor.platformdirs.android', 'pkg_resources._vendor.platformdirs.api', 'pkg_resources._vendor.platformdirs.macos', 'pkg_resources._vendor.platformdirs.unix', 'pkg_resources._vendor.platformdirs.version', 'pkg_resources._vendor.platformdirs.windows', 'pkg_resources._vendor.typing_extensions', 'pkg_resources._vendor.zipp'] 97259 DEBUG: Collecting submodules for packaging 97674 DEBUG: collect_submodules - found submodules: ['packaging', 'packaging.__about__', 'packaging._manylinux', 'packaging._musllinux', 'packaging._structures', 'packaging.markers', 'packaging.requirements', 'packaging.specifiers', 'packaging.tags', 'packaging.utils', 'packaging.version'] 97857 DEBUG: Suppressing import of '__main__' from module 'pkg_resources' due to excluded import '__main__' specified in a hook for 'pkg_resources' (or its parent package(s)). 99413 INFO: Loading module hook 'hook-PyQt5.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 100950 INFO: Loading module hook 'hook-openpyxl.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 100999 DEBUG: Collecting data files for openpyxl 101208 DEBUG: collect_data_files - Found files: [] 101261 INFO: Loading module hook 'hook-lxml.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 101268 DEBUG: Collecting submodules for lxml 101974 DEBUG: collect_submodules - found submodules: ['lxml', 'lxml.ElementInclude', 'lxml._elementpath', 'lxml.builder', 'lxml.cssselect', 'lxml.doctestcompare', 'lxml.etree', 'lxml.html', 'lxml.html.ElementSoup', 'lxml.html._diffcommand', 'lxml.html._html5builder', 'lxml.html._setmixin', 'lxml.html.builder', 'lxml.html.clean', 'lxml.html.defs', 'lxml.html.diff', 'lxml.html.formfill', 'lxml.html.html5parser', 'lxml.html.soupparser', 'lxml.html.usedoctest', 'lxml.includes', 'lxml.includes.extlibs', 'lxml.includes.libexslt', 'lxml.includes.libxml', 'lxml.includes.libxslt', 'lxml.isoschematron', 'lxml.objectify', 'lxml.pyclasslookup', 'lxml.sax', 'lxml.usedoctest'] 103191 INFO: Loading module hook 'hook-PIL.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 103331 INFO: Loading module hook 'hook-PIL.Image.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 103347 DEBUG: Collecting submodules for PIL 103763 DEBUG: collect_submodules - found submodules: ['PIL.BlpImagePlugin', 'PIL.BmpImagePlugin', 'PIL.BufrStubImagePlugin', 'PIL.CurImagePlugin', 'PIL.DcxImagePlugin', 'PIL.DdsImagePlugin', 'PIL.EpsImagePlugin', 'PIL.FitsImagePlugin', 'PIL.FitsStubImagePlugin', 'PIL.FliImagePlugin', 'PIL.FpxImagePlugin', 'PIL.FtexImagePlugin', 'PIL.GbrImagePlugin', 'PIL.GifImagePlugin', 'PIL.GribStubImagePlugin', 'PIL.Hdf5StubImagePlugin', 'PIL.IcnsImagePlugin', 'PIL.IcoImagePlugin', 'PIL.ImImagePlugin', 'PIL.ImtImagePlugin', 'PIL.IptcImagePlugin', 'PIL.Jpeg2KImagePlugin', 'PIL.JpegImagePlugin', 'PIL.McIdasImagePlugin', 'PIL.MicImagePlugin', 'PIL.MpegImagePlugin', 'PIL.MpoImagePlugin', 'PIL.MspImagePlugin', 'PIL.PalmImagePlugin', 'PIL.PcdImagePlugin', 'PIL.PcxImagePlugin', 'PIL.PdfImagePlugin', 'PIL.PixarImagePlugin', 'PIL.PngImagePlugin', 'PIL.PpmImagePlugin', 'PIL.PsdImagePlugin', 'PIL.SgiImagePlugin', 'PIL.SpiderImagePlugin', 'PIL.SunImagePlugin', 'PIL.TgaImagePlugin', 'PIL.TiffImagePlugin', 'PIL.WebPImagePlugin', 'PIL.WmfImagePlugin', 'PIL.XVThumbImagePlugin', 'PIL.XbmImagePlugin', 'PIL.XpmImagePlugin'] 104336 INFO: Loading module hook 'hook-pycparser.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 105497 INFO: Loading module hook 'hook-distutils.util.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 105572 DEBUG: Suppressing import of 'lib2to3.refactor' from module 'distutils.util' due to excluded import 'lib2to3.refactor' specified in a hook for 'distutils.util' (or its parent package(s)). 106714 INFO: Loading module hook 'hook-setuptools.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 106786 DEBUG: Collecting submodules for setuptools._vendor 108651 DEBUG: collect_submodules - found submodules: ['setuptools._vendor', 'setuptools._vendor.importlib_metadata', 'setuptools._vendor.importlib_metadata._adapters', 'setuptools._vendor.importlib_metadata._collections', 'setuptools._vendor.importlib_metadata._compat', 'setuptools._vendor.importlib_metadata._functools', 'setuptools._vendor.importlib_metadata._itertools', 'setuptools._vendor.importlib_metadata._meta', 'setuptools._vendor.importlib_metadata._py39compat', 'setuptools._vendor.importlib_metadata._text', 'setuptools._vendor.importlib_resources', 'setuptools._vendor.importlib_resources._adapters', 'setuptools._vendor.importlib_resources._common', 'setuptools._vendor.importlib_resources._compat', 'setuptools._vendor.importlib_resources._itertools', 'setuptools._vendor.importlib_resources._legacy', 'setuptools._vendor.importlib_resources.abc', 'setuptools._vendor.importlib_resources.readers', 'setuptools._vendor.importlib_resources.simple', 'setuptools._vendor.jaraco', 'setuptools._vendor.jaraco.context', 'setuptools._vendor.jaraco.functools', 'setuptools._vendor.jaraco.text', 'setuptools._vendor.more_itertools', 'setuptools._vendor.more_itertools.more', 'setuptools._vendor.more_itertools.recipes', 'setuptools._vendor.ordered_set', 'setuptools._vendor.packaging', 'setuptools._vendor.packaging._elffile', 'setuptools._vendor.packaging._manylinux', 'setuptools._vendor.packaging._musllinux', 'setuptools._vendor.packaging._parser', 'setuptools._vendor.packaging._structures', 'setuptools._vendor.packaging._tokenizer', 'setuptools._vendor.packaging.markers', 'setuptools._vendor.packaging.metadata', 'setuptools._vendor.packaging.requirements', 'setuptools._vendor.packaging.specifiers', 'setuptools._vendor.packaging.tags', 'setuptools._vendor.packaging.utils', 'setuptools._vendor.packaging.version', 'setuptools._vendor.tomli', 'setuptools._vendor.tomli._parser', 'setuptools._vendor.tomli._re', 'setuptools._vendor.tomli._types', 'setuptools._vendor.typing_extensions', 'setuptools._vendor.zipp'] 108670 DEBUG: Collecting submodules for setuptools._distutils 109522 DEBUG: collect_submodules - found submodules: ['setuptools._distutils', 'setuptools._distutils._collections', 'setuptools._distutils._functools', 'setuptools._distutils._log', 'setuptools._distutils._macos_compat', 'setuptools._distutils._msvccompiler', 'setuptools._distutils.archive_util', 'setuptools._distutils.bcppcompiler', 'setuptools._distutils.ccompiler', 'setuptools._distutils.cmd', 'setuptools._distutils.command', 'setuptools._distutils.command._framework_compat', 'setuptools._distutils.command.bdist', 'setuptools._distutils.command.bdist_dumb', 'setuptools._distutils.command.bdist_rpm', 'setuptools._distutils.command.build', 'setuptools._distutils.command.build_clib', 'setuptools._distutils.command.build_ext', 'setuptools._distutils.command.build_py', 'setuptools._distutils.command.build_scripts', 'setuptools._distutils.command.check', 'setuptools._distutils.command.clean', 'setuptools._distutils.command.config', 'setuptools._distutils.command.install', 'setuptools._distutils.command.install_data', 'setuptools._distutils.command.install_egg_info', 'setuptools._distutils.command.install_headers', 'setuptools._distutils.command.install_lib', 'setuptools._distutils.command.install_scripts', 'setuptools._distutils.command.py37compat', 'setuptools._distutils.command.register', 'setuptools._distutils.command.sdist', 'setuptools._distutils.command.upload', 'setuptools._distutils.config', 'setuptools._distutils.core', 'setuptools._distutils.cygwinccompiler', 'setuptools._distutils.debug', 'setuptools._distutils.dep_util', 'setuptools._distutils.dir_util', 'setuptools._distutils.dist', 'setuptools._distutils.errors', 'setuptools._distutils.extension', 'setuptools._distutils.fancy_getopt', 'setuptools._distutils.file_util', 'setuptools._distutils.filelist', 'setuptools._distutils.log', 'setuptools._distutils.msvc9compiler', 'setuptools._distutils.msvccompiler', 'setuptools._distutils.py38compat', 'setuptools._distutils.py39compat', 'setuptools._distutils.spawn', 'setuptools._distutils.sysconfig', 'setuptools._distutils.text_file', 'setuptools._distutils.unixccompiler', 'setuptools._distutils.util', 'setuptools._distutils.version', 'setuptools._distutils.versionpredicate'] 110638 INFO: Loading module hook 'hook-packaging.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 113616 INFO: Loading module hook 'hook-jinja2.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 114336 INFO: Loading module hook 'hook-multiprocessing.util.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 114352 DEBUG: Suppressing import of 'test' from module 'multiprocessing.util' due to excluded import 'test' specified in a hook for 'multiprocessing.util' (or its parent package(s)). 117680 INFO: Loading module hook 'hook-PIL.ImageFilter.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 117692 DEBUG: Suppressing import of 'numpy' from module 'PIL.ImageFilter' due to excluded import 'numpy' specified in a hook for 'PIL.ImageFilter' (or its parent package(s)). 117710 DEBUG: Suppressing import of 'PyQt6.QtCore' from module 'PIL.ImageQt' due to excluded import 'PyQt6' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117722 DEBUG: Suppressing import of 'PyQt6.QtGui' from module 'PIL.ImageQt' due to excluded import 'PyQt6' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117726 DEBUG: Suppressing import of 'PySide6.QtCore' from module 'PIL.ImageQt' due to excluded import 'PySide6' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117737 DEBUG: Suppressing import of 'PySide6.QtGui' from module 'PIL.ImageQt' due to excluded import 'PySide6' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117749 DEBUG: Suppressing import of 'PyQt5.QtCore' from module 'PIL.ImageQt' due to excluded import 'PyQt5' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117766 DEBUG: Suppressing import of 'PyQt5.QtGui' from module 'PIL.ImageQt' due to excluded import 'PyQt5' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117783 DEBUG: Suppressing import of 'PySide2.QtCore' from module 'PIL.ImageQt' due to excluded import 'PySide2' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117789 DEBUG: Suppressing import of 'PySide2.QtGui' from module 'PIL.ImageQt' due to excluded import 'PySide2' specified in a hook for 'PIL.ImageQt' (or its parent package(s)). 117807 DEBUG: Suppressing import of 'IPython.display' from module 'PIL.ImageShow' due to excluded import 'IPython' specified in a hook for 'PIL.ImageShow' (or its parent package(s)). 118759 INFO: Loading module hook 'hook-pythoncom.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 119035 INFO: Loading module hook 'hook-pywintypes.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 119164 INFO: Processing pre-safe import module hook win32com from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\pre_safe_import_module\\hook-win32com.py'. 119373 DEBUG: win32com: extending __path__ with dir 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\win32comext' 119406 INFO: Loading module hook 'hook-win32com.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 120157 INFO: Loading module hook 'hook-Crypto.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 122972 INFO: Loading module hook 'hook-xml.dom.domreg.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 124290 INFO: Processing pre-safe import module hook urllib3.packages.six.moves from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\pre_saf e_import_module\\hook-urllib3.packages.six.moves.py'. 125904 INFO: Loading module hook 'hook-certifi.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 125932 DEBUG: Collecting data files for certifi 125946 DEBUG: collect_data_files - Found files: [('D:\\work\\Python\\cfepy310\\lib\\site-packages\\certifi\\cacert.pem', 'certifi'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\certifi\\py.typed', 'certifi')] 126399 INFO: Processing module hooks... 126421 INFO: Loading module hook 'hook-lxml.etree.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 126586 INFO: Loading module hook 'hook-difflib.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 126605 DEBUG: Suppressing import of 'doctest' from module 'difflib' due to excluded import 'doctest' specified in a hook for 'difflib' (or its parent package(s)). 127223 INFO: Loading module hook 'hook-lxml.isoschematron.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 127247 DEBUG: Collecting data files for lxml 127270 DEBUG: collect_data_files - Found files: [('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\reso urces\\xsl\\iso-schematron-xslt1\\iso_schematron_skeleton_for_xslt1.xsl', 'lxml\\isoschematron\\resources\\xsl\\iso-schematron-xslt1'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\xsl\\iso-schematron-xslt1\\iso_abstract_expand.xsl', 'lxml\\isoschematron\\resources\\xsl\\iso-schematron-xslt1'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\xsl\\iso-schematron-xslt1\\readme.txt', 'lxml\\isoschematron\\resources\\xsl\\iso-schematron-xslt1'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\xsl\\iso-schematron-xslt1\\iso_dsdl_include.xsl', 'lxml\\isoschematron\\resources\\xsl\\iso-schematron-xslt1'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\xsl\\iso-schematron-xslt1\\iso_svrl_for_xslt1.xsl', 'lxml\\isoschematron\\resources\\xsl\\iso-schematron-xslt1'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\xsl\\XSD2Schtrn.xsl', 'lxml\\isoschematron\\resources\\xsl'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\xsl\\RNG2Schtrn.xsl', 'lxml\\isoschematron\\resources\\xsl'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\rng\\iso-schematron.rng', 'lxml\\isoschematron\\resources\\rng'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\isoschematron\\resou rces\\xsl\\iso-schematron-xslt1\\iso_schematron_message.xsl', 'lxml\\isoschematron\\resources\\xsl\\iso-schematron-xslt1')] 127999 INFO: Loading module hook 'hook-PIL.SpiderImagePlugin.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 128029 DEBUG: Suppressing import of 'tkinter' from module 'PIL.ImageTk' due to excluded import 'tkinter' specified in a hook for 'PIL.ImageTk' (or its parent package(s)). 138434 WARNING: Hidden import "sip" not found! 138464 INFO: Loading module hook 'hook-PyQt5.QtCore.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 138555 DEBUG: QtLibraryInfo(PyQt5): processing module PyQt5.QtCore... 138780 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' -> parsed name 'vcruntime140'. 138803 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-runtime-l1-1-0.dll' 138822 DEBUG: QtLibraryInfo(PyQt5): imported library 'python3.dll', full path 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' -> parsed name 'python3'. 138839 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Core.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' -> parsed name 'qt5core'. 138855 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5core'. 139422 DEBUG: QtLibraryInfo(PyQt5): imported library 'ole32.dll', full path 'C:\\Windows\\system32\\ole32.dll' -> parsed name 'ole32'. 139453 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-environment-l1-1-0.dll' 139474 DEBUG: QtLibraryInfo(PyQt5): imported library 'KERNEL32.dll', full path 'C:\\Windows\\system32\\KERNEL32.dll' -> parsed name 'kernel32'. 139490 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-math-l1-1-0.dll' 139505 DEBUG: QtLibraryInfo(PyQt5): imported library 'SHELL32.dll', full path 'C:\\Windows\\system32\\SHELL32.dll' -> parsed name 'shell32'. 139526 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-time-l1-1-0.dll' 139542 DEBUG: QtLibraryInfo(PyQt5): imported library 'WS2_32.dll', full path 'C:\\Windows\\system32\\WS2_32.dll' -> parsed name 'ws2_32'. 139559 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-string-l1-1-0.dll' 139576 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-stdio-l1-1-0.dll' 139593 DEBUG: QtLibraryInfo(PyQt5): imported library 'NETAPI32.dll', full path 'C:\\Windows\\system32\\NETAPI32.dll' -> parsed name 'netapi32'. 139609 DEBUG: QtLibraryInfo(PyQt5): imported library 'ADVAPI32.dll', full path 'C:\\Windows\\system32\\ADVAPI32.dll' -> parsed name 'advapi32'. 139611 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-runtime-l1-1-0.dll' 139626 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' -> parsed name 'vcruntime140'. 139644 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140_1.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' -> parsed name 'vcruntime140_1'. 139660 DEBUG: QtLibraryInfo(PyQt5): imported library 'WINMM.dll', full path 'C:\\Windows\\system32\\WINMM.dll' -> parsed name 'winmm'. 139675 DEBUG: QtLibraryInfo(PyQt5): imported library 'MPR.dll', full path 'C:\\Windows\\system32\\MPR.dll' -> parsed name 'mpr'. 139693 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-convert-l1-1-0.dll' 139694 DEBUG: QtLibraryInfo(PyQt5): imported library 'MSVCP140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' -> parsed name 'msvcp140'. 139716 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-filesystem-l1-1-0.dll' 139730 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-heap-l1-1-0.dll' 139745 DEBUG: QtLibraryInfo(PyQt5): imported library 'USER32.dll', full path 'C:\\Windows\\system32\\USER32.dll' -> parsed name 'user32'. 139760 DEBUG: QtLibraryInfo(PyQt5): imported library 'MSVCP140_1.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140_1 .dll' -> parsed name 'msvcp140_1'. 139760 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-utility-l1-1-0.dll' 139783 DEBUG: QtLibraryInfo(PyQt5): imported library 'VERSION.dll', full path 'C:\\Windows\\system32\\VERSION.dll' -> parsed name 'version'. 139798 DEBUG: QtLibraryInfo(PyQt5): imported library 'USERENV.dll', full path 'C:\\Windows\\system32\\USERENV.dll' -> parsed name 'userenv'. 139919 DEBUG: QtLibraryInfo(PyQt5): dependencies for PyQt5.QtCore: hiddenimports = [] binaries = [] datas = [('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_ar.q m', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_bg.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_ca.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_cs.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_da.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_de.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_en.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_es.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_fa.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_fi.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_fr.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_gd.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_gl.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_he.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ ar.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ bg.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ ca.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ cs.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ da.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ de.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ en.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ es.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ fr.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ gl.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ hu.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ it.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ ja.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ ko.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ pl.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ ru.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ sk.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ sl.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ tr.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ uk.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ zh_CN.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_help_ zh_TW.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_hu.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_it.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_ja.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_ko.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_lt.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_lv.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_pl.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_pt.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_ru.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_sk.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_sl.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_sv.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_tr.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_uk.qm ', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_zh_CN .qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qt_zh_TW .qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_a r.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_b g.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_c a.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_c s.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_d a.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_d e.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_e n.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_e s.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_f i.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_f r.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_g d.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_h e.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_h u.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_i t.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_j a.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_k o.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_l v.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_p l.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_r u.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_s k.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_t r.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_u k.qm', 'PyQt5\\Qt5\\translations'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/translations\\qtbase_z h_TW.qm', 'PyQt5\\Qt5\\translations')] 139974 INFO: Loading module hook 'hook-PyQt5.QtGui.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 140036 DEBUG: QtLibraryInfo(PyQt5): processing module PyQt5.QtGui... 140151 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' -> parsed name 'vcruntime140'. 140167 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Gui.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' -> parsed name 'qt5gui'. 140188 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5gui'. 140428 DEBUG: QtLibraryInfo(PyQt5): imported library 'dxgi.dll', full path 'C:\\Windows\\system32\\dxgi.dll' -> parsed name 'dxgi'. 140442 DEBUG: QtLibraryInfo(PyQt5): imported library 'python3.dll', full path 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' -> parsed name 'python3'. 140463 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-locale-l1-1-0.dll' 140478 DEBUG: QtLibraryInfo(PyQt5): imported library 'ole32.dll', full path 'C:\\Windows\\system32\\ole32.dll' -> parsed name 'ole32'. 140496 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-environment-l1-1-0.dll' 140512 DEBUG: QtLibraryInfo(PyQt5): imported library 'KERNEL32.dll', full path 'C:\\Windows\\system32\\KERNEL32.dll' -> parsed name 'kernel32'. 140530 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-math-l1-1-0.dll' 140547 DEBUG: QtLibraryInfo(PyQt5): imported library 'GDI32.dll', full path 'C:\\Windows\\system32\\GDI32.dll' -> parsed name 'gdi32'. 140564 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-string-l1-1-0.dll' 140576 DEBUG: QtLibraryInfo(PyQt5): imported library 'd3d11.dll', full path 'C:\\Windows\\system32\\d3d11.dll' -> parsed name 'd3d11'. 140600 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-stdio-l1-1-0.dll' 140622 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-runtime-l1-1-0.dll' 140641 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' -> parsed name 'vcruntime140'. 140641 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140_1.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' -> parsed name 'vcruntime140_1'. 140669 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Core.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' -> parsed name 'qt5core'. 140684 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5core'. 140704 DEBUG: QtLibraryInfo(PyQt5): imported library 'MSVCP140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' -> parsed name 'msvcp140'. 140720 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-heap-l1-1-0.dll' 140724 DEBUG: QtLibraryInfo(PyQt5): imported library 'USER32.dll', full path 'C:\\Windows\\system32\\USER32.dll' -> parsed name 'user32'. 140755 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-utility-l1-1-0.dll' 140756 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'imageformats': ['D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qgif.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qicns.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qico.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qjpeg.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qsvg.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qtga.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qtiff.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qwbmp.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\\ qwebp.dll'] 140788 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'platforms/darwin': [] 140805 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'wayland-shell-integration': [] 140821 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'accessiblebridge': [] 140823 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'iconengines': ['D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\iconengines\\ qsvgicon.dll'] 140855 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'wayland-graphics-integration-client': [] 140872 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'platforminputcontexts': [] 140883 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'platformthemes': ['D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platformtheme s\\qxdgdesktopportal.dll'] 140906 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'wayland-decoration-client': [] 140906 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'egldeviceintegrations': [] 140930 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'platforms': ['D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qm inimal.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qof fscreen.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qwe bgl.dll', 'D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qwi ndows.dll'] 140945 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'xcbglintegrations': [] 140967 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'generic': ['D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\generic\\qtui otouchplugin.dll'] 140980 DEBUG: QtLibraryInfo(PyQt5): dependencies for PyQt5.QtGui: hiddenimports = ['PyQt5.QtCore'] binaries = [('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats \\qgif.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qicns.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qico.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qjpeg.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qsvg.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qtga.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qtiff.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qwbmp.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\imageformats\ \qwebp.dll', 'PyQt5\\Qt5\\plugins\\imageformats'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\iconengines\\ qsvgicon.dll', 'PyQt5\\Qt5\\plugins\\iconengines'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platformtheme s\\qxdgdesktopportal.dll', 'PyQt5\\Qt5\\plugins\\platformthemes'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qm inimal.dll', 'PyQt5\\Qt5\\plugins\\platforms'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qo ffscreen.dll', 'PyQt5\\Qt5\\plugins\\platforms'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qw ebgl.dll', 'PyQt5\\Qt5\\plugins\\platforms'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\platforms\\qw indows.dll', 'PyQt5\\Qt5\\plugins\\platforms'), ('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\generic\\qtui otouchplugin.dll', 'PyQt5\\Qt5\\plugins\\generic')] datas = [] 141003 INFO: Loading module hook 'hook-PyQt5.QtWidgets.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 141041 DEBUG: QtLibraryInfo(PyQt5): processing module PyQt5.QtWidgets... 141169 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' -> parsed name 'vcruntime140'. 141198 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Gui.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' -> parsed name 'qt5gui'. 141208 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5gui'. 141243 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-runtime-l1-1-0.dll' 141243 DEBUG: QtLibraryInfo(PyQt5): imported library 'python3.dll', full path 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' -> parsed name 'python3'. 141267 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Core.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' -> parsed name 'qt5core'. 141290 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5core'. 141290 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Widgets.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' -> parsed name 'qt5widgets'. 141314 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5widgets'. 142091 DEBUG: QtLibraryInfo(PyQt5): imported library 'KERNEL32.dll', full path 'C:\\Windows\\system32\\KERNEL32.dll' -> parsed name 'kernel32'. 142124 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-math-l1-1-0.dll' 142142 DEBUG: QtLibraryInfo(PyQt5): imported library 'SHELL32.dll', full path 'C:\\Windows\\system32\\SHELL32.dll' -> parsed name 'shell32'. 142159 DEBUG: QtLibraryInfo(PyQt5): imported library 'GDI32.dll', full path 'C:\\Windows\\system32\\GDI32.dll' -> parsed name 'gdi32'. 142178 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-string-l1-1-0.dll' 142190 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' -> parsed name 'vcruntime140'. 142212 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-runtime-l1-1-0.dll' 142228 DEBUG: QtLibraryInfo(PyQt5): imported library 'VCRUNTIME140_1.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' -> parsed name 'vcruntime140_1'. 142246 DEBUG: QtLibraryInfo(PyQt5): imported library 'dwmapi.dll', full path 'C:\\Windows\\system32\\dwmapi.dll' -> parsed name 'dwmapi'. 142277 DEBUG: QtLibraryInfo(PyQt5): imported library 'UxTheme.dll', full path 'C:\\Windows\\system32\\UxTheme.dll' -> parsed name 'uxtheme'. 142292 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Core.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' -> parsed name 'qt5core'. 142296 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5core'. 142328 DEBUG: QtLibraryInfo(PyQt5): imported library 'MSVCP140.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' -> parsed name 'msvcp140'. 142344 DEBUG: QtLibraryInfo(PyQt5): ignoring unresolved library import 'api-ms-win-crt-heap-l1-1-0.dll' 142363 DEBUG: QtLibraryInfo(PyQt5): imported library 'USER32.dll', full path 'C:\\Windows\\system32\\USER32.dll' -> parsed name 'user32'. 142378 DEBUG: QtLibraryInfo(PyQt5): imported library 'MSVCP140_1.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140_1 .dll' -> parsed name 'msvcp140_1'. 142400 DEBUG: QtLibraryInfo(PyQt5): imported library 'Qt5Gui.dll', full path 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' -> parsed name 'qt5gui'. 142412 DEBUG: QtLibraryInfo(PyQt5): collecting Qt module associated with 'qt5gui'. 142430 DEBUG: QtLibraryInfo(PyQt5): imported library 'ole32.dll', full path 'C:\\Windows\\system32\\ole32.dll' -> parsed name 'ole32'. 142452 DEBUG: QtLibraryInfo(PyQt5): found plugin files for plugin type 'styles': ['D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\styles\\qwind owsvistastyle.dll'] 142467 DEBUG: QtLibraryInfo(PyQt5): dependencies for PyQt5.QtWidgets: hiddenimports = ['PyQt5.QtCore', 'PyQt5.QtGui'] binaries = [('D:/work/Python/cfepy310/lib/site-packages/PyQt5/Qt5/plugins\\styles\\qwin dowsvistastyle.dll', 'PyQt5\\Qt5\\plugins\\styles')] datas = [] 142526 INFO: Loading module hook 'hook-setuptools.msvc.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 143858 INFO: Loading module hook 'hook-docutils.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 143976 DEBUG: Collecting submodules for docutils.languages 145091 DEBUG: collect_submodules - found submodules: ['docutils.languages', 'docutils.languages.af', 'docutils.languages.ar', 'docutils.languages.ca', 'docutils.languages.cs', 'docutils.languages.da', 'docutils.languages.de', 'docutils.languages.en', 'docutils.languages.eo', 'docutils.languages.es', 'docutils.languages.fa', 'docutils.languages.fi', 'docutils.languages.fr', 'docutils.languages.gl', 'docutils.languages.he', 'docutils.languages.it', 'docutils.languages.ja', 'docutils.languages.ko', 'docutils.languages.lt', 'docutils.languages.lv', 'docutils.languages.nl', 'docutils.languages.pl', 'docutils.languages.pt_br', 'docutils.languages.ru', 'docutils.languages.sk', 'docutils.languages.sv', 'docutils.languages.zh_cn', 'docutils.languages.zh_tw'] 145113 DEBUG: Collecting submodules for docutils.writers 148193 DEBUG: collect_submodules - found submodules: ['docutils.writers', 'docutils.writers._html_base', 'docutils.writers.docutils_xml', 'docutils.writers.html4css1', 'docutils.writers.html5_polyglot', 'docutils.writers.latex2e', 'docutils.writers.manpage', 'docutils.writers.null', 'docutils.writers.odf_odt', 'docutils.writers.odf_odt.pygmentsformatter', 'docutils.writers.pep_html', 'docutils.writers.pseudoxml', 'docutils.writers.s5_html', 'docutils.writers.xetex'] 148212 DEBUG: Collecting submodules for docutils.parsers.rst.languages 148781 DEBUG: collect_submodules - found submodules: ['docutils.parsers.rst.languages', 'docutils.parsers.rst.languages.af', 'docutils.parsers.rst.languages.ar', 'docutils.parsers.rst.languages.ca', 'docutils.parsers.rst.languages.cs', 'docutils.parsers.rst.languages.da', 'docutils.parsers.rst.languages.de', 'docutils.parsers.rst.languages.en', 'docutils.parsers.rst.languages.eo', 'docutils.parsers.rst.languages.es', 'docutils.parsers.rst.languages.fa', 'docutils.parsers.rst.languages.fi', 'docutils.parsers.rst.languages.fr', 'docutils.parsers.rst.languages.gl', 'docutils.parsers.rst.languages.he', 'docutils.parsers.rst.languages.it', 'docutils.parsers.rst.languages.ja', 'docutils.parsers.rst.languages.ko', 'docutils.parsers.rst.languages.lt', 'docutils.parsers.rst.languages.lv', 'docutils.parsers.rst.languages.nl', 'docutils.parsers.rst.languages.pl', 'docutils.parsers.rst.languages.pt_br', 'docutils.parsers.rst.languages.ru', 'docutils.parsers.rst.languages.sk', 'docutils.parsers.rst.languages.sv', 'docutils.parsers.rst.languages.zh_cn', 'docutils.parsers.rst.languages.zh_tw'] 148800 DEBUG: Collecting submodules for docutils.parsers.rst.directives 149365 DEBUG: collect_submodules - found submodules: ['docutils.parsers.rst.directives', 'docutils.parsers.rst.directives.admonitions', 'docutils.parsers.rst.directives.body', 'docutils.parsers.rst.directives.html', 'docutils.parsers.rst.directives.images', 'docutils.parsers.rst.directives.misc', 'docutils.parsers.rst.directives.parts', 'docutils.parsers.rst.directives.references', 'docutils.parsers.rst.directives.tables'] 149396 DEBUG: Collecting data files for docutils 149779 DEBUG: collect_data_files - Found files: [('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_htm l\\themes\\big-white\\pretty.css', 'docutils\\writers\\s5_html\\themes\\big-white'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\medium-black\\pretty.css', 'docutils\\writers\\s5_html\\themes\\medium-black'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\mmlextra-wide.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html5_p olyglot\\plain.css', 'docutils\\writers\\html5_polyglot'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isobox.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\big-white\\framing.css', 'docutils\\writers\\s5_html\\themes\\big-white'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\medium-white\\pretty.css', 'docutils\\writers\\s5_html\\themes\\medium-white'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\framing.css', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\pep_htm l\\pep.css', 'docutils\\writers\\pep_html'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isoamsc.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\small-black\\__base__', 'docutils\\writers\\s5_html\\themes\\small-black'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html5_p olyglot\\template.txt', 'docutils\\writers\\html5_polyglot'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isoamsa.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\latex2e \\titlepage.tex', 'docutils\\writers\\latex2e'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\big-black\\__base__', 'docutils\\writers\\s5_html\\themes\\big-black'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isoamsr.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html4cs s1\\template.txt', 'docutils\\writers\\html4css1'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\mmlalias.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\medium-white\\framing.css', 'docutils\\writers\\s5_html\\themes\\medium-white'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\pep_htm l\\template.txt', 'docutils\\writers\\pep_html'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\README.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\s5-core.css', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isomfrk.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isocyr2.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\latex2e \\default.tex', 'docutils\\writers\\latex2e'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isopub.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\latex2e \\docutils.sty', 'docutils\\writers\\latex2e'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\slides.js', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\README.txt', 'docutils\\writers\\s5_html\\themes'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isotech.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\xhtml1-special.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isomopf-wide.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isomscr-wide.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isoamso.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\slides.css', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isolat2.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\xhtml1-lat1.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isogrk1.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html4cs s1\\html4css1.css', 'docutils\\writers\\html4css1'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isolat1.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isocyr1.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html5_p olyglot\\responsive.css', 'docutils\\writers\\html5_polyglot'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\opera.css', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html5_p olyglot\\tuftig.css', 'docutils\\writers\\html5_polyglot'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\small-black\\pretty.css', 'docutils\\writers\\s5_html\\themes\\small-black'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\outline.css', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\big-black\\pretty.css', 'docutils\\writers\\s5_html\\themes\\big-black'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\small-white\\pretty.css', 'docutils\\writers\\s5_html\\themes\\small-white'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\mmlextra.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\xhtml1-symbol.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\latex2e \\titlingpage.tex', 'docutils\\writers\\latex2e'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\s5defs.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\medium-black\\__base__', 'docutils\\writers\\s5_html\\themes\\medium-black'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isogrk4-wide.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\big-black\\framing.css', 'docutils\\writers\\s5_html\\themes\\big-black'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isomopf.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isogrk4.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html5_p olyglot\\math.css', 'docutils\\writers\\html5_polyglot'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isogrk2.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isoamsb.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\pretty.css', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\html5_p olyglot\\minimal.css', 'docutils\\writers\\html5_polyglot'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isomfrk-wide.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isonum.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\odf_odt \\styles.odt', 'docutils\\writers\\odf_odt'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isomscr.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isoamsn.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isodia.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\parsers\\rst\\in clude\\isogrk3.txt', 'docutils\\parsers\\rst\\include'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\default\\print.css', 'docutils\\writers\\s5_html\\themes\\default'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\latex2e \\xelatex.tex', 'docutils\\writers\\latex2e'), ('D:\\work\\Python\\cfepy310\\lib\\site-packages\\docutils\\writers\\s5_html \\themes\\small-white\\framing.css', 'docutils\\writers\\s5_html\\themes\\small-white')] 151129 INFO: Loading module hook 'hook-_tkinter.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks'... 151324 INFO: checking Tree 151372 INFO: Building Tree because Tree-00.toc is non existent 151396 INFO: Building Tree Tree-00.toc 151484 INFO: checking Tree 151508 INFO: Building Tree because Tree-01.toc is non existent 151531 INFO: Building Tree Tree-01.toc 151555 INFO: checking Tree 151575 INFO: Building Tree because Tree-02.toc is non existent 151598 INFO: Building Tree Tree-02.toc 154246 INFO: Loading module hook 'hook-lxml.objectify.py' from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\stdhooks'... 162380 INFO: Looking for ctypes DLLs 162440 DEBUG: Scanning psutil._common for ctypes-based references to shared libraries 162473 DEBUG: Scanning psutil._pslinux for ctypes-based references to shared libraries 162499 DEBUG: Scanning colorama.win32 for ctypes-based references to shared libraries 162521 DEBUG: Scanning pyreadline3.clipboard.win32_clipboard for ctypes-based references to shared libraries 162544 DEBUG: Scanning pyreadline3.keysyms.keysyms for ctypes-based references to shared libraries 162564 DEBUG: Scanning pyreadline3.console.console for ctypes-based references to shared libraries 162589 DEBUG: Scanning multiprocessing.sharedctypes for ctypes-based references to shared libraries 162610 DEBUG: Scanning packaging._manylinux for ctypes-based references to shared libraries 162630 DEBUG: Scanning setuptools._vendor.packaging._manylinux for ctypes-based references to shared libraries 162652 DEBUG: Scanning setuptools.windows_support for ctypes-based references to shared libraries 162669 DEBUG: Scanning Crypto.Util._raw_api for ctypes-based references to shared libraries 162690 DEBUG: Scanning dateutil.tz.win for ctypes-based references to shared libraries 162715 DEBUG: Scanning pkg_resources._vendor.packaging._manylinux for ctypes-based references to shared libraries 162734 DEBUG: Scanning pkg_resources._vendor.platformdirs.windows for ctypes-based references to shared libraries 162762 INFO: Analyzing run-time hooks ... 162786 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth_inspect.py' 162834 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\rthooks\\pyi_rth_pywintypes.py' 162872 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth_pkgutil.py' 162896 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth_win32comgenpy.py' 162932 INFO: Processing pre-find module path hook _pyi_rth_utils from 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\pre_fin d_module_path\\hook-_pyi_rth_utils.py'. 162996 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_pyinstaller_hooks_contrib\ \hooks\\rthooks\\pyi_rth_pythoncom.py' 163020 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth_multiprocessing.py' 163046 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth_setuptools.py' 163074 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth_pkgres.py' 163100 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth__tkinter.py' 163136 INFO: Including run-time hook 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyInstaller\\hooks\\rthooks \\pyi_rth_pyqt5.py' 163196 DEBUG: Module collection settings: {} 196413 INFO: Looking for dynamic libraries 205384 INFO: Extra DLL search directories (AddDllDirectory): ['D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin'] 205424 INFO: Extra DLL search directories (PATH): ['D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin'] 205447 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 205615 DEBUG: Processing dependency, name: 'api-ms-win-crt-conio-l1-1-0.dll', resolved path: None 205637 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 205661 DEBUG: Processing dependency, name: 'VERSION.dll', resolved path: 'C:\\Windows\\system32\\VERSION.dll' 205682 DEBUG: Skipping dependency 'C:\\Windows\\system32\\VERSION.dll' due to global exclusion rules. 205705 DEBUG: Processing dependency, name: 'api-ms-win-crt-process-l1-1-0.dll', resolved path: None 205725 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 205750 DEBUG: Processing dependency, name: 'api-ms-win-crt-locale-l1-1-0.dll', resolved path: None 205772 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 205789 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 205810 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 205830 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 205857 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 205873 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 205896 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 205922 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' as 'VCRUNTIME140.dll'. 205945 DEBUG: Processing dependency, name: 'api-ms-win-core-path-l1-1-0.dll', resolved path: None 205962 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 205983 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 206004 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 206031 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 206048 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 206069 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 206096 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 206112 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\Lib\\site-packages\\pywin32_system32\\pywintype s310.dll' 206221 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 206254 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 206279 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' as 'python310.dll'. 206303 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 206319 DEBUG: Processing dependency, name: 'OLEAUT32.dll', resolved path: 'C:\\Windows\\system32\\OLEAUT32.dll' 206341 DEBUG: Skipping dependency 'C:\\Windows\\system32\\OLEAUT32.dll' due to global exclusion rules. 206361 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 206389 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 206421 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 206445 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 206468 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 206491 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 206508 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 206536 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 206556 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 206580 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 206598 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 206625 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 206648 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 206671 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 206695 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\Lib\\site-packages\\pywin32_system32\\pythoncom 310.dll' 206991 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 207017 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 207038 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 207066 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 207089 DEBUG: Processing dependency, name: 'pywintypes310.dll', resolved path: 'D:\\work\\Python\\cfepy310\\Lib\\site-packages\\pywin32_system32\\pywintype s310.dll' 207107 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\Lib\\site-packages\\pywin32_system32\\pywintype s310.dll' as 'pywin32_system32\\pywintypes310.dll'. 207134 DEBUG: Processing dependency, name: 'OLEAUT32.dll', resolved path: 'C:\\Windows\\system32\\OLEAUT32.dll' 207159 DEBUG: Skipping dependency 'C:\\Windows\\system32\\OLEAUT32.dll' due to global exclusion rules. 207185 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 207202 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 207230 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 207254 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 207278 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 207296 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 207324 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 207341 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 207370 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 207390 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 207408 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 207431 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_ghash_clmul. pyd' 207460 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 207488 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 207513 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 207531 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 207560 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 207578 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_SHA384.pyd' 207718 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 207772 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 207801 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 207831 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 207855 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 207880 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\PublicKey\\_ed448.p yd' 207989 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 208036 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 208055 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 208079 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 208100 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 208130 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_blowfi sh.pyd' 208161 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 208190 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 208214 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 208239 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 208264 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 208289 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_cast.p yd' 208315 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 208345 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 208374 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 208399 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 208424 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 208443 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_ofb.py d' 208469 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 208495 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 208521 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 208540 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 208569 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 208591 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_ghash_portab le.pyd' 208619 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 208641 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 208671 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 208696 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 208721 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 208747 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\PublicKey\\_x25519. pyd' 208777 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 208802 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 208827 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 208853 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 208879 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 208904 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_BLAKE2b.pyd' 208927 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 208953 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 208972 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 208994 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 209018 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 209048 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_SHA256.pyd' 209079 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 209104 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 209123 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 209146 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 209177 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 209203 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_des.py d' 209354 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 209413 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 209434 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 209457 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 209489 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 209520 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_chacha20.p yd' 209546 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 209571 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 209589 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 209620 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 209646 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 209665 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_keccak.pyd' 209695 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 209718 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 209748 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 209774 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 209800 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 209826 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_eksblo wfish.pyd' 209852 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 209876 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 209906 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 209932 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 209952 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 209982 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_MD4.pyd' 210005 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 210032 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 210059 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 210085 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 210109 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 210129 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Protocol\\_scrypt.p yd' 210164 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 210191 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 210217 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 210237 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 210269 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 210289 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_ecb.py d' 210316 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 210337 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 210368 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 210388 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 210411 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 210436 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_aes.py d' 210495 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 210515 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 210538 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 210572 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 210607 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 210626 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_RIPEMD160.py d' 210660 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 210686 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 210712 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 210739 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 210765 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 210792 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_ctr.py d' 210819 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 210850 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 210870 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 210901 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 210927 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 210954 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_SHA1.pyd' 210981 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 211010 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 211037 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 211057 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 211083 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 211114 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\PublicKey\\_ec_ws.p yd' 211350 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 211407 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 211439 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 211467 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 211494 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 211521 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_BLAKE2s.pyd' 211550 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 211576 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 211609 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 211638 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 211666 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 211685 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Util\\_strxor.pyd' 211719 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 211750 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 211771 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 211803 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 211831 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 211862 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Util\\_cpuid_c.pyd' 211896 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 211916 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 211944 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 211974 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 211995 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 212028 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_cbc.py d' 212051 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 212080 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 212107 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 212129 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 212161 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 212190 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_arc2.p yd' 212214 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 212237 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 212269 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 212295 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 212324 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 212345 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_ocb.py d' 212381 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 212407 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 212435 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 212462 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 212483 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 212512 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_Salsa20.py d' 212546 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 212586 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 212617 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 212645 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 212673 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 212715 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_MD2.pyd' 212742 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 212765 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 212790 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 212825 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 212856 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 212889 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_cfb.py d' 212913 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 212943 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 212971 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 212992 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 213018 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 213044 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_ARC4.pyd' 213081 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 213109 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 213131 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 213162 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 213193 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 213222 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_SHA224.pyd' 213248 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 213277 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 213305 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 213334 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 213362 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 213391 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_MD5.pyd' 213419 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 213450 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 213471 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 213505 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 213534 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 213562 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_pkcs1_deco de.pyd' 213589 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 213619 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 213640 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 213668 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 213703 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 213732 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_poly1305.pyd ' 213763 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 213787 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 213821 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 213850 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 213880 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 213908 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_aesni. pyd' 213938 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 213964 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 213999 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 214027 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 214057 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 214079 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Hash\\_SHA512.pyd' 214618 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 214675 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 214714 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 214744 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 214773 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 214802 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\PublicKey\\_ed25519 .pyd' 214880 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 214920 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 214956 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 214985 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 215007 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 215043 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Cipher\\_raw_des3.p yd' 215116 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 215168 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 215198 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 215231 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 215254 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 215290 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Crypto\\Math\\_modexp.pyd' 215342 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 215367 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 215398 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 215428 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 215458 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 215479 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\styles \\qwindowsvistastyle.dll' 215613 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 215656 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' as 'PyQt5\\Qt5\\bin\\Qt5Gui.dll'. 215692 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 215714 DEBUG: Processing dependency, name: 'UxTheme.dll', resolved path: 'C:\\Windows\\system32\\UxTheme.dll' 215749 DEBUG: Skipping dependency 'C:\\Windows\\system32\\UxTheme.dll' due to global exclusion rules. 215780 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 215809 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' as 'PyQt5\\Qt5\\bin\\Qt5Core.dll'. 215840 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 215863 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 215898 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 215920 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 215956 DEBUG: Processing dependency, name: 'Qt5Widgets.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' 215987 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' as 'PyQt5\\Qt5\\bin\\Qt5Widgets.dll'. 216009 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 216045 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 216076 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 _1.dll' 216107 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 _1.dll' as 'VCRUNTIME140_1.dll'. 216138 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 216160 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 216198 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 216221 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\platfo rms\\qminimal.dll' 216300 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 216327 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 216362 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 216387 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 216425 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 216455 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 216486 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 216516 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 216549 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 216579 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 216611 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 216635 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 216672 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 216696 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 216732 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 216762 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 216799 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 216830 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 216861 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 216892 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 216924 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 216948 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 216983 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qtiff.dll' 217049 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 217073 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 217109 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 217141 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 217172 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 217197 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 217233 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 217264 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 217288 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 217317 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 217354 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 217385 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 217414 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 217442 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 217478 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 217500 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 217537 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\generi c\\qtuiotouchplugin.dll' 217728 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 217775 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 217805 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 217834 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 217863 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 217900 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 217931 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 217963 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 217994 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 218025 DEBUG: Processing dependency, name: 'Qt5Network.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' 218057 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' as 'PyQt5\\Qt5\\bin\\Qt5Network.dll'. 218081 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 218117 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\iconen gines\\qsvgicon.dll' 218184 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 218213 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 218247 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 218279 DEBUG: Processing dependency, name: 'Qt5Svg.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Svg.dll ' 218304 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Svg.dll ' as 'PyQt5\\Qt5\\bin\\Qt5Svg.dll'. 218333 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 218372 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 218418 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 218455 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 218486 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 218518 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 218542 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 218572 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qjpeg.dll' 218778 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 218828 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 218862 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 218887 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 218917 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 218954 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 218985 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 219018 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 219049 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 219085 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 219109 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 219148 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 219177 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 219216 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 219240 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qsvg.dll' 219286 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 219311 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 219349 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 219380 DEBUG: Processing dependency, name: 'Qt5Svg.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Svg.dll ' 219413 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Svg.dll ' due to prior processing. 219450 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 219485 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 219510 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 219549 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 219580 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 219613 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 219639 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 219677 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qtga.dll' 219710 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 219741 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 219779 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 219811 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 219844 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 219875 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 219909 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 219935 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 219973 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 220019 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 220049 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 220086 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qwebp.dll' 220168 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 220210 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 220238 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 220277 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 220309 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 220338 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 220369 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 220399 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 220436 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 220462 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 220499 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 220532 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 220563 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\platfo rmthemes\\qxdgdesktopportal.dll' 220653 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 220710 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 220738 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 220776 DEBUG: Processing dependency, name: 'Qt5DBus.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5DBus.dl l' 220801 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5DBus.dl l' as 'PyQt5\\Qt5\\bin\\Qt5DBus.dll'. 220841 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 220867 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 220898 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 220937 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 220968 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 221002 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 221033 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 221061 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\platfo rms\\qwindows.dll' 221263 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 221311 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 221338 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 221378 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 221419 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 221451 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 221477 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 221507 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 221539 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 221578 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 221609 DEBUG: Processing dependency, name: 'WINMM.dll', resolved path: 'C:\\Windows\\system32\\WINMM.dll' 221643 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WINMM.dll' due to global exclusion rules. 221674 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 221711 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 221745 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' as 'PyQt5\\Qt5\\bin\\MSVCP140.dll'. 221772 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 _1.dll' 221811 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 _1.dll' due to prior processing. 221838 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 221869 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 221903 DEBUG: Processing dependency, name: 'OLEAUT32.dll', resolved path: 'C:\\Windows\\system32\\OLEAUT32.dll' 221942 DEBUG: Skipping dependency 'C:\\Windows\\system32\\OLEAUT32.dll' due to global exclusion rules. 221973 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 222009 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 222040 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 222066 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 222106 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 222133 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 222174 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 222207 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 222248 DEBUG: Processing dependency, name: 'dwmapi.dll', resolved path: 'C:\\Windows\\system32\\dwmapi.dll' 222282 DEBUG: Skipping dependency 'C:\\Windows\\system32\\dwmapi.dll' due to global exclusion rules. 222313 DEBUG: Processing dependency, name: 'WTSAPI32.dll', resolved path: 'C:\\Windows\\system32\\WTSAPI32.dll' 222347 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WTSAPI32.dll' due to global exclusion rules. 222375 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 222414 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 222445 DEBUG: Processing dependency, name: 'IMM32.dll', resolved path: 'C:\\Windows\\system32\\IMM32.dll' 222481 DEBUG: Skipping dependency 'C:\\Windows\\system32\\IMM32.dll' due to global exclusion rules. 222512 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 222541 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qwbmp.dll' 222580 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 222621 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 222649 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 222687 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 222713 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 222754 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 222785 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 222813 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 222853 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 222884 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 222920 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\platfo rms\\qwebgl.dll' 223226 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 223260 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 223288 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 223320 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 223352 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 223383 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 223423 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 223450 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 223489 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 223521 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 223548 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 223582 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 223613 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 223653 DEBUG: Processing dependency, name: 'Qt5Quick.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Quick.d ll' 223686 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Quick.d ll' as 'PyQt5\\Qt5\\bin\\Qt5Quick.dll'. 223719 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 223747 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 223779 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 223812 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 223852 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 223884 DEBUG: Processing dependency, name: 'Qt5WebSockets.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5WebSock ets.dll' 223920 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5WebSock ets.dll' as 'PyQt5\\Qt5\\bin\\Qt5WebSockets.dll'. 223953 DEBUG: Processing dependency, name: 'Qt5Network.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' 223982 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' due to prior processing. 224023 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 224056 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 224097 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 224125 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qicns.dll' 224166 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 224207 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 224238 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 224273 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 224307 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 224340 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 224373 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 224408 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 224435 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 224475 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 224507 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 224542 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qgif.dll' 224577 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 224605 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 224638 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 224677 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 224706 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 224746 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 224779 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 224813 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 224848 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 224886 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 224920 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 224953 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\platfo rms\\qoffscreen.dll' 225133 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 225195 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 225232 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 225260 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 225299 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 225328 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 225367 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 225395 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 225436 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 225469 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 225506 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 225535 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 225573 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 225602 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 225642 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 225677 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 225705 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\plugins\\imagef ormats\\qico.dll' 225758 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 225792 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 225825 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 225854 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 225893 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 225921 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 225957 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 225996 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 226031 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 226061 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 226100 DEBUG: Analyzing binary 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\d3dcompile r_47.dll' 226411 DEBUG: Processing dependency, name: 'RPCRT4.dll', resolved path: 'C:\\Windows\\system32\\RPCRT4.dll' 226459 DEBUG: Skipping dependency 'C:\\Windows\\system32\\RPCRT4.dll' due to global exclusion rules. 226493 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 226532 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 226567 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 226597 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 226636 DEBUG: Processing dependency, name: 'msvcrt.dll', resolved path: 'C:\\Windows\\system32\\msvcrt.dll' 226670 DEBUG: Skipping dependency 'C:\\Windows\\system32\\msvcrt.dll' due to global exclusion rules. 226705 DEBUG: Analyzing binary 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\libEGL.dll ' 226746 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 226783 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 226815 DEBUG: Collecting dependency 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' as 'PyQt5\\Qt5\\bin\\VCRUNTIME140.dll'. 226849 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 226882 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 226917 DEBUG: Processing dependency, name: 'libGLESv2.dll', resolved path: 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\libGLESv2. dll' 226956 DEBUG: Collecting dependency 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\libGLESv2. dll' as 'PyQt5\\Qt5\\bin\\libGLESv2.dll'. 226991 DEBUG: Analyzing binary 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\libGLESv2. dll' 227328 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 227397 DEBUG: Skipping dependency 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 227437 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 227467 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 227503 DEBUG: Skipping dependency 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 227537 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 227576 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 227611 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 227646 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 227676 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 227715 DEBUG: Collecting dependency 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' as 'PyQt5\\Qt5\\bin\\VCRUNTIME140_1.dll'. 227751 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 227785 DEBUG: Processing dependency, name: 'd3d9.dll', resolved path: 'C:\\Windows\\system32\\d3d9.dll' 227821 DEBUG: Skipping dependency 'C:\\Windows\\system32\\d3d9.dll' due to global exclusion rules. 227856 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 227886 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 227922 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 227964 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 228006 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 228042 DEBUG: Analyzing binary 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\opengl32sw .dll' 228785 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 228850 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 228884 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 228920 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 228958 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 228989 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 229028 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 229059 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 229098 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 229134 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 229168 DEBUG: Processing dependency, name: 'imagehlp.dll', resolved path: 'C:\\Windows\\system32\\imagehlp.dll' 229205 DEBUG: Skipping dependency 'C:\\Windows\\system32\\imagehlp.dll' due to global exclusion rules. 229240 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_lzma. pyd' 229277 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 229306 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 229346 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 229382 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 229427 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 229457 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 229498 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 229532 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 229566 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_bz2.p yd' 229606 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 229645 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 229676 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 229710 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 229751 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 229786 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 229822 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 229858 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 229889 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 229925 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_decim al.pyd' 229971 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 230013 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 230048 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 230092 DEBUG: Processing dependency, name: 'api-ms-win-crt-locale-l1-1-0.dll', resolved path: None 230122 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 230162 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 230197 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 230235 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 230271 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 230302 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 230342 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 230377 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 230418 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 230449 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_hashl ib.pyd' 230493 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 230530 DEBUG: Processing dependency, name: 'libcrypto-1_1.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libcry pto-1_1.dll' 230563 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libcry pto-1_1.dll' as 'libcrypto-1_1.dll'. 230602 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 230635 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 230676 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 230713 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 230751 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 230785 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 230830 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 230872 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\markupsafe\\_speedups.cp310 -win_amd64.pyd' 230962 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 230996 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 231029 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 231070 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 231113 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 231147 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 231191 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 231230 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\select .pyd' 231267 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 231300 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 231335 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 231374 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 231407 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 231446 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 231484 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 231520 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 231559 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 231596 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_overl apped.pyd' 231661 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 231696 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 231736 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 231776 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 231807 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 231846 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 231880 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 231921 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 231958 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 231992 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 232037 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_ssl.p yd' 232081 DEBUG: Processing dependency, name: 'libssl-1_1.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libssl -1_1.dll' 232115 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libssl -1_1.dll' as 'libssl-1_1.dll'. 232159 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 232198 DEBUG: Processing dependency, name: 'libcrypto-1_1.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libcry pto-1_1.dll' 232238 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libcry pto-1_1.dll' due to prior processing. 232279 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 232315 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 232350 DEBUG: Processing dependency, name: 'CRYPT32.dll', resolved path: 'C:\\Windows\\system32\\CRYPT32.dll' 232388 DEBUG: Skipping dependency 'C:\\Windows\\system32\\CRYPT32.dll' due to global exclusion rules. 232425 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 232463 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 232502 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 232547 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 232584 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 232627 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 232670 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 232710 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 232749 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_queue .pyd' 232825 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 232861 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 232895 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 232933 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 232973 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 233011 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 233049 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 233088 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_ctype s.pyd' 233135 DEBUG: Processing dependency, name: 'libffi-7.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libffi -7.dll' 233178 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libffi -7.dll' as 'libffi-7.dll'. 233217 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 233255 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 233291 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 233332 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 233375 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 233415 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 233449 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 233487 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 233532 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 233566 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 233611 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 233650 DEBUG: Processing dependency, name: 'OLEAUT32.dll', resolved path: 'C:\\Windows\\system32\\OLEAUT32.dll' 233681 DEBUG: Skipping dependency 'C:\\Windows\\system32\\OLEAUT32.dll' due to global exclusion rules. 233729 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_multi processing.pyd' 233818 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 233878 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 233914 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 233953 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 233993 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 234033 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 234072 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 234117 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 234160 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 234200 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\pyexpa t.pyd' 234249 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 234291 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 234323 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 234367 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 234408 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 234449 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 234484 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 234520 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 234567 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 234601 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 234648 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 234680 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 234729 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_async io.pyd' 234770 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 234816 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 234849 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 234897 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 234930 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 234977 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 235018 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 235059 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\win32\\win32evtlog.pyd' 235108 DEBUG: Processing dependency, name: 'pywintypes310.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' 235147 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' due to prior processing. 235191 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 235233 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 235271 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 235315 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 235351 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 235396 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 235435 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 235478 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 235518 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 235568 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 235601 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 235640 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\win32\\win32api.pyd' 235687 DEBUG: Processing dependency, name: 'pywintypes310.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' 235731 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' due to prior processing. 235779 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 235818 DEBUG: Processing dependency, name: 'VERSION.dll', resolved path: 'C:\\Windows\\system32\\VERSION.dll' 235852 DEBUG: Skipping dependency 'C:\\Windows\\system32\\VERSION.dll' due to global exclusion rules. 235900 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 235939 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 235983 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 236018 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 236067 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 236106 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 236142 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 236186 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 236236 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 236283 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 236326 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 236368 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 236402 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 236449 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 236486 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 236532 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\unicod edata.pyd' 236574 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 236609 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 236649 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 236689 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 236730 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 236779 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 236819 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 236863 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 236903 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 236953 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\_imagingft.cp310-win_a md64.pyd' 237100 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 237161 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 237208 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 237253 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 237296 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 237331 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 237379 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' as 'PIL\\VCRUNTIME140.dll'. 237420 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140_1.dll' 237465 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140_1.dll' as 'PIL\\VCRUNTIME140_1.dll'. 237503 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 237549 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 237587 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 237624 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 237666 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 237707 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 237754 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 237798 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\_webp.cp310-win_amd64. pyd' 237845 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 237881 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 237929 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 237971 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 238014 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 238054 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' due to prior processing. 238098 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 238137 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 238185 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 238221 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 238271 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 238314 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\_imagingtk.cp310-win_a md64.pyd' 238562 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 238634 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 238680 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 238721 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 238771 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 238806 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' due to prior processing. 238855 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 238898 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 238938 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 238984 DEBUG: Processing dependency, name: 'PSAPI.DLL', resolved path: 'C:\\Windows\\system32\\PSAPI.DLL' 239019 DEBUG: Skipping dependency 'C:\\Windows\\system32\\PSAPI.DLL' due to global exclusion rules. 239069 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 239105 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\_cffi_backend.cp310-win_amd 64.pyd' 239155 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 239197 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 239248 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 239289 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 239335 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 239377 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 239422 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 239458 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 239517 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 239556 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 239592 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 239633 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 239684 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 239722 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 239770 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\_imaging.cp310-win_amd 64.pyd' 239844 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 239879 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 239922 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 239964 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 240015 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\MSVCP140.dll' 240056 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\MSVCP140.dll' as 'PIL\\MSVCP140.dll'. 240106 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 240141 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 240190 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' due to prior processing. 240234 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140_1.dll' 240273 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140_1.dll' due to prior processing. 240314 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 240366 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 240406 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 240444 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 240490 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 240536 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 240577 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 240623 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 240659 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 240707 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 240743 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 240790 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\_imagingcms.cp310-win_ amd64.pyd' 240839 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 240889 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 240926 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 240974 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 241010 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' due to prior processing. 241057 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 241103 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 241144 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 241191 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 241236 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 241274 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 241314 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 241367 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 241407 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 241446 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 241491 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 241531 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 241585 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_eleme nttree.pyd' 241629 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 241674 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 241722 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 241763 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 241801 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 241852 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 241891 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 241941 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 241982 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\win32\\win32trace.pyd' 242342 DEBUG: Processing dependency, name: 'pywintypes310.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' 242396 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' due to prior processing. 242442 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 242487 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 242524 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 242575 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 242623 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 242674 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 242715 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 242759 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 242805 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 242847 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 242892 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Pythonwin\\win32ui.pyd' 243040 DEBUG: Processing dependency, name: 'mfc140u.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Pythonwin\\mfc140u.dll' 243105 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Pythonwin\\mfc140u.dll' as 'Pythonwin\\mfc140u.dll'. 243153 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 243195 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 243237 DEBUG: Processing dependency, name: 'pywintypes310.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' 243290 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' due to prior processing. 243328 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 243376 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 243426 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 243470 DEBUG: Processing dependency, name: 'OLEAUT32.dll', resolved path: 'C:\\Windows\\system32\\OLEAUT32.dll' 243513 DEBUG: Skipping dependency 'C:\\Windows\\system32\\OLEAUT32.dll' due to global exclusion rules. 243560 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 243607 DEBUG: Processing dependency, name: 'COMCTL32.dll', resolved path: 'C:\\Windows\\system32\\COMCTL32.dll' 243650 DEBUG: Skipping dependency 'C:\\Windows\\system32\\COMCTL32.dll' due to global exclusion rules. 243689 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 243741 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 243784 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 243827 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 243876 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 243919 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 243960 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 244002 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 244055 DEBUG: Processing dependency, name: 'WINSPOOL.DRV', resolved path: 'C:\\Windows\\system32\\WINSPOOL.DRV' 244104 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WINSPOOL.DRV' due to global exclusion rules. 244143 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 244189 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 244241 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 244283 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 244327 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\win32\\_win32sysloader.pyd' 244441 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 244492 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 244543 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 244580 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 244627 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 244678 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 244725 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 244763 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\greenlet\\_greenlet.cp310-w in_amd64.pyd' 244878 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 244944 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 244994 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 245036 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 245078 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 245128 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 245177 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 245214 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\charset_normalizer\\md.cp31 0-win_amd64.pyd' 245306 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 245345 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 245395 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 245441 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 245484 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 245526 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 245571 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 245625 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\etree.cp310-win_amd64 .pyd' 245680 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 245732 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 245778 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 245825 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 245869 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 245912 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 245962 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 246009 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 246047 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 246095 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 246146 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 246194 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 246233 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 246277 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 246323 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 246378 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 246419 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 246467 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 246511 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 246557 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 246611 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\_elementpath.cp310-wi n_amd64.pyd' 246659 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 246698 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 246743 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 246796 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 246835 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 246885 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 246930 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 246979 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\sax.cp310-win_amd64.p yd' 247037 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 247079 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 247130 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 247178 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 247229 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 247272 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 247313 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 247358 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\objectify.cp310-win_a md64.pyd' 247422 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 247463 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 247507 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 247552 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 247600 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 247647 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 247697 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 247747 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 247797 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 247839 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 247892 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 247932 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 247981 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 248022 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 248078 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 248123 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\html\\diff.cp310-win_ amd64.pyd' 248175 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 248219 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 248264 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 248314 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 248362 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 248413 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 248464 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 248512 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\html\\clean.cp310-win _amd64.pyd' 248560 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 248606 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 248654 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 248696 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 248748 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 248797 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 248837 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 248884 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\lxml\\builder.cp310-win_amd 64.pyd' 248935 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 248982 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 249032 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 249079 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 249132 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 249180 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 249229 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 249268 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_uuid. pyd' 249367 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 249436 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 249482 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 249531 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 249580 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 249626 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 249675 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 249717 DEBUG: Processing dependency, name: 'RPCRT4.dll', resolved path: 'C:\\Windows\\system32\\RPCRT4.dll' 249780 DEBUG: Skipping dependency 'C:\\Windows\\system32\\RPCRT4.dll' due to global exclusion rules. 249820 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_tkint er.pyd' 249906 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 249949 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 249999 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 250049 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 250094 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 250136 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 250199 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 250250 DEBUG: Processing dependency, name: 'tcl86t.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\tcl86t .dll' 250290 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\tcl86t .dll' as 'tcl86t.dll'. 250336 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 250383 DEBUG: Processing dependency, name: 'tk86t.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\tk86t. dll' 250433 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\tk86t. dll' as 'tk86t.dll'. 250477 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 250533 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\_qpdf.cp310-win_am d64.pyd' 250695 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\MSVCP140.dll' 250784 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\MSVCP140.dll' as 'pikepdf\\MSVCP140.dll'. 250834 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 250884 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 250927 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 250983 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140_1.dll ' 251034 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140_1.dll ' as 'pikepdf\\VCRUNTIME140_1.dll'. 251084 DEBUG: Processing dependency, name: 'qpdf29.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\qpdf29.dll' 251134 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\qpdf29.dll' as 'pikepdf\\qpdf29.dll'. 251183 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' 251234 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' as 'pikepdf\\VCRUNTIME140.dll'. 251283 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 251332 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 251378 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 251425 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 251473 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 251520 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\QtWidgets.pyd' 251571 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 251614 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 251661 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 251718 DEBUG: Processing dependency, name: 'python3.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' 251765 DEBUG: Collecting dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' as 'python3.dll'. 251812 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 251868 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 251918 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 251967 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 252012 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 252054 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 252109 DEBUG: Processing dependency, name: 'Qt5Widgets.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' 252152 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' due to prior processing. 252208 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 252252 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\QtGui.pyd' 252306 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 252362 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 252409 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 252456 DEBUG: Processing dependency, name: 'python3.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' 252499 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' due to prior processing. 252552 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 252602 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 252650 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 252701 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 252750 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 252793 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 252850 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 252897 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\QtCore.pyd' 252953 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 253002 DEBUG: Processing dependency, name: 'python3.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' 253053 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' due to prior processing. 253103 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 253152 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 253200 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 253250 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 253297 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 253340 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 253394 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 253441 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 253486 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 253536 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\sip.cp310-win_amd64. pyd' 253591 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 253638 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 253694 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 253742 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 253787 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 253836 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 253884 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 253937 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 253987 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 254037 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 254079 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\yaml\\_yaml.cp310-win_amd64 .pyd' 254134 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 254186 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 254236 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 254278 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 254332 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 254383 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 254431 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 254487 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 254529 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 254585 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\win32\\win32wnet.pyd' 254704 DEBUG: Processing dependency, name: 'pywintypes310.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' 254770 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pywin32_system32\\pywintype s310.dll' due to prior processing. 254821 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 254870 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 254921 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 254964 DEBUG: Processing dependency, name: 'MPR.dll', resolved path: 'C:\\Windows\\system32\\MPR.dll' 255013 DEBUG: Skipping dependency 'C:\\Windows\\system32\\MPR.dll' due to global exclusion rules. 255063 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 255112 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 255167 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 255219 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 255269 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 255319 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 255362 DEBUG: Processing dependency, name: 'NETAPI32.dll', resolved path: 'C:\\Windows\\system32\\NETAPI32.dll' 255417 DEBUG: Skipping dependency 'C:\\Windows\\system32\\NETAPI32.dll' due to global exclusion rules. 255467 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\_socke t.pyd' 255546 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 255588 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 255638 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 255686 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 255735 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 255789 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 255839 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 255886 DEBUG: Processing dependency, name: 'IPHLPAPI.DLL', resolved path: 'C:\\Windows\\system32\\IPHLPAPI.DLL' 255939 DEBUG: Skipping dependency 'C:\\Windows\\system32\\IPHLPAPI.DLL' due to global exclusion rules. 255989 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 256036 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 256089 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 256139 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 256197 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\psutil\\_psutil_windows.cp3 10-win_amd64.pyd' 256290 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 256343 DEBUG: Processing dependency, name: 'PSAPI.DLL', resolved path: 'C:\\Windows\\system32\\PSAPI.DLL' 256393 DEBUG: Skipping dependency 'C:\\Windows\\system32\\PSAPI.DLL' due to global exclusion rules. 256449 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 256494 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 256555 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 256612 DEBUG: Processing dependency, name: 'pdh.dll', resolved path: 'C:\\Windows\\system32\\pdh.dll' 256662 DEBUG: Skipping dependency 'C:\\Windows\\system32\\pdh.dll' due to global exclusion rules. 256711 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 256761 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 256806 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 256862 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 256908 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 256964 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 257007 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 257064 DEBUG: Processing dependency, name: 'IPHLPAPI.DLL', resolved path: 'C:\\Windows\\system32\\IPHLPAPI.DLL' 257123 DEBUG: Skipping dependency 'C:\\Windows\\system32\\IPHLPAPI.DLL' due to global exclusion rules. 257173 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 257223 DEBUG: Processing dependency, name: 'POWRPROF.dll', resolved path: 'C:\\Windows\\system32\\POWRPROF.dll' 257271 DEBUG: Skipping dependency 'C:\\Windows\\system32\\POWRPROF.dll' due to global exclusion rules. 257323 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 257374 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 257424 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 257471 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 257521 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 257574 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 257675 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 257729 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 257775 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 257831 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 257876 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 257939 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 257987 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 258041 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 258158 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 258221 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 258271 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 258322 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 258367 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 258423 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' due to prior processing. 258474 DEBUG: Processing dependency, name: 'dxgi.dll', resolved path: 'C:\\Windows\\system32\\dxgi.dll' 258525 DEBUG: Skipping dependency 'C:\\Windows\\system32\\dxgi.dll' due to global exclusion rules. 258575 DEBUG: Processing dependency, name: 'api-ms-win-crt-locale-l1-1-0.dll', resolved path: None 258625 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 258691 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 258742 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 258789 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 258842 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 258897 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 258950 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 259002 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 259053 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 259105 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 259156 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 259208 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 259259 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 259305 DEBUG: Processing dependency, name: 'd3d11.dll', resolved path: 'C:\\Windows\\system32\\d3d11.dll' 259372 DEBUG: Skipping dependency 'C:\\Windows\\system32\\d3d11.dll' due to global exclusion rules. 259417 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 259473 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 259524 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 259576 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 259626 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 259759 DEBUG: Processing dependency, name: 'USERENV.dll', resolved path: 'C:\\Windows\\system32\\USERENV.dll' 259812 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USERENV.dll' due to global exclusion rules. 259868 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 259919 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 259971 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 260024 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 260073 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 260126 DEBUG: Processing dependency, name: 'NETAPI32.dll', resolved path: 'C:\\Windows\\system32\\NETAPI32.dll' 260185 DEBUG: Skipping dependency 'C:\\Windows\\system32\\NETAPI32.dll' due to global exclusion rules. 260236 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 260287 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 260333 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 260390 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 260441 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' due to prior processing. 260492 DEBUG: Processing dependency, name: 'WINMM.dll', resolved path: 'C:\\Windows\\system32\\WINMM.dll' 260543 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WINMM.dll' due to global exclusion rules. 260599 DEBUG: Processing dependency, name: 'MPR.dll', resolved path: 'C:\\Windows\\system32\\MPR.dll' 260651 DEBUG: Skipping dependency 'C:\\Windows\\system32\\MPR.dll' due to global exclusion rules. 260703 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 260760 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 260818 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 260869 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 260915 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 260972 DEBUG: Processing dependency, name: 'MSVCP140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140_1 .dll' 261024 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140_1 .dll' as 'PyQt5\\Qt5\\bin\\MSVCP140_1.dll'. 261077 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 261127 DEBUG: Processing dependency, name: 'VERSION.dll', resolved path: 'C:\\Windows\\system32\\VERSION.dll' 261185 DEBUG: Skipping dependency 'C:\\Windows\\system32\\VERSION.dll' due to global exclusion rules. 261236 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 261282 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 261341 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 261392 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 261444 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 261497 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 261560 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 261607 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 261661 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 261716 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 261768 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 261814 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 261867 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' 261955 DEBUG: Processing dependency, name: 'MSVCP140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140_1 .dll' 261999 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140_1 .dll' due to prior processing. 262051 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 262105 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 262161 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 262217 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 262274 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 262326 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 262378 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' due to prior processing. 262426 DEBUG: Processing dependency, name: 'dwmapi.dll', resolved path: 'C:\\Windows\\system32\\dwmapi.dll' 262479 DEBUG: Skipping dependency 'C:\\Windows\\system32\\dwmapi.dll' due to global exclusion rules. 262537 DEBUG: Processing dependency, name: 'UxTheme.dll', resolved path: 'C:\\Windows\\system32\\UxTheme.dll' 262590 DEBUG: Skipping dependency 'C:\\Windows\\system32\\UxTheme.dll' due to global exclusion rules. 262643 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 262690 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 262742 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 262801 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 262849 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 262911 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 262975 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 263027 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 263078 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 263135 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 263189 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 263241 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 263294 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 263342 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 263396 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 263461 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 263513 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 263563 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 _1.dll' 263619 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 263674 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 263721 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 263776 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 263830 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 263887 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 263945 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 264005 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' 264145 DEBUG: Processing dependency, name: 'DNSAPI.dll', resolved path: 'C:\\Windows\\system32\\DNSAPI.dll' 264213 DEBUG: Skipping dependency 'C:\\Windows\\system32\\DNSAPI.dll' due to global exclusion rules. 264259 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 264313 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 264372 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 264419 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 264472 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' due to prior processing. 264524 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 264581 DEBUG: Processing dependency, name: 'CRYPT32.dll', resolved path: 'C:\\Windows\\system32\\CRYPT32.dll' 264638 DEBUG: Skipping dependency 'C:\\Windows\\system32\\CRYPT32.dll' due to global exclusion rules. 264686 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 264746 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 264797 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 264862 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 264912 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 264965 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 265023 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 265071 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 265131 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 265180 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 265241 DEBUG: Processing dependency, name: 'IPHLPAPI.DLL', resolved path: 'C:\\Windows\\system32\\IPHLPAPI.DLL' 265288 DEBUG: Skipping dependency 'C:\\Windows\\system32\\IPHLPAPI.DLL' due to global exclusion rules. 265343 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 265412 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 265463 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 265515 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 265565 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 265624 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 265678 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Svg.dll ' 266205 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 266264 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 266323 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 266370 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 266429 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 266480 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 266531 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 266590 DEBUG: Processing dependency, name: 'Qt5Widgets.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' 266644 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Widgets .dll' due to prior processing. 266699 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 266748 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 266815 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 266866 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 266917 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 266971 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5DBus.dl l' 267116 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 267182 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 267234 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 267295 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 267344 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 267400 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 267466 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 267517 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 267574 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 267623 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 267677 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 267734 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 267835 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 267898 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 267948 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 268007 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 268061 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 268117 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' due to prior processing. 268168 DEBUG: Processing dependency, name: 'api-ms-win-crt-locale-l1-1-0.dll', resolved path: None 268229 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 268284 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 268337 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 268397 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 268447 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 268501 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 268563 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 268612 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 268668 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 268722 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 268785 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Quick.d ll' 269700 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 269793 DEBUG: Processing dependency, name: 'Qt5Qml.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Qml.dll ' 269843 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Qml.dll ' as 'PyQt5\\Qt5\\bin\\Qt5Qml.dll'. 269896 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 269953 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 270019 DEBUG: Processing dependency, name: 'Qt5Gui.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' 270070 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Gui.dll ' due to prior processing. 270130 DEBUG: Processing dependency, name: 'Qt5QmlModels.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5QmlMode ls.dll' 270182 DEBUG: Collecting dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5QmlMode ls.dll' as 'PyQt5\\Qt5\\bin\\Qt5QmlModels.dll'. 270243 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 270298 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 270347 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' due to prior processing. 270402 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 270463 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 270512 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 270570 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 270623 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 270679 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 270741 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 270804 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 270863 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 270918 DEBUG: Processing dependency, name: 'Qt5Network.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' 270968 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' due to prior processing. 271030 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 271087 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 271149 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 271203 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5WebSock ets.dll' 271321 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 271399 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 271454 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 271505 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 271567 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 271621 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 271674 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 271737 DEBUG: Processing dependency, name: 'Qt5Network.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' 271804 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' due to prior processing. 271861 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 271916 DEBUG: Analyzing binary 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 272039 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 272110 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 272167 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 272229 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 272278 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 272334 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 272391 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 272454 DEBUG: Analyzing binary 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 272519 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 272568 DEBUG: Skipping dependency 'D:\\Work\\Python\\cfepy310\\Lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 272624 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 272687 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 272744 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 272801 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 272869 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 272920 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libcry pto-1_1.dll' 273274 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 273338 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 273396 DEBUG: Processing dependency, name: 'bcrypt.dll', resolved path: 'C:\\Windows\\system32\\bcrypt.dll' 273452 DEBUG: Skipping dependency 'C:\\Windows\\system32\\bcrypt.dll' due to global exclusion rules. 273504 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 273565 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 273621 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 273673 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 273735 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 273789 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 273843 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 273906 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 273967 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 274030 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 274086 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 274136 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 274205 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 274265 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 274314 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 274373 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 274435 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 274489 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libssl -1_1.dll' 274579 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 274635 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 274690 DEBUG: Processing dependency, name: 'libcrypto-1_1.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libcry pto-1_1.dll' 274750 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libcry pto-1_1.dll' due to prior processing. 274807 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 274871 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 274932 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 274985 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 275049 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 275105 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 275158 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 275222 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 275275 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\libffi -7.dll' 275369 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 275442 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 275503 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 275558 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 275617 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 275674 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 275824 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 275897 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 275947 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 276009 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 276067 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 276126 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 276189 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 276243 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140_1.dll' 276309 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 276374 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 276426 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' due to prior processing. 276487 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 276542 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 276602 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 276653 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 276717 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\MSVCP140.dll' 276816 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 276872 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 276925 DEBUG: Processing dependency, name: 'api-ms-win-crt-locale-l1-1-0.dll', resolved path: None 276981 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 277050 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' 277109 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140.dll' due to prior processing. 277176 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140_1.dll' 277236 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PIL\\VCRUNTIME140_1.dll' due to prior processing. 277292 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 277350 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 277407 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 277460 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 277516 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 277575 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 277643 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 277704 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 277755 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 277819 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\Pythonwin\\mfc140u.dll' 278023 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 278082 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 278144 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 278206 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 278261 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 278321 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 278371 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 278437 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 278487 DEBUG: Processing dependency, name: 'SHLWAPI.dll', resolved path: 'C:\\Windows\\system32\\SHLWAPI.dll' 278546 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHLWAPI.dll' due to global exclusion rules. 278605 DEBUG: Processing dependency, name: 'UxTheme.dll', resolved path: 'C:\\Windows\\system32\\UxTheme.dll' 278669 DEBUG: Skipping dependency 'C:\\Windows\\system32\\UxTheme.dll' due to global exclusion rules. 278721 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 278786 DEBUG: Processing dependency, name: 'api-ms-win-crt-multibyte-l1-1-0.dll', resolved path: None 278845 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 278897 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 278961 DEBUG: Processing dependency, name: 'OLEAUT32.dll', resolved path: 'C:\\Windows\\system32\\OLEAUT32.dll' 279028 DEBUG: Skipping dependency 'C:\\Windows\\system32\\OLEAUT32.dll' due to global exclusion rules. 279089 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 279151 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 279211 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 279270 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 279328 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 279380 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 279455 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 279511 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 279570 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 279622 DEBUG: Processing dependency, name: 'IMM32.dll', resolved path: 'C:\\Windows\\system32\\IMM32.dll' 279680 DEBUG: Skipping dependency 'C:\\Windows\\system32\\IMM32.dll' due to global exclusion rules. 279745 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 279804 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\tcl86t .dll' 279889 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 279945 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 280005 DEBUG: Processing dependency, name: 'NETAPI32.dll', resolved path: 'C:\\Windows\\system32\\NETAPI32.dll' 280058 DEBUG: Skipping dependency 'C:\\Windows\\system32\\NETAPI32.dll' due to global exclusion rules. 280129 DEBUG: Processing dependency, name: 'USERENV.dll', resolved path: 'C:\\Windows\\system32\\USERENV.dll' 280196 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USERENV.dll' due to global exclusion rules. 280254 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 280313 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 280370 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 280429 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 280488 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 280539 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 280613 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 280667 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 280730 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 280791 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 280843 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 280908 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 280961 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 281028 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 281088 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 281147 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 281225 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 281280 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\DLLs\\tk86t. dll' 281506 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 281570 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 281629 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 281694 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 281748 DEBUG: Processing dependency, name: 'COMCTL32.dll', resolved path: 'C:\\Windows\\system32\\COMCTL32.dll' 281812 DEBUG: Skipping dependency 'C:\\Windows\\system32\\COMCTL32.dll' due to global exclusion rules. 281865 DEBUG: Processing dependency, name: 'ole32.dll', resolved path: 'C:\\Windows\\system32\\ole32.dll' 281931 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ole32.dll' due to global exclusion rules. 281984 DEBUG: Processing dependency, name: 'COMDLG32.dll', resolved path: 'C:\\Windows\\system32\\COMDLG32.dll' 282048 DEBUG: Skipping dependency 'C:\\Windows\\system32\\COMDLG32.dll' due to global exclusion rules. 282114 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 282171 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 282240 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 282298 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' 282357 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\VCRUNTIME140 .dll' due to prior processing. 282410 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 282469 DEBUG: Processing dependency, name: 'IMM32.dll', resolved path: 'C:\\Windows\\system32\\IMM32.dll' 282532 DEBUG: Skipping dependency 'C:\\Windows\\system32\\IMM32.dll' due to global exclusion rules. 282598 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 282663 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 282722 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 282781 DEBUG: Processing dependency, name: 'GDI32.dll', resolved path: 'C:\\Windows\\system32\\GDI32.dll' 282848 DEBUG: Skipping dependency 'C:\\Windows\\system32\\GDI32.dll' due to global exclusion rules. 282901 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 282965 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 283020 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 283081 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 283139 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 283213 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\MSVCP140.dll' 284255 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 284314 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 284374 DEBUG: Processing dependency, name: 'api-ms-win-crt-locale-l1-1-0.dll', resolved path: None 284426 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 284494 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140_1.dll ' 284550 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140_1.dll ' due to prior processing. 284617 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 284681 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 284734 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 284800 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 284852 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 284917 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' 284980 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' due to prior processing. 285047 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 285112 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 285168 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 285226 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 285292 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140_1.dll ' 285352 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 285414 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' 285468 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' due to prior processing. 285529 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 285601 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 285667 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 285720 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 285780 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\qpdf29.dll' 285886 DEBUG: Processing dependency, name: 'bcrypt.dll', resolved path: 'C:\\Windows\\system32\\bcrypt.dll' 285951 DEBUG: Skipping dependency 'C:\\Windows\\system32\\bcrypt.dll' due to global exclusion rules. 286007 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140_1.dll ' 286075 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140_1.dll ' due to prior processing. 286129 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 286198 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 286252 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 286318 DEBUG: Processing dependency, name: 'ADVAPI32.dll', resolved path: 'C:\\Windows\\system32\\ADVAPI32.dll' 286385 DEBUG: Skipping dependency 'C:\\Windows\\system32\\ADVAPI32.dll' due to global exclusion rules. 286450 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\MSVCP140.dll' 286510 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\MSVCP140.dll' due to prior processing. 286568 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 286624 DEBUG: Processing dependency, name: 'CRYPT32.dll', resolved path: 'C:\\Windows\\system32\\CRYPT32.dll' 286685 DEBUG: Skipping dependency 'C:\\Windows\\system32\\CRYPT32.dll' due to global exclusion rules. 286745 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 286819 DEBUG: Processing dependency, name: 'USER32.dll', resolved path: 'C:\\Windows\\system32\\USER32.dll' 286884 DEBUG: Skipping dependency 'C:\\Windows\\system32\\USER32.dll' due to global exclusion rules. 286944 DEBUG: Processing dependency, name: 'api-ms-win-crt-utility-l1-1-0.dll', resolved path: None 286998 DEBUG: Processing dependency, name: 'api-ms-win-crt-environment-l1-1-0.dll', resolved path: None 287057 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 287125 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 287186 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 287253 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' 287320 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' due to prior processing. 287373 DEBUG: Processing dependency, name: 'api-ms-win-crt-filesystem-l1-1-0.dll', resolved path: None 287436 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 287503 DEBUG: Processing dependency, name: 'WS2_32.dll', resolved path: 'C:\\Windows\\system32\\WS2_32.dll' 287565 DEBUG: Skipping dependency 'C:\\Windows\\system32\\WS2_32.dll' due to global exclusion rules. 287620 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\pikepdf\\VCRUNTIME140.dll' 287718 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 287778 DEBUG: Processing dependency, name: 'api-ms-win-crt-convert-l1-1-0.dll', resolved path: None 287837 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 287902 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 287961 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 288030 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 288086 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 288152 DEBUG: Analyzing binary 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python3.dll' 288898 DEBUG: Processing dependency, name: 'python310.dll', resolved path: 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' 288960 DEBUG: Skipping dependency 'C:\\Users\\icnte\\AppData\\Local\\Programs\\Python\\Python310\\python310.dl l' due to prior processing. 289013 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140_1 .dll' 289084 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 289139 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 289205 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 289271 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 289325 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 289388 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 289455 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 289517 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 289573 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Qml.dll ' 290282 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 290346 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 290406 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 290461 DEBUG: Processing dependency, name: 'VCRUNTIME140_1.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' 290529 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40_1.dll' due to prior processing. 290589 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 290652 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 290707 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 290770 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 290839 DEBUG: Processing dependency, name: 'api-ms-win-crt-time-l1-1-0.dll', resolved path: None 290902 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 290972 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 291027 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 291088 DEBUG: Processing dependency, name: 'SHELL32.dll', resolved path: 'C:\\Windows\\system32\\SHELL32.dll' 291150 DEBUG: Skipping dependency 'C:\\Windows\\system32\\SHELL32.dll' due to global exclusion rules. 291221 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 291283 DEBUG: Processing dependency, name: 'Qt5Network.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' 291343 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Network .dll' due to prior processing. 291416 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 291473 DEBUG: Processing dependency, name: 'api-ms-win-crt-stdio-l1-1-0.dll', resolved path: None 291540 DEBUG: Analyzing binary 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5QmlMode ls.dll' 291636 DEBUG: Processing dependency, name: 'Qt5Qml.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Qml.dll ' 291690 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Qml.dll ' due to prior processing. 291758 DEBUG: Processing dependency, name: 'VCRUNTIME140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' 291823 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\VCRUNTIME1 40.dll' due to prior processing. 291891 DEBUG: Processing dependency, name: 'api-ms-win-crt-runtime-l1-1-0.dll', resolved path: None 291950 DEBUG: Processing dependency, name: 'Qt5Core.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' 292011 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\Qt5Core.dl l' due to prior processing. 292081 DEBUG: Processing dependency, name: 'KERNEL32.dll', resolved path: 'C:\\Windows\\system32\\KERNEL32.dll' 292141 DEBUG: Skipping dependency 'C:\\Windows\\system32\\KERNEL32.dll' due to global exclusion rules. 292208 DEBUG: Processing dependency, name: 'api-ms-win-crt-math-l1-1-0.dll', resolved path: None 292271 DEBUG: Processing dependency, name: 'MSVCP140.dll', resolved path: 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' 292333 DEBUG: Skipping dependency 'D:\\work\\Python\\cfepy310\\lib\\site-packages\\PyQt5\\Qt5\\bin\\MSVCP140.d ll' due to prior processing. 292391 DEBUG: Processing dependency, name: 'api-ms-win-crt-string-l1-1-0.dll', resolved path: None 292454 DEBUG: Processing dependency, name: 'api-ms-win-crt-heap-l1-1-0.dll', resolved path: None 292749 INFO: Warnings written to C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\build\Conform-e\warn-Conform-e .txt 292986 INFO: Graph cross-reference written to C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\build\Conform-e\xref-Conform-e .html 293126 INFO: Graph drawing written to C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\build\Conform-e\graph-Conform- e.dot 293494 INFO: checking PYZ 293560 INFO: Building PYZ because PYZ-00.toc is non existent 293627 INFO: Building PYZ (ZlibArchive) C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\build\Conform-e\PYZ-00.pyz 294667 INFO: Building PYZ (ZlibArchive) C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\build\Conform-e\PYZ-00.pyz completed successfully. 294749 DEBUG: Loading version info from file: 'D:\\Work\\Python\\cfepy310\\xl\\cfegui\\cfe_versionfile.txt' 294863 INFO: checking PKG 294936 INFO: Building PKG because PKG-00.toc is non existent 294994 INFO: Building PKG (CArchive) Conform-e.pkg 295207 DEBUG: Compiling python script/module file D:\work\Python\cfepy310\lib\site-packages\PyInstaller\loader\pyiboot01_boots trap.py 295999 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ inspect.py 296089 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\_pyinstaller_hooks_contrib\hooks\r thooks\pyi_rth_pywintypes.py 296145 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ pkgutil.py 296213 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ win32comgenpy.py 296277 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\_pyinstaller_hooks_contrib\hooks\r thooks\pyi_rth_pythoncom.py 296341 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ multiprocessing.py 296398 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ setuptools.py 296463 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ pkgres.py 296530 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ _tkinter.py 296588 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_ pyqt5.py 296661 DEBUG: Compiling python script/module file D:\Work\Python\cfepy310\xl\cfegui\cfe_MainForm.py 315980 INFO: Building PKG (CArchive) Conform-e.pkg completed successfully. 316099 INFO: Bootloader D:\work\Python\cfepy310\lib\site-packages\PyInstaller\bootloader\Windows-64b it-intel\runw_d.exe 316172 INFO: checking EXE 316232 INFO: Building EXE because EXE-00.toc is non existent 316291 INFO: Building EXE from EXE-00.toc 316354 INFO: Copying bootloader EXE to C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\application\Conform-e.exe 316516 INFO: Copying icon to EXE 316577 DEBUG: Copying icons from ['D:\\Work\\Python\\cfepy310\\xl\\cfegui\\Resources\\Conform-e_48_1.ico'] 316643 DEBUG: Writing RT_GROUP_ICON 1 resource with 90 bytes 316699 DEBUG: Writing RT_ICON 1 resource with 15402 bytes 316766 DEBUG: Writing RT_ICON 2 resource with 67624 bytes 316833 DEBUG: Writing RT_ICON 3 resource with 16936 bytes 316900 DEBUG: Writing RT_ICON 4 resource with 9640 bytes 316966 DEBUG: Writing RT_ICON 5 resource with 4264 bytes 317026 DEBUG: Writing RT_ICON 6 resource with 1128 bytes 317119 INFO: Copying version information to EXE 317213 INFO: Copying 1 resources to EXE 317267 DEBUG: Processing resource: 'D:\\\\Work\\\\Python\\\\cfepy310\\\\xl\\\\cfegui\\\\cfe_Resource_rc.py' 317332 DEBUG: Resource file 'D:\\\\Work\\\\Python\\\\cfepy310\\\\xl\\\\cfegui\\\\cfe_Resource_rc.py' is an arbitrary data file... An error occurred while packaging Traceback (most recent call last): File "D:\work\Python\cfepy310\lib\site-packages\auto_py_to_exe\packaging.py", line 132, in package run_pyinstaller() File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\__main__.py", line 189, in run run_build(pyi_config, spec_file, **vars(args)) File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\__main__.py", line 61, in run_build PyInstaller.building.build_main.main(pyi_config, spec_file, **kwargs) File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\building\build_main.p y", line 1042, in main build(specfile, distpath, workpath, clean_build) File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\building\build_main.p y", line 982, in build exec(code, spec_namespace) File "C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\Conform-e.spec", line 18, in exe = EXE( File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\building\api.py", line 628, in __init__ self.__postinit__() File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\building\datastruct.p y", line 184, in __postinit__ self.assemble() File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\building\api.py", line 749, in assemble self._retry_operation(self._copy_windows_resource, build_name, resource) File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\building\api.py", line 995, in _retry_operation return func(*args) File "D:\work\Python\cfepy310\lib\site-packages\PyInstaller\building\api.py", line 918, in _copy_windows_resource raise ValueError( ValueError: Invalid Windows resource specifier 'D:\\\\Work\\\\Python\\\\cfepy310\\\\xl\\\\cfegui\\\\cfe_Resource_rc.py'! For arbitrary data file, the format is 'filename,type,name,[language]'! Project output will not be moved to output folder Complete. From python at mrabarnett.plus.com Mon Oct 30 17:28:07 2023 From: python at mrabarnett.plus.com (MRAB) Date: Mon, 30 Oct 2023 21:28:07 +0000 Subject: PyInstaller value error: Invalid Windows resource specifier In-Reply-To: <002201da0b66$00940000$01bc0000$@ncf.ca> References: <002201da0b66$00940000$01bc0000$@ncf.ca> Message-ID: <189c82d3-e698-4b79-b0a9-4d69b4fb2400@mrabarnett.plus.com> On 2023-10-30 19:19, McDermott Family via Python-list wrote: > Hello, I am trying to create a one file executable with pyinstaller 6.1.0 > and auto-py-to-exe 2.41.0 using Python version 3.10.9 in a virtual > environment. > > Some points before the output of pinstaller is shown. My resource .py file > is there where it should be. Also I can fun my program from the command-line > > > and it does work with the compiled resource file without a problem. Any help > would be greatly appreciated. Thank you. > > > Running auto-py-to-exe v2.41.0 > > Building directory: C:\Users\icnte\AppData\Local\Temp\tmpp870eytg > > Provided command: pyinstaller --noconfirm --onefile --windowed --icon > "D:/Work/Python/cfepy310/xl/cfegui/Resources/Conform-e_48_1.ico" --name > "Conform-e" --clean --log-level "DEBUG" --debug "all" --version-file > "D:/Work/Python/cfepy310/xl/cfegui/cfe_versionfile.txt" --resource > "D:/Work/Python/cfepy310/xl/cfegui/cfe_Resource_rc.py" > "D:/Work/Python/cfepy310/xl/cfegui/cfe_MainForm.py" > > Recursion Limit is set to 5000 > > Executing: pyinstaller --noconfirm --onefile --windowed --icon > D:/Work/Python/cfepy310/xl/cfegui/Resources/Conform-e_48_1.ico --name > Conform-e --clean --log-level DEBUG --debug all --version-file > D:/Work/Python/cfepy310/xl/cfegui/cfe_versionfile.txt --resource > D:/Work/Python/cfepy310/xl/cfegui/cfe_Resource_rc.py > D:/Work/Python/cfepy310/xl/cfegui/cfe_MainForm.py --distpath > C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\application --workpath > C:\Users\icnte\AppData\Local\Temp\tmpp870eytg\build --specpath > C:\Users\icnte\AppData\Local\Temp\tmpp870eytg > [snip] > > ValueError: Invalid Windows resource specifier > 'D:\\\\Work\\\\Python\\\\cfepy310\\\\xl\\\\cfegui\\\\cfe_Resource_rc.py'! > For arbitrary data file, the format is 'filename,type,name,[language]'! > > > > Project output will not be moved to output folder > > Complete. > In the docs for "--resource" it says: """FILE can be a data file or an exe/dll. For data files, at least TYPE and NAME must be specified.""" That might be the problem, but I haven't been able to find out what "TYPE" means! I also wonder whether "--add-data" would work.