Git Product home page Git Product logo

Comments (5)

platomav avatar platomav commented on September 24, 2024 1

In my experience, the safest way to get most pre-existing python projects to work, is to manually download and use the installer from the official python website.

The python versions installed by Windows (e.g. store, WSL etc) exhibit weird behaviors when it comes to "path" environment variables, python executable alias names and more. Some more info about this can be found at another project of mine, in case it helps: platomav/MEAnalyzer#41.

But in general, uninstall whatever built-in python is there and re-install using the official offline installer from the python website. This has never failed me at Windows 11 x64 and latest (as of now) Python 3.11 releases.

Also, make sure to call/run the utilities from the repo/project root folder, not outside. This is a different python-related annoyance, which has to do with the (badly designed, IMHO) import/packaging system in Python 3. I will attempt to fix that, as good as I can, at an upcoming release (reference).

from biosutilities.

platomav avatar platomav commented on September 24, 2024

Python 3.10 or newer is required, as explained at the README for the project. There is no "common" module, it's a folder which accompanies the script, which is probably missing in your case for whatever reason. Closing this as it is not an issue with the repository code.

from biosutilities.

dribgnikcom avatar dribgnikcom commented on September 24, 2024

Thanks, I thought so and tried with the folder present (i.e. downloaded the whole project as a zip)... But I'll need to check if this is a global path directive issue in Windows.

from biosutilities.

mikebeaton avatar mikebeaton commented on September 24, 2024

This is not working for me with standard Windows python3, not even with PYTHONPATH (set to . or to full project directory), but it is working, without needing PYTHONPATH, if I install and use python3.10 on WSL.

from biosutilities.

67113513 avatar 67113513 commented on September 24, 2024

I faced same issue, and fix it by moving common to bioscommon and changing all 'import common.' to 'import bioscommon.'. Guess there is a system package also named 'common' on somewhere.

from biosutilities.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.