🌐 Mailman 3 September 2016 - Python-list - python.org

Re: Oh gods can we get any more off-topic *wink* [was Re: [Python-ideas] Inconsistencies]
by Steve D'Aprano Sept. 15, 2016

Sept. 15, 2016

On Thu, 15 Sep 2016 04:02 pm, Random832 wrote: > On Wed, Sep 14, 2016, at 23:12, Steve D'Aprano wrote: >> Yes it does. Even an infinitely large flat plane has a horizon almost >> identical to the actual horizon. > > Your link actually doesn't support the latter claim, it goes into some > detail on why it wouldn't if it were infinitely large due to > gravitational effects on light. No, the horizon would still be horizontal. It merely wouldn't *look* horizontal, an optical illusion. And even there, I have my doubts. In a universe where at least one infinitely large flat planet existed, gravity would clearly have to be significantly different from our universe's gravity, lest the universe be destroyed. In the scenario given by the article, the flat earth is acting as a Newtonian black hole: light cannot escape the planet. In addition, anything that came into range of the flat earth's gravity -- which would be *everything* in the universe -- would experience a 1 gee force[1] towards the earth, no matter how far away it was. There would be a steady rain of meteors, comets and even stars onto the planet. The planet would also be gravitationally unstable in the horizontal direction. Consider a single atom somewhere in the flat plane. It is gravitationally pulled by an infinite number of other atoms in one direction, say to the left, balanced by an infinite number in the opposite direction, to the right. But those infinite forces will only be in balance if the body of the planet is utterly, perfectly, 100% uniform. Any tiny variation in density will lead to an inbalance in one direction or another, which will increase the variations in density and hence increasing the preferential gravitational force. For a normal planet, the gravitational forces are typically smaller than the electromagnet repulsion of atoms to each other, and so there's a limit to how densely packed the planet will be. But in an infinitely large planet, the forces can increase without limit, leading to the planet either collapsing into a relativistic black hole (it's already a Newtonian black hole!) or being torn apart. Or both. In any case, even if the earth is flat, it's not infinitely big. We know that because some stars dip below the horizon. Unless there are convenient tunnels for them to travel through... Personally, I'm more fond of the Hollow Earth theory. The earth is a sphere, but it's a hollow sphere, and we're on the inside... :-) [1] Yes I know gee is a unit of acceleration, not force. Someone else can do the dimensional analysis, there's a limit to how much care I'm going to put into counter-factual physics like infinitely large flat planets. -- Steve “Cheer up,” they said, “things could be worse.” So I cheered up, and sure enough, things got worse.

3 2

Re: Oh gods can we get any more off-topic *wink* [was Re: [Python-ideas] Inconsistencies]
by Steve D'Aprano Sept. 15, 2016

Sept. 15, 2016

On Thu, 15 Sep 2016 11:45 pm, Grant Edwards wrote: > On 2016-09-15, Steve D'Aprano <steve+python(a)pearwood.info> wrote: >> On Thu, 15 Sep 2016 06:19 am, breamoreboy(a)gmail.com wrote: >> >>> It is so blantantly obvious that the world is not flat I find this >>> discussion flabbergasting. >> >> You wouldn't say that if you lived in Kanvas, or the west coast of >> Ireland. >> >> I'm told that a few years ago somebody accidentally dumped a trailer load >> of soil by the side of the road in Kanvas, and within a day some >> enterprising entrepreneur had set up a thriving roadside business >> offering mountain-climbing tours to the locals. > > Kanvas? Oh vorry about that, that'v a villy mivtake. I obsiouvly meant to type Kansav. -- Vteve

2 1

Playing an audio file, but not waiting for it to finish?
by kerbingamer376 Sept. 15, 2016

Sept. 15, 2016

Hi, I have a library that allows me to play sound files. However, the play function waits for the sound to finish before it returns, and I'd like to be able to start the sound playing, and then have it return immediately so my program can continue, but also be able to know when the sound finishes. Is this possible, without modifying the library?

3 2

logging TypeError: not all arguments converted during string formatting
by Daiyue Weng Sept. 15, 2016

