Open Bugzey opened 1 year ago
@Bugzey it does specify that OS is only windows in the pyproject.toml. Good call out though and I will add that specification to the README. I welcome any insights to get it compatible with other OS. Current use cases work fine in windows vms. I've currently got Azure Pipelines running for my requirements.
Added disclaimer and put 'windows' tag in top right tags. Converting to Enhancement with hope that some smart people will take a look at it.
My initial run had for some reason installed and imported a different clr
library - https://pypi.org/project/clr/. Why doesn't pythonnet just define pythonnet? Anyway, the package now imports correctly, and I can import objects from Microsoft.AnalysisServices
.
Now I'd love to at least get the tests running, but I can't figure out what the import local
line in tests.test_tabular
actually imports. Can you please clarify what that is? Link
PS: My tests don't necessarily prove Linux compatibility yet since I'm not sure why pythonnet and misc C# code is successfully running on my system. I most probably have some remnant Mono or other Microsoft tools installed as part of other packages. Optimally, we should set up the package and run the tests on a blank virtual machine in order to test out exactly what needs to be set up to get this package up and running.
local is a workaround I have so I could continue testing and moving this forward. I have #10 to get rid of that workaround. Because local contains info to get connected to my local models (an AAS model and Gen2 model).
My thoughts are getting an AdventureWorks DB and Model spun up when running tests? Then run the tests off that? What do you think? Rather than having the user needing to supply their own model.
Looking at all the local
references though... I can git rid of the need for local.SINGLEVALTESTPATH
and local.DFVALTESTPATH
because those are just file paths to the existing .dax files in the repo in the test folder.
Which means all that is left is solving a universal Tabular model for the test to run on.
Describe the bug Running the provided test suite produces an error with importing
clr
with Python 3.10 and Manjaro Linux. If we try importing the package from an interactive Python shell, the error is more specific about theclr
package not having anAddReference
attribute. Logs attachedTo Reproduce
pytest
Expected behavior Tests load correctly and start running.
Screenshots (None)
Desktop (please complete the following information):
Additional context Seeing that the module comes bundled with
.dll
files led me to believe that this package was never meant to run under anything other than Microsoft Windows even though any automation of data processes would likely be carried out by data engineers, developed and tested under Linux or the Windows Subsystem for Linux (WSL), and deployed to some cloud service such as functions, app services, containers or virtual machines. All of those predominantly run Linux. The current package should either try to support and test on such systems or explicitly state that they are unsupported in the README file.Pytest log:
Import log: