Files.com 1.4.120__tar.gz → 1.4.122__tar.gz

{Files.com-1.4.120 → Files.com-1.4.122}/Files.com.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: Files.com
-Version: 1.4.120
+Version: 1.4.122
 Summary: Python bindings for the Files.com API
 Home-page: UNKNOWN
 License: MIT

{Files.com-1.4.120 → Files.com-1.4.122}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: Files.com
-Version: 1.4.120
+Version: 1.4.122
 Summary: Python bindings for the Files.com API
 Home-page: UNKNOWN
 License: MIT

{Files.com-1.4.120 → Files.com-1.4.122}/README.md

@@ -191,42 +191,6 @@ Configure the local IP address from which to send requests.
 files_sdk.source_ip = '10.1.2.3'
 ```
 
-### Logging
-
-The Files.com SDK is compatible with the standard log4j logging scheme.
-
-Add `com.files` logger to your `Loggers` root in the `log4j2.xml` file.
-
-```xml title="log4j2.xml"
-<Loggers>
-    <!-- set preferred level -->
-    <Logger name="com.files" level="TRACE" />
-    <!-- to enable network request -->
-    <Logger name="okhttp3.logging.wire" level="INFO"/>
-</Loggers>
-```
-
-Create a `resources/log4j2.xml` file.
-
-```xml title="resources/log4j2.xml"
-<?xml version="1.0" encoding="UTF-8"?>
-<Configuration>
-    <Appenders>
-        <Console name="Console" target="SYSTEM_OUT">
-            <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
-        </Console>
-    </Appenders>
-    <Loggers>
-        <!-- set preferred level -->
-        <Logger name="com.files" level="TRACE"/>
-        <!-- to enable network request -->
-        <Logger name="okhttp3.logging.wire" level="INFO"/>
-    </Loggers>
-</Configuration>
-```
-
-You can read more about [log4j2 configuration](https://logging.apache.org/log4j/2.x/manual/configuration.html).
-
 ## Errors
 
 The Files.com Python SDK will return errors by raising exceptions. There are many exception classes defined in the Files SDK that correspond

{Files.com-1.4.120 → Files.com-1.4.122}/files_sdk/__init__.py

@@ -204,7 +204,7 @@ session_id = None
 source_ip = None
 base_url = "https://app.files.com"
 base_path = "api/rest/v1"
-version = "1.4.120"
+version = "1.4.122"
 
 __version__ = version
 

{Files.com-1.4.120 → Files.com-1.4.122}/files_sdk/models/api_key.py

@@ -22,7 +22,7 @@ class ApiKey:
         "platform": None,  # string - If this API key represents a Desktop app, what platform was it created on?
         "url": None,  # string - URL for API host.
         "user_id": None,  # int64 - User ID for the owner of this API Key.  May be blank for Site-wide API Keys.
-        "path": None,  # string - Folder path restriction for this API key.
+        "path": None,  # string - Folder path restriction for `office_integration` permission set API keys.
     }
 
     def __init__(self, attributes=None, options=None):
@@ -203,7 +203,7 @@ def get(id, params=None, options=None):
 #   expires_at - string - API Key expiration date
 #   permission_set - string - Permissions for this API Key. It must be full for site-wide API Keys.  Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Additional permission sets may become available in the future, such as for a Site Admin to give a key with no administrator privileges.  If you have ideas for permission sets, please let us know.
 #   name (required) - string - Internal name for the API Key.  For your use.
-#   path - string - Folder path restriction for this API key.
+#   path - string - Folder path restriction for `office_integration` permission set API keys.
 def create(params=None, options=None):
     if not isinstance(params, dict):
         params = {}