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

Re: Save-to-file code not quite working completely
by dn Aug. 10, 2020

Aug. 10, 2020

On 10/08/2020 05:23, Dennis Lee Bieber wrote: > On Sun, 9 Aug 2020 11:50:51 +1200, dn via Python-list > <python-list(a)python.org> declaimed the following: >> To be a logomach, let's talk about "update":- >> May I advise that a 'good practice' would be to create a new file, and >> thus be able to (also) maintain the old version as a 'backup'. >> (also: advantage when debugging/testing logic!) > > Per the documentation, this is exactly what the "inplace=True" does! It > renames the original file, then writes the output under the original name. > Keeping the backup after processing requires providing an explicit > "backup=.ext" option, otherwise it uses .bak and deletes the file when > processing completes. Apologies for incomplete answer. I have finally remembered why I (have long) steer-clear of fileinput: a) criticism from Martijn Pieters https://www.zopatista.com/python/2013/11/26/inplace-file-rewriting/ b) I can't recall 'my' last application requiring/desiring a flat-file that wasn't JSON or YAML. The above article is (2013) old. I notice that whilst the github received a trivial update one month back, that the PyPI entry is almost two years old. I (am biased, admittedly) still maintain that for anything more than the trivial, a direct-access mechanism is the tool-for-the-job, and because I think they are 'easy', an RDBMS. YMMV! -- Regards =dn

1 0

Re: How explain why Python is easier/nicer than Lisp which has a simpler grammar/syntax?
by Christian Seberino Aug. 10, 2020

Aug. 10, 2020

> Trying to maintain that recursive list of unclosed lists in your > brain is fun. It stretches the brain in interesting ways. I was > way into Lisp at one point, including writing several Lisp > interpreters (that simple structure makes Lisp very easy to > implement). But I never found Lisp code very maintainable, because > any time you read a program, you have to build up that list in your > head every time just to follow the logic structure and figure out > what the return value will be. So basically while recursion is easy to write it isn't so easy for other people to understand compared to iterative code. So maybe that is a big part of it....recursion is just harder on the brain than iteration. cs

9 17

Re: Including a Variable In the HTML Tags When Sending An Email
by sammy.jackson987＠gmail.com Aug. 9, 2020

Aug. 9, 2020

On Sunday, August 9, 2020 at 1:32:30 AM UTC+1, Richard Damon wrote: > On 8/8/20 8:03 PM, sammy.jackson987(a)gmail.com wrote: > > If i use place holders i.e. {0} and {1} where {0} is the name and {1} is the dataframe i get an error for the following line of code:- > > .format((Name,Body).to_html()) which states 'tuple' object has no attribute 'to_html'. > > I would do it as > > .format(Name, Body.to_html()) if your names really are just straight > letters. > > If they might have some funny characters that need html handling, you > could do: > > import html > > > .format(html.escape(Name), Body.to_html()) > > > Note that different types need to be treated differently to get them > into clean html. > > > -- > Richard Damon Richard I love you. The following change you recommended worked.

2 1

Re: Any ideas for a new language inspired to Python?
by 2QdxY4RzWzUUiLuE＠potatochowder.com Aug. 9, 2020

Aug. 9, 2020

On 2020-08-09 at 13:07:03 -0400, Dennis Lee Bieber <wlfraed(a)ix.netcom.com> wrote: > On Sun, 9 Aug 2020 09:31:04 +0100, Barry Scott <barry(a)barrys-emacs.org> > declaimed the following: > > > > >By going to C you are really saying you want to use the native instructions of your CPU. > >Contrast that with bytecode that needs an interpreter. > > > > Unless one has located a C-compiler that generates byte-code for some > virtual machine. gcc compiles source code into different levels of virtual machines, and then those virtual machines into actual object code. Start at https://gcc.gnu.org/onlinedocs/gccint/index.html, and drill down into section 6.3.8 (Anatomy of a Language Front End) and chapter 9 (Passes and Files of the Compiler). Nothing stops you from translating your source code directly into, say, RTL. The Wikipedia page for LLVM tells me it's designed for this sort of thing.

1 0

Python 3 Feature Request: `pathlib` Use Trailing Slash Flag
by Adam Hendry Aug. 9, 2020

Aug. 9, 2020

`pathlib` trims trailing slashes by default, but certain packages require trailing slashes. In particular, `cx_Freeze.bdist_msi` option "directories" is used to build the package directory structure of a program and requires trailing slashes. Does anyone think it would be a good idea to add a flag or argument to `pathlib.Path` to keep trailing slashes? For instance, I envision something like: ``` from pathlib import Path my_path = Path(r"foo/bar/", keep_trailing_slash=True) ``` The argument could be made `False` by default to maintain backwards compatibility. The only way I know to keep the backslash and maintain cross-compatibility is as follows: ``` import os from pathlib import Path my_path = f"{Path(r"foo/bar").resolve()}{os.sep}" ``` although this returns a string and the `Path` object is lost. Any thoughts?

1 0

Re: Module import question
by Bob Gailer Aug. 9, 2020

Aug. 9, 2020

On Aug 9, 2020 11:41 AM, "Mats Wichmann" <mats(a)python.org> wrote: > > On 8/9/20 12:51 AM, Gabor Urban wrote: > > Hi guys, > > > > I have a quite simple question but I could not find the correct answer. > > > > I have twoo modules A and B. A imports B. If I import A in a script, Will > > be B imported automatically? I guess not, but fő not know exactly. > > > > Thanks for your answer ín advance, > > Think of import as meaning "make available in namespace". Well it's actually a little more involved than that. When python import a module it executes the module code. This is why you often see at the bottom of a module: if __name__ == '__main__': # code to execute when running the module as opposed to importing it. When importing a module __name__ is the module's name rather than '__main__'. What happens when module A Imports module B depends on whether or not the import B statement is actually executed.

