DOCSLIB.ORG

Pyslet Documentation Release 0.7.20180305

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pyslet Documentation Release 0.7.20180305 Pyslet Documentation Release 0.7.20180305 Steve Lay Mar 05, 2018 Contents 1 What’s New? 1 2 Compatibility 11 3 IMS Global Learning Consortium Specifications 21 4 The Open Data Protocol (OData) 119 5 Hypertext Transfer Protocol (RFC2616) 231 6 Other Supporting Standards 279 7 Welcome to Pyslet 461 Python Module Index 465 i ii CHAPTER 1 What’s New? To improve PEP-8 compliance a number of name changes are being made to methods and class attributes with each release. There is a module, pyslet.pep8, which contains a compatibility class for remapping missing class attribute names to their new forms and generating deprecation warnings, run your code with “python -Wd” to force these warnings to appear. As Pyslet makes the transition to Python 3 some of the old names may go away completely. The warning messages explain any changes you need to make. Although backwards compatible, using the new names is slightly faster as they don’t go through the extra deprecation wrapper. It is still possible that some previously documented names could now fail (module level functions, function arguments, etc.) but I’ve tried to include wrappers or aliases so please raise an issue on Github if you discover a bug caused by the renaming. I’ll restore any missing old-style names to improve backwards compatibility on request. 1.1 Version Numbering Pyslet version numbers use the check-in date as their last component so you can always tell if one build is newer than another. At the moment there is only one actively maintained branch of the code: version ‘0”. Changes are reported against the versions released to PyPi. The main version number increases with each PyPi release. Starting with version 0.7 changes are documented in order of build date to make it easier to see what is changing in the master branch on GitHub. Not sure which version you are using? Try: from pyslet.info import version print version 1.2 Version 0.8 TBC 1 Pyslet Documentation, Release 0.7.20180305 1.3 Version 0.7.20170805 1.3.1 Summary of new features Pyslet now supports Python 3, all tests are passing in Python 3. Travis now builds and tests Python 2.7 and Python 3.5, I’ve dropped 2.6 from the continuous integration testing because the latest Ubuntu images have dropped Python2.6 but you can still run tox on your own environments as it includes 2.6 in tox.ini. Various bug fixes in OData and HTTP code. Warning: for future compatibility with Python 3 you should ensure that you use the bytes type (and the ‘b’ prefix on any string constants) when initialising OData entity properties of type Edm.Binary. Failure to do so will raise an error in Python 3. 1.3.2 Tracked issues The following issues are resolved (or substantially resolved) in this release. #3 PEP-8 Compliance The pep8-regression.py script now checks all source files using flake8; all reported errors have been resolved Added a new metaclass-based solution to enable method renaming while maintaining support for derived classes that override using the old names. Crazy I know, but it works. #12 Bug in odata2/sqlds.py Bug when using numeric or named parameters in DB API. Added support for pyformat in DB APIs as part of enabling support for PyMySQL. #23 Framework for WSGI-based LTI Applications (beta quality) Re-engineered Session support in the wsgi module to reduce database load, replacing the Session table completely with signed cookies. If you have used the wsgi.SessionApp class directly this will be a breaking change but these classes will remain experimental until this item is closed out. The database schema required to support LTI has changed slightly as a result. Changed from Django templates to use Jinja2 (this requires almost no changes to the actual sample code templates and makes the intention of the samples much clearer). Thanks to Christopher Lee for recommending this change. Possible breaking change to wsgi module to refactor authority setting to “canonical_root”, modified WSGIContext object to accept an optional canonical_root argument and removed the optional authority argument from get_app_root and get_url. The authority setting was previously a misnomer and the wsgi sammples were not working properly with localhost. Changed wsgi module to use the OSFilePath wrapper for file paths for better compatibility with Posix file systems that use binary strings for file paths. This module was causing test failures due to some use of os.path module with mixed string types. #29 https connections fail on POST after remote server hangup The currently implemented solution is to allow an open ssl socket to be idle in the ‘blocked’ state for a maximum of 2s before sending a new request. After that time we tear down the socket and build a new one. This may now be a bit aggressive given the newer SSL behaviour (which differentiates issues in the underlying socket with different SSL exceptions). #30 Provide http connection clean-up thread 2 Chapter 1. What’s New? Pyslet Documentation, Release 0.7.20180305 The implementation is not as intelligent as I’d like it to be. The protocol version that a server last used is stored on the connection object and is lost when we clean up idle connections. Although it is likely that a new connection will speak the same protocol as the previous one there is little harm in going in to protocol detection mode again (we declare ourselves HTTP/1.1) other than the problem of using transfer encodings on an initial POST. In particular, we only drop out of keep-alive mode when the server has actually responded with an HTTP/1.0 response. #38 Make Pyslet run under Python 3 See above for details. #43 Fixes for Python running on Windows This issue came back again, both unicode file name problems and further problems due to timing in unittests. Fixed this time by mocking and monkey-patching the time.time function in the QTI tests. #47 Improve CharClass-derived doc strings Fixed - no functional changes. #49 Typo in pyslet/odata2/csdl.py Fixed OData serialisation of LongDescription element - thanks to @thomaseitler #51 Fix processing of dates in JSON format OData communication by the #server We now accept ISO string formatted dates for both DateTime and DateTimeOffset. Note that providing a timezone other than Z (+00:00) when setting a DateTime will cause the time to be zone-shifted to UTC before the value is set. Thanks to @ianwj5int. #53 Use datetime.date to create datetime object You can now set DateTimeValue using a standard python datetime.date, the value is extended to be 00:00:00 on that date. Thanks to @nmichaud #54 Fix use of super to remove self Fixed Atom Date handling bug, thanks to @nmichaud #55 Replace print_exception with logging (this includes the traceback) Thanks to @ianwj5int for reporting. #56 Garbage received when server delays response This was caused by a bug when handling 401 responses in HTTP client The issue affected any response that was received as a result of a resend (after a redirect or 401 response). The stream used to receive the data in the follow-up request was not being reset correctly and this resulted in a chunk of 0x00 bytes being written before the actual content. This bug was discovered following changes in the 20160209 build when StringIO was replaced with BytesIO for Python 3 compatibility. StringIO.truncate moves the stream pointer, BytesIO.truncate does not. As a result all resends where the 3xx or 401 response had a non-zero length body were being affected. Previously the bug only affected the rarer use case of resends of streamed downloads to real files, i.e., requests created by passing an open file in the res_body argument of ClientRequest. With thanks to @karurosu for reporting. #58 OData default values (PUT/PATCH/MERGE) Warning: if you use Pyslet for an OData server please check that PUTs are still working as required. Changed the SQL data stores to use DEFAULT values from the metadata file as part of the CREATE TABLE queries. Modified update_entity in memds, and SQL storage layers to use MERGE semantics by default, added option to enable replace (PUT) semantics using column defaults. This differs from the previous (incorrect behaviour) where unselected properties were set to NULL. 1.3. Version 0.7.20170805 3 Pyslet Documentation, Release 0.7.20180305 Updated OData server to support MERGE and ensured that PUT now uses the correct semantics (set to default instead of NULL) for values missing from the incoming request. Improved error handling to reduce log noise in SQL layer. #60 authentication example in docs Added a first cut at a documentation page for HTTP auth. #61 Add support for NTLM Experimental support for NTLM authentication now available using the python-ntlm3 module from pip/GitHub which must be installed before you can use NTLM. The module is in pyslet.ntlmauth and it can be used in a similar way to Basic auth (see set_ntlm_credentials for details.) Improved handling of error responses in all HTTP requests (includes a Python 3 bug fix) to enable the connection to be kept open more easily during pipelined requests that are terminated early by a final response from the server. This allows a large POST that generates a 401 response to abort sending of chunked bodies and retry without opening a new connection - vital for NTLM which is connection based. Added automated resend after 417 Expectation failed responses as per latest HTTP guidance. (Even for POST re- quests!) #64 Add a LICENSE file Added to distribution #65 syntax error in sqlds.SQLCollectionBase.sql_expression_substring Also added an override for SQLite given the lack of support for the standard substring syntax.
Load more

