Files.com 2.0.4__tar.gz → 2.0.6__tar.gz

{files_com-2.0.4/files_com.egg-info → files_com-2.0.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: files_com
-Version: 2.0.4
+Version: 2.0.6
 Summary: Python bindings for the Files.com API
 License-Expression: MIT
 Project-URL: Documentation, https://developers.files.com/python/
@@ -18,7 +18,7 @@ Requires-Dist: requests<3,>=2.34.2
 Requires-Dist: requests-toolbelt<2,>=1.0.0
 Requires-Dist: urllib3<3,>=2.8.0
 Requires-Dist: idna<4,>=3.15
-Requires-Dist: certifi>=2026.7.22
+Requires-Dist: certifi>=2026.10.19
 Requires-Dist: charset-normalizer<4,>=3.5.1
 Dynamic: license-file
 
@@ -37,6 +37,8 @@ is a short, runnable tour of the SDK.
 
 ## Introduction
 
+For integration choices and credential scope, start with [SDKs & APIs](https://www.files.com/docs/clients-and-protocols/sdks-and-apis). [Scripts, APIs & Application Workflows](https://www.files.com/docs/automated-workflows/scripts-apis-and-application-workflows) explains how to coordinate Files.com operations with the work your application owns.
+
 The Files.com Python SDK manages files, folders, users, permissions and other API resources. Start by installing the package, then choose [Authentication](/python/overview/authentication) and a [Client](/python/overview/clients). For file transfers, begin with [Uploads](/python/overview/uploads) or [Downloads](/python/overview/downloads).
 
 The SDK communicates over HTTPS on port 443. Your environment needs outbound access to Files.com and the storage hosts used for transfers.
@@ -67,7 +69,7 @@ Explore the [files-sdk-python](https://github.com/Files-com/files-sdk-python) co
 
 The Files.com Support team provides official support for all of our official Files.com integration tools.
 
-To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/overview/requesting-support) or simply send an E-Mail to support@files.com.
+To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/support-and-services/requesting-support) or simply send an E-Mail to support@files.com.
 
 ## Authentication
 
@@ -79,12 +81,10 @@ Authenticating with an API key is the recommended authentication method for most
 the method used in the examples on this site.
 
 To use an API Key, first generate an API key from the [web
-interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
+interface](https://www.files.com/docs/security/authentication-and-credentials/api-keys) or [via the API or an
 SDK](https://developers.files.com/python/resources/developers/api-keys).
 
-Note that when using a user-specific API key, if the user is an administrator, you will have full
-access to the entire API. If the user is not an administrator, you will only be able to access files
-that user can access, and no access will be granted to site administration functions in the API.
+A user key follows its account's permissions, narrowed by the key's permission scope, Workspace, and any path restriction on file operations. It can perform administrative operations only when both the account and key permit them. [API Keys](https://www.files.com/docs/security/authentication-and-credentials/api-keys) explains credential scope and lifecycle; [Workspaces](https://developers.files.com/python/overview/workspaces) explains request context and delegated administration.
 
 ```python title="Example Request"
 import files_sdk
@@ -104,10 +104,7 @@ Don't forget to replace the placeholder, `YOUR_API_KEY`, with your actual API ke
 
 ### Authenticate with a Session
 
-You can also authenticate by creating a user session using the username and
-password of an active user. If the user is an administrator, the session will have full access to
-all capabilities of Files.com. Sessions created from regular user accounts will only be able to access files that
-user can access, and no access will be granted to site administration functions.
+Create a session with the username and password of an active user. The session uses that user's permissions, including any delegated administrative access. [Workspaces](https://developers.files.com/python/overview/workspaces) describes account scope and administrative access.
 
 Sessions use the exact same session timeout settings as web interface sessions. When a
 session times out, simply create a new session and resume where you left off. This process is not
@@ -592,7 +589,7 @@ This behavior applies across:
 - Folder and file lookup operations
 - Automations and workflows
 
-See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
+See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/file-system-semantics/case-sensitivity)
 
 The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
 your native file system would be considered the same on Files.com. This is particularly important

{files_com-2.0.4 → files_com-2.0.6}/README.md

@@ -13,6 +13,8 @@ is a short, runnable tour of the SDK.
 
 ## Introduction
 
+For integration choices and credential scope, start with [SDKs & APIs](https://www.files.com/docs/clients-and-protocols/sdks-and-apis). [Scripts, APIs & Application Workflows](https://www.files.com/docs/automated-workflows/scripts-apis-and-application-workflows) explains how to coordinate Files.com operations with the work your application owns.
+
 The Files.com Python SDK manages files, folders, users, permissions and other API resources. Start by installing the package, then choose [Authentication](/python/overview/authentication) and a [Client](/python/overview/clients). For file transfers, begin with [Uploads](/python/overview/uploads) or [Downloads](/python/overview/downloads).
 
 The SDK communicates over HTTPS on port 443. Your environment needs outbound access to Files.com and the storage hosts used for transfers.
@@ -43,7 +45,7 @@ Explore the [files-sdk-python](https://github.com/Files-com/files-sdk-python) co
 
 The Files.com Support team provides official support for all of our official Files.com integration tools.
 
-To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/overview/requesting-support) or simply send an E-Mail to support@files.com.
+To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/support-and-services/requesting-support) or simply send an E-Mail to support@files.com.
 
 ## Authentication
 
@@ -55,12 +57,10 @@ Authenticating with an API key is the recommended authentication method for most
 the method used in the examples on this site.
 
 To use an API Key, first generate an API key from the [web
-interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
+interface](https://www.files.com/docs/security/authentication-and-credentials/api-keys) or [via the API or an
 SDK](https://developers.files.com/python/resources/developers/api-keys).
 
-Note that when using a user-specific API key, if the user is an administrator, you will have full
-access to the entire API. If the user is not an administrator, you will only be able to access files
-that user can access, and no access will be granted to site administration functions in the API.
+A user key follows its account's permissions, narrowed by the key's permission scope, Workspace, and any path restriction on file operations. It can perform administrative operations only when both the account and key permit them. [API Keys](https://www.files.com/docs/security/authentication-and-credentials/api-keys) explains credential scope and lifecycle; [Workspaces](https://developers.files.com/python/overview/workspaces) explains request context and delegated administration.
 
 ```python title="Example Request"
 import files_sdk
@@ -80,10 +80,7 @@ Don't forget to replace the placeholder, `YOUR_API_KEY`, with your actual API ke
 
 ### Authenticate with a Session
 
-You can also authenticate by creating a user session using the username and
-password of an active user. If the user is an administrator, the session will have full access to
-all capabilities of Files.com. Sessions created from regular user accounts will only be able to access files that
-user can access, and no access will be granted to site administration functions.
+Create a session with the username and password of an active user. The session uses that user's permissions, including any delegated administrative access. [Workspaces](https://developers.files.com/python/overview/workspaces) describes account scope and administrative access.
 
 Sessions use the exact same session timeout settings as web interface sessions. When a
 session times out, simply create a new session and resume where you left off. This process is not
@@ -568,7 +565,7 @@ This behavior applies across:
 - Folder and file lookup operations
 - Automations and workflows
 
-See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
+See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/file-system-semantics/case-sensitivity)
 
 The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
 your native file system would be considered the same on Files.com. This is particularly important

{files_com-2.0.4 → files_com-2.0.6/files_com.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: files_com
-Version: 2.0.4
+Version: 2.0.6
 Summary: Python bindings for the Files.com API
 License-Expression: MIT
 Project-URL: Documentation, https://developers.files.com/python/
@@ -18,7 +18,7 @@ Requires-Dist: requests<3,>=2.34.2
 Requires-Dist: requests-toolbelt<2,>=1.0.0
 Requires-Dist: urllib3<3,>=2.8.0
 Requires-Dist: idna<4,>=3.15
-Requires-Dist: certifi>=2026.7.22
+Requires-Dist: certifi>=2026.10.19
 Requires-Dist: charset-normalizer<4,>=3.5.1
 Dynamic: license-file
 
@@ -37,6 +37,8 @@ is a short, runnable tour of the SDK.
 
 ## Introduction
 
+For integration choices and credential scope, start with [SDKs & APIs](https://www.files.com/docs/clients-and-protocols/sdks-and-apis). [Scripts, APIs & Application Workflows](https://www.files.com/docs/automated-workflows/scripts-apis-and-application-workflows) explains how to coordinate Files.com operations with the work your application owns.
+
 The Files.com Python SDK manages files, folders, users, permissions and other API resources. Start by installing the package, then choose [Authentication](/python/overview/authentication) and a [Client](/python/overview/clients). For file transfers, begin with [Uploads](/python/overview/uploads) or [Downloads](/python/overview/downloads).
 
 The SDK communicates over HTTPS on port 443. Your environment needs outbound access to Files.com and the storage hosts used for transfers.
@@ -67,7 +69,7 @@ Explore the [files-sdk-python](https://github.com/Files-com/files-sdk-python) co
 
 The Files.com Support team provides official support for all of our official Files.com integration tools.
 
-To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/overview/requesting-support) or simply send an E-Mail to support@files.com.
+To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/support-and-services/requesting-support) or simply send an E-Mail to support@files.com.
 
 ## Authentication
 
@@ -79,12 +81,10 @@ Authenticating with an API key is the recommended authentication method for most
 the method used in the examples on this site.
 
 To use an API Key, first generate an API key from the [web
-interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
+interface](https://www.files.com/docs/security/authentication-and-credentials/api-keys) or [via the API or an
 SDK](https://developers.files.com/python/resources/developers/api-keys).
 
-Note that when using a user-specific API key, if the user is an administrator, you will have full
-access to the entire API. If the user is not an administrator, you will only be able to access files
-that user can access, and no access will be granted to site administration functions in the API.
+A user key follows its account's permissions, narrowed by the key's permission scope, Workspace, and any path restriction on file operations. It can perform administrative operations only when both the account and key permit them. [API Keys](https://www.files.com/docs/security/authentication-and-credentials/api-keys) explains credential scope and lifecycle; [Workspaces](https://developers.files.com/python/overview/workspaces) explains request context and delegated administration.
 
 ```python title="Example Request"
 import files_sdk
@@ -104,10 +104,7 @@ Don't forget to replace the placeholder, `YOUR_API_KEY`, with your actual API ke
 
 ### Authenticate with a Session
 
-You can also authenticate by creating a user session using the username and
-password of an active user. If the user is an administrator, the session will have full access to
-all capabilities of Files.com. Sessions created from regular user accounts will only be able to access files that
-user can access, and no access will be granted to site administration functions.
+Create a session with the username and password of an active user. The session uses that user's permissions, including any delegated administrative access. [Workspaces](https://developers.files.com/python/overview/workspaces) describes account scope and administrative access.
 
 Sessions use the exact same session timeout settings as web interface sessions. When a
 session times out, simply create a new session and resume where you left off. This process is not
@@ -592,7 +589,7 @@ This behavior applies across:
 - Folder and file lookup operations
 - Automations and workflows
 
-See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
+See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/file-system-semantics/case-sensitivity)
 
 The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
 your native file system would be considered the same on Files.com. This is particularly important

{files_com-2.0.4 → files_com-2.0.6}/files_com.egg-info/requires.txt

@@ -2,5 +2,5 @@ requests<3,>=2.34.2
 requests-toolbelt<2,>=1.0.0
 urllib3<3,>=2.8.0
 idna<4,>=3.15
-certifi>=2026.7.22
+certifi>=2026.10.19
 charset-normalizer<4,>=3.5.1

{files_com-2.0.4 → files_com-2.0.6}/files_sdk/__init__.py

@@ -479,7 +479,7 @@ source_ip = None
 workspace_id = None
 base_url = "https://app.files.com"
 base_path = "api/rest/v1"
-version = "2.0.4"
+version = "2.0.6"
 
 __version__ = version
 

{files_com-2.0.4 → files_com-2.0.6}/files_sdk/localfs.py

@@ -178,10 +178,15 @@ class Directory:
         path, dir_fd = self._at(name)
         os.rmdir(path, dir_fd=dir_fd)
 
+    def renames_by_path(self, target):
+        """Whether rename_into goes by path names, where directories are not
+        held open (Windows)."""
+        return self.fd is None or target.fd is None
+
     def rename_into(self, name, target, target_name):
         """Rename name here to target_name in the directory target,
         replacing what is there."""
-        if self.fd is None or target.fd is None:
+        if self.renames_by_path(target):
             os.replace(self.join(name), target.join(target_name))
             return
         os.rename(name, target_name, src_dir_fd=self.fd, dst_dir_fd=target.fd)
@@ -452,10 +457,54 @@ class Stage:
             os.chmod(self.private.join(self.file_name), mode)
         if not self._is_ours():
             raise ReplacedStage(self.private.join(self.file_name))
-        self.private.rename_into(self.file_name, self.parent, target_name)
-        self.close()
+        if self.private.renames_by_path(self.parent):
+            # Windows does not rename a file this process holds open: os.open
+            # does not share deletion. The file is closed first, and opened
+            # again if it is not renamed, so that a checkpoint can still sync
+            # and keep it.
+            self.close()
+            try:
+                self.private.rename_into(
+                    self.file_name, self.parent, target_name
+                )
+            except BaseException as error:
+                self._reopen(error)
+                raise
+        else:
+            self.private.rename_into(self.file_name, self.parent, target_name)
+            self.close()
         self._remove_private()
 
+    def _reopen(self, error):
+        """Open the file again after it was closed to be renamed and was not
+        (error is why), if it is still the SDK's own; otherwise it stays
+        closed, with a note on error saying why. Nothing here is raised in
+        place of error."""
+        path = self.private.join(self.file_name)
+        try:
+            fd = self.private.open_file(self.file_name, os.O_RDWR)
+        except OSError as problem:
+            error.add_note(
+                "The temporary file {} could not be opened again: {}".format(
+                    path, problem
+                )
+            )
+            return
+        try:
+            mine = identity_of(os.fstat(fd)) == self.file_identity
+        except OSError:
+            mine = False
+        if mine:
+            self.fd = fd
+            return
+        try:
+            os.close(fd)
+        except OSError:
+            pass
+        error.add_note(
+            "The temporary file {} is no longer the SDK's own".format(path)
+        )
+
     def close(self):
         fd, self.fd = self.fd, -1
         if fd >= 0:
@@ -502,12 +551,24 @@ def _exposed(private, directory, fd, found):
     its status) or its private directory (directory is its status) has
     since become usable by others: by the directory's or the file's
     permissions, the file's owner, or on macOS an access control list on
-    either. Whoever opened it meanwhile keeps what they opened, however the
+    either. Windows permissions show only whether an item is read-only, so
+    there it is by owners and access control lists (see files_sdk.access):
+    the file's must let no one but this user, the system or administrators
+    use it, and the private directory and every folder above it must let no
+    one else delete, replace or re-permission them or what is in them, nor
+    be a link or junction; what cannot be read counts as usable by others.
+    Whoever opened it meanwhile keeps what they opened, however the
     permissions are changed back, so such a file is never resumed."""
+    if sys.platform == "win32":
+        try:
+            return (
+                access.namespace_problem(private.path) is not None
+                or access.new_file_problem(fd, "temporary file") is not None
+            )
+        except OSError:
+            return True
     if stat.S_IMODE(directory.st_mode) & 0o077:
         return True
-    if sys.platform == "win32":
-        return False
     if stat.S_IMODE(found.st_mode) & 0o077 or found.st_uid != os.geteuid():
         return True
     return private.fd is not None and (

{files_com-2.0.4 → files_com-2.0.6}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "files_com"
-version = "2.0.4"
+version = "2.0.6"
 description = "Python bindings for the Files.com API"
 readme = "README.md"
 license = "MIT"
@@ -19,7 +19,7 @@ dependencies = [
     "requests-toolbelt>=1.0.0,<2",
     "urllib3>=2.8.0,<3",
     "idna>=3.15,<4",
-    "certifi>=2026.7.22",
+    "certifi>=2026.10.19",
     "charset-normalizer>=3.5.1,<4",
 ]
 classifiers = [