1 0

Re: Module import question
by Gabor Urban Aug. 9, 2020

Aug. 9, 2020

Hi guys, Thanks for the answers. IT is clear Noé. Gábor

1 0

3.8.5 Failing To Install With pythonz
by Tim Daneliuk Aug. 9, 2020

Aug. 9, 2020

I have a weird problem I could use a bit of help with ... I have successfully installed 3.8.5 using pew/pythonz on a BSD FreeBSD system. But when I attempt to install it on a Linux system I get the traceback below. In this case, pew/pythonz were installed locally in my own account using system native python 3.6: Installing CPython-3.8.5 into /home/tundra/.pythonz/pythons/CPython-3.8.5 Traceback (most recent call last): File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/installer/pythoninstaller.py", line 204, in install self.make() File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/installer/pythoninstaller.py", line 350, in make s.check_call(make) File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/util.py", line 294, in check_call returncode = self.call(cmd) File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/util.py", line 286, in call fp.write(line) UnicodeEncodeError: 'ascii' codec can't encode character '\u2018' in position 81: ordinal not in range(128) ERROR: Failed to install CPython-3.8.5. Check /home/tundra/.pythonz/log/build.log to see why. Traceback (most recent call last): File "/home/tundra/.local/bin/pew", line 11, in <module> sys.exit(pew()) File "/home/tundra/.local/lib/python3.6/site-packages/pew/pew.py", line 809, in pew return command(sys.argv[2:]) File "/home/tundra/.local/lib/python3.6/site-packages/pew/pew.py", line 704, in install_cmd return actual_installer.install() File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/installer/pythoninstaller.py", line 204, in install self.make() File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/installer/pythoninstaller.py", line 350, in make s.check_call(make) File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/util.py", line 294, in check_call returncode = self.call(cmd) File "/home/tundra/.local/lib/python3.6/site-packages/pythonz/util.py", line 286, in call fp.write(line) UnicodeEncodeError: 'ascii' codec can't encode character '\u2018' in position 81: ordinal not in range(128) Ideas anyone?

2 1

Module import question
by Gabor Urban Aug. 9, 2020

Aug. 9, 2020

Hi guys, I have a quite simple question but I could not find the correct answer. I have twoo modules A and B. A imports B. If I import A in a script, Will be B imported automatically? I guess not, but fő not know exactly. Thanks for your answer ín advance, Gábor

2 1

[ANN] PyInstaller 4.0
by Hartmut Goebel Aug. 9, 2020

Aug. 9, 2020

Hello, on behalf of the PyInstaller development team I'm happy to announce PyInstaller 4.0. http://www.pyinstaller.org Thanks for all those who contributed questions, bug-reports or pull-requests. PyInstaller is in urgent need of funding to make future security fixes happen, see <https://github.com/pyinstaller/pyinstaller/issues/4404> for details. === Important Changes === Release 4.0 adds support for 3rd-party packages to provide PyInstaller hooks along with the package. This allows Maintainers of other Python packages to deliver up-to-date PyInstaller hooks as part of their package. See our sample project <https://github.com/pyinstaller/hooksample> for more information. PyInstaller uses this option itself to provide updated hooks much faster: Many hooks are moved into the new package pyinstaller-hooks-contrib <https://github.com/pyinstaller/pyinstaller-hooks-contrib>, which is updated monthly. This package is installed automatically when installing PyInstaller, but can also be updated independently. Finally, this version drops support for Python 2.7, which is end-of-life since January 2020.. The minimum required version is now Python 3.5. The last version supporting Python 2.7 was PyInstaller 3.6. The full changelog for this release can be found at: https://pyinstaller.readthedocs.io/en/v4.0/CHANGES.html === What it is === PyInstaller bundles a Python application and all its dependencies into a single package. The user can run the packaged app without installing a Python interpreter or any modules. PyInstaller reads a Python script written by you. It analyzes your code to discover every other module and library your script needs in order to execute. Then it collects copies of all those files – including the active Python interpreter! – and puts them with your script in a single folder, or optionally in a single executable file. PyInstaller is tested against Windows, Mac OS X, and Linux. However, it is not a cross-compiler: to make a Windows app you run PyInstaller in Windows; to make a Linux app you run it in Linux, etc. PyInstaller has been used successfully with AIX, Solaris, and FreeBSD, but is not tested against them. === Help keeping PyInstaller alive === Maintaining PyInstaller is a huge amount of work. PyInstaller development can only continue if users and companies provide sustainable funding. Please consider recurring donations. See http://www.pyinstaller.org/funding.html for how to support PyInstaller. === Installation === PyInstaller can be installed from PyPi using pip install pyinstaller === Important Changes === The full changelog for this release can be found at: https://pyinstaller.readthedocs.io/en/v4.0/CHANGES.html === Feedback === We're eager to listen to your feedback on using PyInstaller: Bug tracker: https://github.com/pyinstaller/pyinstaller/issues Mailing list: http://groups.google.com/group/PyInstaller -- Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: http://www.goebel-consult.de/blog/warum-sie-nicht-perl-programmiern-sollten Kolumne: http://www.cissp-gefluester.de/2012-02-bring-your-own-life-glosse

1 0