Recommended publications
  • Odata Services Company
    PUBLIC 2021-03-09 OData Services company. All rights reserved. All rights company. affiliate THE BEST RUN 2021 SAP SE or an SAP SE or an SAP SAP 2021 © Content 1 SAP Cloud for Customer OData API..............................................4 2 New Features.............................................................. 13 2.1 What's New in OData API v2 Reference.............................................13 2.2 Add Public Solution Model (PSM) Fields to Standard OData Services........................15 2.3 Transport Custom OData Services with Transport Management............................16 2.4 Compatibility Mode for READ Operations........................................... 16 2.5 Support for User-Friendly IDs in Standard OData Services................................16 2.6 Constant Values to Function Imports...............................................17 3 OData API Reference.........................................................18 3.1 OData API v2 Reference........................................................18 3.2 OData API v1 Reference (Deprecated)..............................................20 Account Contact Relationship.................................................21 Account EntityType........................................................22 Appointment Entity Type....................................................40 BusinessPartner Entity Type..................................................46 CodeList Entity Type....................................................... 47 Contextual CodeList Entity Type...............................................48
    [Show full text]
  • Pyslet Documentation Release 0.6.20160201
    Pyslet Documentation Release 0.6.20160201 Steve Lay February 02, 2016 Contents 1 What’s New? 1 2 Compatibility 7 3 IMS Global Learning Consortium Specifications 13 4 The Open Data Protocol (OData) 101 5 Hypertext Transfer Protocol (RFC2616) 207 6 Other Supporting Standards 247 7 Welcome to Pyslet 357 Python Module Index 359 i ii CHAPTER 1 What’s New? As part of moving towards PEP-8 compliance a number of name changes are being made to methods and class at- tributes with each release. There is a module, pyslet.pep8, which contains a compatibility class for remapping missing class attribute names to their new forms and generating deprecation warnings, run your code with “python -Wd” to force these warnings to appear. As Pyslet makes the transition to Python 3 some of the old names will go away completely. It is still possible that some previously documented names could now fail (module level functions, function arguments, etc.) but I’ve tried to include wrappers or aliases so please raise an issue on Github if you discover a bug caused by the renaming. I’ll restore any missing old-style names to improve backwards compatibility on request. Finally, in some cases you are encouraged to derive classes from those defined by Pyslet and to override default method implementations. If you have done this using old-style names you will have to update your method names to prevent ambiguity. I have added code to automatically detect most problems and force fatal errors at runtime on construction, the error messages should explain which methods need to be renamed.
    [Show full text]
  • ISO/IEC JTC 1 Information Technology
    ISO/IEC JTC 1 Information technology Big data Preliminary Report 2014 Our vision Our process To be the world’s leading provider of high Our standards are developed by experts quality, globally relevant International all over the world who work on a Standards through its members and volunteer or part-time basis. We sell stakeholders. International Standards to recover the costs of organizing this process and Our mission making standards widely available. ISO develops high quality voluntary Please respect our licensing terms and International Standards that facilitate copyright to ensure this system remains international exchange of goods and independent. services, support sustainable and equitable economic growth, promote If you would like to contribute to the innovation and protect health, safety development of ISO standards, please and the environment. contact the ISO Member Body in your country: www.iso.org/iso/home/about/iso_ members.htm This document has been prepared by: Copyright protected document ISO/IEC JTC 1, Information technology All rights reserved. Unless otherwise Cover photo credit: ISO/CS, 2015 be reproduced or utilized otherwise in specified,any form noor partby anyof this means, publication electronic may or mechanical, including photocopy, or posting on the internet or intranet, without prior permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester: © ISO 2015, Published in Switzerland Case postale 56 • CH-1211 Geneva 20 Tel.ISO copyright+41 22
    [Show full text]
  • Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, Proposes
    Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, proposes ○ Geodata on the web in raw form. ○ Raw geodata must be searchable How do you find raw geospatial data ? Data Catalogs Wouldn’t it be nice if… And see.. Searchable Raw Geospatial Data www.georest.org Open Data Protocol “The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today.” www.odata.org ODATA HTTP Atom AtomPUB JSON HTTP://.../vancouver/libraries <feed xmlns=http://www.w3.org/2005/Atom … > <title type="text">libraries</title> <id>http://…/vancouver/libraries(10)</id> <title type="text"></title> <entry> <content type="application/xml"> <m:properties> <d:library_name>Britannia</d:library_name> <d:latitude m:type="Edm.Double">49.2756486</d:latitude> <d:longitude m:type="Edm.Double">-123.0737717</d:longitude> <d:address>1661 Napier St</d:address> </m:properties> …..</entry> <entry>…</entry></feed> HTTP://.../vancouver/libraries ?$format=JSON {"d":[{"library_name":"Britannia","latitude":" 49.2756486","longitude":"- 123.0737717","address":"1661 Napier St"} , {..}] } HTTP Header accept: application/json OData Example Live OData Service from Vancouver OData Producers SharePoint 2010, SQL Azure, IBM WebSphere, … GeoREST OData Live Services Netflix, Open Goverment Data Initiative (OGDI), Stack Overflow, Vancouver, Edmonton, … City of Nanaimo OData Consumers Browsers, Odata Explorer, Excel 2010,…
    [Show full text]
  • SAP Analytics Cloud, Analytics Designer Developer Handbook
    SAP Analytics Cloud, analytics designer Developer Handbook Document Version: 5.1 – 2020-04-06 Table of Contents 1 Table of Contents Table of Contents ......................................................................................................................... 1 Figures .......................................................................................................................................... 7 1 About Analytics Designer .............................................................................................10 1.1 What Is an Analytic Application? .....................................................................................10 1.2 What Is Analytics Designer? ............................................................................................10 1.3 What Can You Do with Analytic Applications That You Can’t Do with Stories? ..............10 1.4 How Are Stories and Analytic Applications Related to Each Other? ...............................10 1.5 Why Do We Need Both Stories and Analytic Applications? ............................................11 1.6 What Is the Typical Workflow in Creating an Analytic Application? .................................11 1.7 What Are Typical Analytic Applications? .........................................................................12 1.8 How Does Scripting Work in Analytic Applications? ........................................................12 1.9 What’s the Scripting Language for Analytic Applications? ..............................................13 2 Getting
    [Show full text]
  • Catalogue Open Data Protocol (Odata API) User Guide
    Catalogue Open Data Protocol (OData API) User Guide Content 1. Introduction .......................................................................................................................................... 3 1.1. Purpose......................................................................................................................... 3 1.2. Change register ............................................................................................................. 3 1.3. Structure of the document ............................................................................................. 3 1.4. Acronyms ...................................................................................................................... 4 1.5. Reference Documents ................................................................................................... 4 2. Open Data Protocol overview ............................................................................................................. 6 2.1. Entity Data Model concept ............................................................................................ 6 Entity Type ..................................................................................................................... 7 Entity Set ....................................................................................................................... 7 3. ONDA OData Entity Data Model ......................................................................................................... 8 3.1. ONDA Entity
    [Show full text]
  • Deliverable D7.5: Standards and Methodologies Big Data Guidance
    Project acronym: BYTE Project title: Big data roadmap and cross-disciplinarY community for addressing socieTal Externalities Grant number: 619551 Programme: Seventh Framework Programme for ICT Objective: ICT-2013.4.2 Scalable data analytics Contract type: Co-ordination and Support Action Start date of project: 01 March 2014 Duration: 36 months Website: www.byte-project.eu Deliverable D7.5: Standards and methodologies big data guidance Author(s): Jarl Magnusson, DNV GL AS Erik Stensrud, DNV GL AS Tore Hartvigsen, DNV GL AS Lorenzo Bigagli, National Research Council of Italy Dissemination level: Public Deliverable type: Final Version: 1.1 Submission date: 26 July 2017 Table of Contents Preface ......................................................................................................................................... 3 Task 7.5 Description ............................................................................................................... 3 Executive summary ..................................................................................................................... 4 1 Introduction ......................................................................................................................... 5 2 Big Data Standards Organizations ...................................................................................... 6 3 Big Data Standards ............................................................................................................. 8 4 Big Data Quality Standards .............................................................................................
    [Show full text]
  • Blackbaud CRM Query and Export Guide
    Query and Export Guide 03/23/2016 Blackbaud CRM 4.0 Query and Export US ©2016 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, or mechanical, including photocopying, recording, storage in an information retrieval system, or otherwise, without the prior written permission of Blackbaud, Inc. The information in this manual has been carefully checked and is believed to be accurate. Blackbaud, Inc., assumes no responsibility for any inaccuracies, errors, or omissions in this manual. In no event will Blackbaud, Inc., be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect or omission in this manual, even if advised of the possibility of damages. In the interest of continuing product development, Blackbaud, Inc., reserves the right to make improvements in this manual and the products it describes at any time, without notice or obligation. All Blackbaud product names appearing herein are trademarks or registered trademarks of Blackbaud, Inc. All other products and company names mentioned herein are trademarks of their respective holder. QueryExport-2016 Contents Getting Started with Query 4 Query: A Guided Tour 4 Common Query Fields 20 Common Query Filters 22 Query 25 Information Library 27 Ad-Hoc Queries 27 Smart Queries 58 Selections 71 Copy an Existing Query 74 Export Queries 74 Browse Query Results 75 View Query Results 75 Organize Queries 75 Open Data Protocol (OData) 79 Export 82 Exports 82 Export Definitions 86 Export Process Status Page 100 Import Selections 106 Import Selections 106 Import Selection Process Status Page 110 chapter 1 Getting Started with Query Query: A Guided Tour 4 Common Query Fields 20 Constituent Query Fields 20 Revenue Query Fields 21 Registrant Query Fields 22 Common Query Filters 22 Constituent Query Filters 22 Revenue Query Filters 23 Registrant Query Filters 23 Query is a powerful tool you can use to help filter and group records.
    [Show full text]
  • Denodo Odata 2.0 Service User Manual
    Denodo OData 2.0 Service User Manual Revision 20200508 NOTE This document is confidential and proprietary of Denodo Technologies. No part of this document may be reproduced in any form by any means without prior written authorization of Denodo Technologies. Copyright © 2021 Denodo Technologies Proprietary and Confidential Denodo OData 2.0 Service User Manual 20200508 2 of 34 CONTENTS 1 OVERVIEW........................................................................5 2 INSTALLATION..................................................................6 2.1 DEPLOYING INTO THE DENODO EMBEDDED WEB CONTAINER............8 2.2 CONFIGURING JNDI RESOURCES IN APACHE TOMCAT......................10 3 VIRTUAL DATAPORT PRIVILEGE REQUIREMENTS.................12 4 FEATURES.......................................................................13 5 SERVING METADATA........................................................14 6 QUERYING DATA: THE BASICS..........................................16 6.1 QUERYING COLLECTIONS..............................................................16 6.2 OBTAINING ITEMS BY PRIMARY KEY..............................................16 6.3 ACCESSING INDIVIDUAL PROPERTIES............................................16 6.4 ACCESSING INDIVIDUAL PROPERTY VALUES...................................17 6.5 ACCESSING COMPLEX PROPERTIES...............................................17 6.6 COUNTING ELEMENTS IN A COLLECTION: $COUNT..........................18 6.7 ESTABLISHING RESPONSE FORMAT...............................................18 7 NAVIGATING
    [Show full text]
  • Information Technology — Open Data Protocol (Odata) V4.0
    BS ISO/IEC 20802-2:2016 BSI Standards Publication Information technology — Open data protocol (OData) v4.0 Part 2: OData JSON Format WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06 BS ISO/IEC 20802-2:2016 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 20802-2:2016. The UK participation in its preparation was entrusted to Technical Committee ICT/-/1, Information systems co-ordination. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. © The British Standards Institution 2017. Published by BSI Standards Limited 2017 ISBN 978 0 580 90961 0 ICS 35.100.70 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2017. Amendments/corrigenda issued since publication Date Text affected BS ISO/IEC 20802-2:2016 INTERNATIONAL ISO/IEC STANDARD 20802-2 First edition 2016-12-15 Information technology — Open data protocol (OData) v4.0 Part 2: OData JSON Format Technologies de l'information — Protocole de données ouvertes (OData) v4.0 — Partie 2: Format OData JSON Reference number ISO/IEC 20802-2:2016(E) © ISO/IEC 2016 BS ISO/IEC 20802-2:2016 ISO/IEC 20802-2:2016(E) COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2016 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
    [Show full text]
  • Supplement for Adapters DP Bridge, Hive, HTTP, JDBC, JMS, Mongodb, Odata, Salesforce.Com, Shapefile, and Successfactors Company
    PUBLIC SAP Data Services Document Version: 4.2 Support Package 12 (14.2.12.0) – 2020-02-06 Supplement for Adapters DP Bridge, Hive, HTTP, JDBC, JMS, MongoDB, OData, Salesforce.com, Shapefile, and SuccessFactors company. All rights reserved. All rights company. affiliate THE BEST RUN 2020 SAP SE or an SAP SE or an SAP SAP 2020 © Content 1 Naming Conventions......................................................... 5 2 Data Services adapters....................................................... 9 2.1 Adapter required knowledge and expertise...........................................11 3 Adapter installation and configuration...........................................12 3.1 Adding an adapter instance.....................................................13 3.2 Adapter Configuration options ...................................................14 JDBC adapter-specific configuration settings......................................19 DP Bridge runtime configuration options.........................................23 HTTP adapter specific configuration settings......................................24 JMS adapter-specific configuration settings.......................................25 3.3 Starting and stopping the adapter instance..........................................27 3.4 Monitoring the adapter instances and operations..................................... 28 3.5 Viewing adapter instance statistics................................................29 4 Creating an adapter datastore................................................. 31 5 Adapter datastore
    [Show full text]
  • Introducing Odata Data Access for the Web, the Cloud, Mobile Devices, and More
    David Chappell May 2011 INTRODUCING ODATA DATA ACCESS FOR THE WEB, THE CLOUD, MOBILE DEVICES, AND MORE Sponsored by Microsoft Corporation Copyright © 2011 Chappell & Associates Contents Describing OData ................................................................................................................................................ 3 The Problem: Accessing Diverse Data in a Common Way ......................................................................................3 The Solution: What OData Provides .......................................................................................................................3 How OData Works: Technology Basics ...................................................................................................................5 Using OData: Example Scenarios ......................................................................................................................... 6 Accessing Application Data from Mobile Phones and Web Browsers ....................................................................6 Exposing Data from a Cloud Application ................................................................................................................8 Using Diverse Data Sources with Different BI Tools ...............................................................................................9 Examining OData: A Closer Look at the Technology and Its Implementation .................................................... 10 The OData Data Model .........................................................................................................................................10
    [Show full text]