🌐 Mailman 3 May 2018 - Python-list - python.org

Re: How to use an API (xsd format) in Python?
by richardchausse＠gmail.com May 10, 2018

May 10, 2018

On Thursday, May 10, 2018 at 1:54:11 PM UTC-4, Chris Angelico wrote: > > I need to get some data from CME Group which provides a public API to download (xsd) > > What packages should I use in Python to access this data through this API. Thank you. > > Depends a lot on the API, and I have no idea what CME Group is doing > (or who that even is); but my first thought would be to grab the > 'requests' package. If it's any sort of HTTP download, requests is > usually the best way to do it. > > ChrisA They provide Margin Requirements numbers attached to each future contract. The XSD file provide the XML Schema. I'm not sure what to do with that xsd. https://www.cmegroup.com/confluence/display/EPICSANDBOX/Margin+Service+API+…

2 1

How to use an API (xsd format) in Python?
by richardchausse＠gmail.com May 10, 2018

May 10, 2018

I need to get some data from CME Group which provides a public API to download (xsd) What packages should I use in Python to access this data through this API. Thank you.

2 1

Leading 0's syntax error in datetime.date module (Python 3.6)
by Virgil Stokes May 10, 2018

May 10, 2018

Module info: Python 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 17:00:18) [MSC v.1900 64 bit (AMD64)] C:\Python36>pip show datetime Name: DateTime Version: 4.2 Summary: This package provides a DateTime data type, as known from Zope 2. Unless you need to communicate with Zope 2 APIs, you're probably better off using Python's built-in datetime module. Home-page: http://pypi.python.org/pypi/DateTime Author: Zope Foundation and Contributors Author-email: zope-dev(a)zope.org License: ZPL 2.1 Location: c:\python36\lib\site-packages Requires: zope.interface, pytz I tried first to use Python's built-in datetime module as follows: from datetime import date, timedelta d0 = date(2018,02,01) This gave the following error: Syntax Error: invalid token: C:\Users\Virgil Stokes\Desktop\Important Notes_Files\CheckProcessingDate_02.py, line 7, pos 17 d0 = date(2018,02,01) Then I used pip to install the datetime module and the same error occurred! However, when I removed the leading 0's no syntax error was reported and the correct result was returned. d0 = date(2018,2,1) Why does the datetime.date module (both built-in and site-package) not accept leading 0's?

5 4

Print Failure or success based on the value of the standalone tool
by Ganesh Pal May 10, 2018

May 10, 2018

I have to test a standalone tool from a python script and I am using os.system() to run the tool . I need to take decision based on the return value of the standalone tool . But since os.system merely throws the output value to STDOUT & returns the exit status (0 => no error) of the shell , how can I make this print Fail or Pass based on the return value of the standalone tool. In the below example ( return_values() function) Example: # cat standalone_tool.py #!/usr/bin/env python # script name: standalone_tool.py import random def return_values(): """ My Demo function""" # After Execution the actual tools returns True, False, None as return types x = random.choice([True, False, None]) print x return x return_values() >>> ret = os.system('python standalone_tool.py') True >>> ret 0 # vi test_standalone_tool.py #!/usr/bin/env python import os # script name: test_standalone_tool.py for i in range(2): retcode = os.system('python standalone_tool.py') print retcode if retcode: print "The standalone tool returned False. Failure" else: print "The standalone tool returned True. Successful" 1# python test_standalone_tool.py None 0 The standalone tool returned True. Successful True 0 The standalone tool returned True. Successful The above problem is because we are referring to the exit status of the shell, Is there an easy way to print Failure or success based on the value returned by python standalone_tool.py . I am on Linux with Python 2.7 and sorry for the longish post Regards, Ganesh

1 0

Re: Leading 0's syntax error in datetime.date module (Python 3.6)
by AK May 10, 2018

May 10, 2018

On 2018-05-10 13:52, D'Arcy Cain wrote: > On 2018-05-10 07:39 AM, AK wrote: >> Try (should work from both PY2 and PY3): >> >> d0 = date(2018,0o2,0o1) > > Bad advice. Those numbers are decimal, not octal, You should use > "date(2018,2,1)" here. Works in PY2, PY3 and for my birthday, Sept 4. It was only an evidence that it was PY3/PY2 compatibility issue - not a solution/correct way. Of course simple use of decimal constants like date(2018, 2, 1) is most correct. AK

1 0

Re: Leading 0's syntax error in datetime.date module (Python 3.6)
by AK May 10, 2018

May 10, 2018

On 2018-05-10 12:43, Virgil Stokes wrote: > Module info: > > Python 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 17:00:18) [MSC v.1900 64 > bit (AMD64)] [...] > I tried first to use Python's built-in datetime module as follows: > > from datetime import date, timedelta > > d0 = date(2018,02,01) > > This gave the following error: > > Syntax Error: invalid token: C:\Users\Virgil Stokes\Desktop\Important > Notes_Files\CheckProcessingDate_02.py, line 7, pos 17 > d0 = date(2018,02,01) > > Then I used pip to install the datetime module and the same error > occurred! However, when I removed the leading 0's no syntax error was > reported and the correct result was returned. It is not a datetime problem. It is PY3 compatibility problem. Try (should work from both PY2 and PY3): d0 = date(2018,0o2,0o1) AK

2 1

Problems after upgrading Python 3.6.3 to 3.6.5
by Jim May 9, 2018

May 9, 2018