Sept. 15, 2016

Hi, I am trying to record memory and CPU usages and load a logger from an external config file (logging.conf), [loggers] keys=root,hardware_log [handlers] keys=consoleHandler,hardwareFileHandler [formatters] keys=hardwareFormatter [logger_root] level=DEBUG handlers=consoleHandler [logger_hardware_log] level=DEBUG handlers=hardwareFileHandler qualname=hardware_log propagate=0 [handler_consoleHandler] class=StreamHandler level=DEBUG formatter=hardwareFormatter args=(sys.stdout,) [handler_hardwareFileHandler] class=handlers.RotatingFileHandler maxBytes=51200 level=DEBUG formatter=hardwareFormatter args=("log/hardware.log",) [formatter_hardwareFormatter] format=pathname~%(pathname)s||timestamp~%(asctime)s||level~%(levelname)s||name~%(name)s||function_name~%(funcName)s||line_no~%(lineno)s||debug_CPU~%(message)s||debug_Mem~%(message)s datefmt=%m/%d/%Y %H:%M:%S class=logging.Formatter import logging import psutil logging.config.fileConfig('logging.conf') hardware_log = logging.getLogger(HARDWARELOGNAME) free_mem_gb_pre = psutil.virtual_memory().available / 1000000000. cpu_util_pct_pre = psutil.cpu_percent() hardware_log.info(cpu_util_pct_pre, free_mem_gb_pre) I got the following errors, --- Logging error --- Traceback (most recent call last): File "C:\Continuum\Anaconda3\lib\logging\__init__.py", line 980, in emit msg = self.format(record) File "C:\Continuum\Anaconda3\lib\logging\__init__.py", line 830, in format return fmt.format(record) File "C:\Continuum\Anaconda3\lib\logging\__init__.py", line 567, in format record.message = record.getMessage() File "C:\Continuum\Anaconda3\lib\logging\__init__.py", line 330, in getMessage msg = msg % self.args TypeError: not all arguments converted during string formatting Call stack: File "C:\Program Files (x86)\JetBrains\PyCharm 2016.2.1\helpers\pycharm\pytestrunner.py", line 60, in <module> main() File "C:\Program Files (x86)\JetBrains\PyCharm 2016.2.1\helpers\pycharm\pytestrunner.py", line 35, in main exitstatus = hook.pytest_cmdline_main(config=config) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 724, in __call__ return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 338, in _hookexec return self._inner_hookexec(hook, methods, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 333, in <lambda> _MultiCall(methods, kwargs, hook.spec_opts).execute() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 596, in execute res = hook_impl.function(*args) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\main.py", line 115, in pytest_cmdline_main return wrap_session(config, _main) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\main.py", line 90, in wrap_session session.exitstatus = doit(config, session) or 0 File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\main.py", line 121, in _main config.hook.pytest_runtestloop(session=session) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 724, in __call__ return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 338, in _hookexec return self._inner_hookexec(hook, methods, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 333, in <lambda> _MultiCall(methods, kwargs, hook.spec_opts).execute() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 596, in execute res = hook_impl.function(*args) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\main.py", line 146, in pytest_runtestloop item.config.hook.pytest_runtest_protocol(item=item, nextitem=nextitem) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 724, in __call__ return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 338, in _hookexec return self._inner_hookexec(hook, methods, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 333, in <lambda> _MultiCall(methods, kwargs, hook.spec_opts).execute() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 595, in execute return _wrapped_call(hook_impl.function(*args), self.execute) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 247, in _wrapped_call call_outcome = _CallOutcome(func) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 264, in __init__ self.result = func() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 596, in execute res = hook_impl.function(*args) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\runner.py", line 65, in pytest_runtest_protocol runtestprotocol(item, nextitem=nextitem) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\runner.py", line 75, in runtestprotocol reports.append(call_and_report(item, "call", log)) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\runner.py", line 119, in call_and_report call = call_runtest_hook(item, when, **kwds) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\runner.py", line 137, in call_runtest_hook return CallInfo(lambda: ihook(item=item, **kwds), when=when) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\runner.py", line 149, in __init__ self.result = func() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\runner.py", line 137, in <lambda> return CallInfo(lambda: ihook(item=item, **kwds), when=when) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 724, in __call__ return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 338, in _hookexec return self._inner_hookexec(hook, methods, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 333, in <lambda> _MultiCall(methods, kwargs, hook.spec_opts).execute() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 595, in execute return _wrapped_call(hook_impl.function(*args), self.execute) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 247, in _wrapped_call call_outcome = _CallOutcome(func) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 264, in __init__ self.result = func() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 596, in execute res = hook_impl.function(*args) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\runner.py", line 90, in pytest_runtest_call item.runtest() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\python.py", line 1406, in runtest self.ihook.pytest_pyfunc_call(pyfuncitem=self) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 724, in __call__ return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 338, in _hookexec return self._inner_hookexec(hook, methods, kwargs) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 333, in <lambda> _MultiCall(methods, kwargs, hook.spec_opts).execute() File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 596, in execute res = hook_impl.function(*args) File "C:\Continuum\Anaconda3\lib\site-packages\_pytest\python.py", line 286, in pytest_pyfunc_call testfunction(**testargs) File "C:\Users\dweng\PycharmProjects\lumar_ingestion\ingestion_workflows\full_table_workflow_test.py", line 40, in test_SAP_invoice tab_output = workflow.execute(tab) File "C:\Users\dweng\PycharmProjects\lumar_ingestion\ingestion_workflows\full_table_workflow.py", line 85, in execute data = workflow.execute(data) File "C:\Users\dweng\PycharmProjects\lumar_ingestion\Workflow\workflow.py", line 25, in execute output = self.steps[0].execute(data) File "C:\Users\dweng\PycharmProjects\lumar_ingestion\ingestion_workflow_modules\import_to_dataframe.py", line 61, in execute hardware_log.info(cpu_util_pct_pre, free_mem_gb_pre) Message: 38.5 Arguments: (8.87662592,) How to fix the problem? cheers

3 2

Re: Oh gods can we get any more off-topic *wink* [was Re: [Python-ideas] Inconsistencies]
by breamoreboy＠gmail.com Sept. 15, 2016

Sept. 15, 2016

On Wednesday, September 14, 2016 at 9:00:04 PM UTC+1, MRAB wrote: > On 2016-09-14 18:43, Dale Marvin via Python-list wrote: > > On 9/14/16 12:20 AM, Steven D'Aprano wrote: > >> On Wednesday 14 September 2016 16:54, Rustom Mody wrote: > >> > >>> everything we know will be negated in 5-50-500 years > >> > >> I'm pretty sure that in 5, 50, 500 or even 5000 years, the sun will still rise > >> in the east, water will be wet, fire will burn, dogs will have mammary glands > >> and frogs[1] won't, and the square root of 100 will still be 10. > >> > >> Isaac Asimov once wrote: > >> > >> When people thought the earth was flat, they were wrong. When people > >> thought the earth was spherical, they were wrong. But if you think that > >> thinking the earth is spherical is just as wrong as thinking the earth > >> is flat, then your view is wronger than both of them put together. > > > >> http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm > >> > >> [1] Assuming that there are any frogs left by then. > >> > > > > Funny, Asimov's professors must have taught him the same false history > > that I was taught at college. There's much evidence that medieval > > scholars did not believe the earth was flat. > > > > <https://en.wikipedia.org/wiki/Myth_of_the_flat_Earth> > > > Where does it say that he thought that _medieval_ scholars did not > believe the earth was flat? It is so blantantly obvious that the world is not flat I find this discussion flabbergasting. Anybody who has tried to take any form of vehicle up, or probably more dangerously down, any form of hill knows that. As for the raving lunatics who make their living by riding up and down these http://www.bbc.co.uk/news/in-pictures-37348004, well need I say more? Kindest regards. Mark Lawrence.

4 3

Re: Oh gods can we get any more off-topic *wink* [was Re: [Python-ideas] Inconsistencies]
by Gregory Ewing Sept. 15, 2016

Sept. 15, 2016

Dennis Lee Bieber wrote: > And then there is Pratchett's Discworld... which is both flat and round > (just not spherical) And it has a horizon -- if you go far enough you fall off the edge. -- Greg

1 0

Re: ‘pip2 install cryptography’ does not work
by Cecil Westerhof Sept. 15, 2016

Sept. 15, 2016

On Thursday 15 Sep 2016 10:19 CEST, dieter(a)handshake.de wrote: > Cecil Westerhof <Cecil(a)decebal.nl> writes: > >> I try to do a: >> pip2 install cryptography >> >> But this give: gcc -pthread -shared >> build/temp.linux-x86_64-2.7/build/temp.linux-x86_64-2.7/_openssl.o >> -L/usr/lib64 -lssl -lcrypto -lpython2.7 -o >> build/lib.linux-x86_64-2.7/cryptography/hazmat/bindings/_openssl.so >> /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: >> /usr/lib64/libpython2.7.a(abstract.o): relocation R_X86_64_32S >> against _Py_NotImplementedStruct' can not be used when making a >> shared object; recompile with -fPIC /usr/lib64/libpython2.7.a: >> error adding symbols: Bad value collect2: error: ld returned 1 exit >> status error: command 'gcc' failed with exit status 1 > > Apparently, the linker requires use of the "-fPIC" option > ("PIC" stands for "position independent code") for linking a shared > library. > > The problem might come from your system's Python installation > (apparently, that one is used). Usually, you would have > a "libpython*.so" (i.e. a shared object) and it would contain > modules compiled with "-fPIC". In your case, the > static library "libpython*.a" seems to be used and (apparently) > contains not position idependent modules. I installed python-devel and the problems went away. What I find a kind of strange that I did not have python3-devel installed and I do not have a problem with: pip3 install cryptography -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof

1 0

Re: Oh gods can we get any more off-topic *wink* [was Re: [Python-ideas] Inconsistencies]
by alister Sept. 15, 2016

Sept. 15, 2016

On Wed, 14 Sep 2016 18:04:26 -0700, Chris Kaynor wrote: > On Wed, Sep 14, 2016 at 1:19 PM, <breamoreboy(a)gmail.com> wrote: > >> It is so blantantly obvious that the world is not flat I find this >> discussion flabbergasting. Anybody who has tried to take any form of >> vehicle up, or probably more dangerously down, any form of hill knows >> that. As for the raving lunatics who make their living by riding up >> and down these http://www.bbc.co.uk/news/in-pictures-37348004, well >> need I say more? >> >> > Going up or down a mountain does not prove the world is round by itself, No but it does demonstrate that it is not flat (@ a bare minimum it undulates) Not flat != round -- A gift of a flower will soon be made to you.

1 0

‘pip2 install cryptography’ does not work
by Cecil Westerhof Sept. 15, 2016

Sept. 15, 2016

I try to do a: pip2 install cryptography But this give: gcc -pthread -shared build/temp.linux-x86_64-2.7/build/temp.linux-x86_64-2.7/_openssl.o -L/usr/lib64 -lssl -lcrypto -lpython2.7 -o build/lib.linux-x86_64-2.7/cryptography/hazmat/bindings/_openssl.so /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libpython2.7.a(abstract.o): relocation R_X86_64_32S against `_Py_NotImplementedStruct' can not be used when making a shared object; recompile with -fPIC /usr/lib64/libpython2.7.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status error: command 'gcc' failed with exit status 1 ---------------------------------------- Command "/usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-QoMAwn/cryptography/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-LxpwQ4-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-QoMAwn/cryptography/ What is happening here and what can I do about it? -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof

2 1

Re: Why don't we call the for loop what it really is, a foreach loop?
by Paul Rubin Sept. 15, 2016

Sept. 15, 2016

Travis Griggs <travisgriggs(a)gmail.com> writes: > for each in ['cake'] + ['eat', 'it'] * 2: > print(each) https://pbs.twimg.com/media/Cr-edT2VUAArpVL.jpg

4 4