ModuleNotFoundError: No module named 'aspose' after upgrading aspose-total-net (May 2026 release)

Aspose.Total Product Family
,
1

Hi Team,

We are using the licensed version of Aspose.Total for Python via .NET (aspose-total-net) in an Azure Functions application running inside a Docker container.

After upgrading to the latest package version released around 21 May 2026, we started encountering a runtime error that was not present in previous versions.

Error

import aspose.words as awModuleNotFoundError: No module named 'aspose'

Environment

  • Product: Aspose.Total for Python via .NET
  • Licensed version
  • Azure Functions (Python)
  • Docker-based deployment
  • Python 3.10
  • Linux container

Exception Details

Exception while executing functionFile "/home/site/wwwroot/ExtractContentText/__init__.py", line 10, in <module>    import aspose.words as awModuleNotFoundError: No module named 'aspose'

Additional Information

  • The Docker image builds successfully.
  • The issue occurs only at runtime when the Azure Function starts.
  • We did not have this problem before upgrading to the latest Aspose.Total package.
  • Rolling back to an earlier version appears to resolve the issue.

Questions

  1. Has anyone else experienced this issue after upgrading to the latest aspose-total-net release?
  2. Were there any packaging, dependency, or module namespace changes introduced in the recent release?
  3. Is there a known compatibility issue with Azure Functions or Linux Docker containers?
  4. Are there any additional runtime dependencies that now need to be installed?

Any guidance would be appreciated.

1301×495 115 KB

2

@ajaiprakash Aspose.Total consists of separate Aspose products. Please try installing the required products separately:

pip install aspose-words
3

Hi @alexey.noskov ,

Thanks for such quick response,
But maintaining without version has become a difficult as there are multiple environments.

Can you tell me how to install multiple packages with their proper versions compatibility

4

@ajaiprakash I am afraid, the only way to work the problem around is installing the packages one by one. Aspose.Total team is aware about the problem with the total package and is working on resolving it. Please accept our apologies for your inconvenience.