I am running Linux Mint 18.1 and Python3 version 3.5.2, Awhile ago I installed Python3.6 from LP-PPA-jonathonf-python-3.6/now. I did it to run 3.6 in virtual environment. Everything was working until I allowed the package manager to upgrade 3.6.3 to 3.6.5. See (1) below. First problem I had was pip would not run. I solved that problem with help from another forum. Then I discovered I could not import tkinter in my 3.6 EV. At the end of the error message (2) it said to install python3-tk. After i did so I could import tkinter in 3.6 but not the default system python3.5. At this point I checked the log (1) and saw that python3-tk had been removed. Looking at the installed version of python3-tk it now said 3.6.5~16.04.york0.2. So does the version matter between python3.5 and 3.6 or do I just have some kind of path problem. At this point I am somewhat lost as to how to get tkinter working again in 3.5. Regards, Jim (1) Commit Log for Thu May 3 13:26:38 2018 Removed the following packages: python3-tk Upgraded the following packages: libpython3.6-minimal (3.6.3-1ubuntu1~16.04.york1) to 3.6.5-5~16.04.york0 libpython3.6-stdlib (3.6.3-1ubuntu1~16.04.york1) to 3.6.5-5~16.04.york0 python3.6 (3.6.3-1ubuntu1~16.04.york1) to 3.6.5-5~16.04.york0 python3.6-minimal (3.6.3-1ubuntu1~16.04.york1) to 3.6.5-5~16.04.york0 python3.6-venv (3.6.3-1ubuntu1~16.04.york1) to 3.6.5-5~16.04.york0 Commit Log for Fri May 4 14:32:44 2018 Upgraded the following packages: python3-gdbm (3.6.3-0ubuntu1~16.04.york0) to 3.6.5-3~16.04.york0.2 Commit Log for Sun May 6 09:28:25 2018 Installed the following packages: python3-tk (3.6.5-3~16.04.york0.2) Commit Log for Sun May 6 11:42:31 2018 Installed the following packages: libexpat1-dev (2.1.0-7ubuntu0.16.04.3) libpython3-dev (3.5.1-3) libpython3.5-dev (3.5.2-2ubuntu0~16.04.4) python3-dev (3.5.1-3) python3.5-dev (3.5.2-2ubuntu0~16.04.4) (2) jfb@jims-mint18 ~ $ python3 Python 3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import tkinter Traceback (most recent call last): File "/usr/lib/python3.5/tkinter/__init__.py", line 36, in <module> import _tkinter ImportError: No module named '_tkinter' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3.5/tkinter/__init__.py", line 38, in <module> raise ImportError(str(msg) + ', please install the python3-tk package') ImportError: No module named '_tkinter', please install the python3-tk package >>>

1 0

EuroPython 2018: Ticket Sales Update
by M.-A. Lemburg May 9, 2018

May 9, 2018

Some community members have been wondering why tickets are not available yet. We’d like to update you on the current status. EuroPython is run by the EuroPython Society located in Sweden. However, the conference being held in the UK, we have to charge UK VAT for the tickets we sell and submit the collected VAT to the UK tax authorities. In order to be able to do this, we have register with the UK tax authorities and this is where we have experienced unforseen delays. After several attempts at getting this sorted, our friends at PyCon UK have helped us find a capable accountant with whom we are currently implementing the registration. Hopefully, the tax authorities won’t take too long to issue us a UK VAT ID. As soon as we have it, we will start ticket sales. Ticket Prices Available ----------------------- That said, we do already have some more information for you: we have decided on the initial ticket prices for EuroPython 2018. In case you need budget approval from your employer, you may put in your request now. Please see our blog post or registration page for full details on the ticket pricing: * https://blog.europython.eu/post/173732504642/europython-2018-ticket-sales-u… * https://ep2018.europython.eu/en/registration/buy-tickets/ Enjoy, -- EuroPython 2018 Team https://ep2018.europython.eu/ https://www.europython-society.org/ PS: Please forward or retweet to help us reach all interested parties: https://twitter.com/europython/status/994182851997421569 Thanks.

1 0

Re: Problem/bug with class definition inside function definition
by Gregory Ewing May 8, 2018

May 8, 2018

Alexey Muranov wrote: > x = 42 > > class C: > x = x # Works I'd say it kind of works by accident, and is not really an intended feature. > if Python does not allow to refer "simultaneously" to > variables from different scopes if they have the same name. It seems perfectly reasonable to me to have to use different names to refer to different things in the same context. :-) -- Greg

1 0

Re: Module, Package
by Sharan Basappa May 8, 2018

May 8, 2018

On Tuesday, 8 May 2018 13:05:58 UTC+5:30, Steven D'Aprano wrote: > On Mon, 07 May 2018 09:53:45 -0700, Sharan Basappa wrote: > > > I am a bit confused between module and package in Python. Does a module > > contain package or vice versa? When we import something in Python, do we > > import a module or a package? > > The term "module" in Python has multiple meanings: > > - a particular kind of object, types.ModuleType > > - a single importable .py, .pyc etc file > > A package is a logical collection of importable .py etc files, usually > collected inside a single directory. When you import a module of a > package, that gives you a module object. > > Normally we would say that packages contain modules. For example, if you > have this file structure: > > > library/ > +-- __init__.py # special file which defines a package > +-- widgets.py > +-- stuff/ > +-- __init__.py > +-- things.py > > > then we have a package "library", which in turn contains a submodule > "library.widgets", and a subpackage "library.stuff", which in turn > contains a submodule "library.stuff.things". > > Each of these lines imports a module object: > > import library > import library.stuff > import library.stuff.things > import library.widgets > > from library import widgets > from library.stuff import things > > > Effectively, "packages" relates to how you arrange the files on disk; > "modules" relates to what happens when you import them. > > > -- > Steve Wow! Thanks a lot.

1 0