Why does dactyl_manuform.py assume nested directory?

[BansheeHero]

Build fails when importing parts while using a different config name.

I assume this is because I am running python outside of docker-build.

cd src/
python3 dactyl_manuform.py  --config FirstOne

Responsible code:

dactyl-keyboard/src/dactyl_manuform.py

Line 59 in 77b9ed3

parts_path = path.join(r"..", r"..", "src", "parts")

Seems the code assumes you are running it from some other directory just because you are using a different save_dir.

IMPORTING FROM ../../src/parts/trackball_socket_body_34mm
Traceback (most recent call last):
  File "dactyl_manuform.py", line 4249, in <module>
    run()
  File "dactyl_manuform.py", line 4202, in run
    mod_r, tmb_r = model_side(side="right")
  File "dactyl_manuform.py", line 4023, in model_side
    tbprecut, tb, tbcutout, sensor, ball = generate_trackball_in_cluster()
  File "dactyl_manuform.py", line 3316, in generate_trackball_in_cluster
    return generate_trackball(pos, rot)
  File "dactyl_manuform.py", line 3278, in generate_trackball
    shape, cutout, sensor = trackball_socket()
  File "dactyl_manuform.py", line 317, in trackball_socket
    shape = import_file(tb_file)
  File "/home/bansheehero/Repositories/dactyl-keyboard/src/helpers_cadquery.py", line 227, in import_file
    fname + ".step"))
  File "/home/bansheehero/.conda/envs/dactyl-keyboard/lib/python3.7/site-packages/cadquery/occ_impl/importers.py", line 45, in importShape
    return importStep(fileName, *args, **kwargs)
  File "/home/bansheehero/.conda/envs/dactyl-keyboard/lib/python3.7/site-packages/cadquery/occ_impl/importers.py", line 64, in importStep
    raise ValueError("STEP File could not be loaded")
ValueError: STEP File could not be loaded

I am working on just straight up guide for my linux workstation. Docker and conda seems like a real overkill here.

[bosd]

Encountered the same issue by using the CLI inside the docker container.
Pr in: #116

[joshreve]

I adopted the docker approach because many people didn't know how to set up the Python environment manually. Ultimately, I regret that change. I don't think it helped anything and ended up making more problems. I personally always run from the python config file on a manually configured Python environment since it is the most direct and stable method. The json was also trying to allow more predefined configurations, sort of like the config sections in qmk. If I started from scratch today, I would definitely do it differently. The reality is, that this type of repo is really for those more knowledgable in programming. The half "simplification" didn't really meet anyone's needs sufficiently and ended up complicating it.

The best of intent, but a middling outcome on that addition.