Tag: Branch: Tree: b11cf2f371

0.35.1

0.41

0.42

0.42-msi

0.44

0.45

0.46

0.47

0.48

0.49

0.50

0.51

0.52

0.53

0.54

0.55

0.56

0.57

0.58

0.59

0.60

0.61

0.62

0.63

0.64

0.tryme

1.0

1.1

1.2

1.3

1.4

1.5

1.tryme

biggen

builddirupgrade

corporations

crossenvvar

darwin_arch

deprecationdeadline

dirc2

docbuild

dolphin

dotinclude

es/0.61-plus-cython

fedora

gentarget

gh-pages

killpy3

lang-enum

master

mingwdisable

ninjalink

opthelper

optionlookup

optionrefactor

optionrefactor2

optiontree

overrides

pr8895-old

remove-parse_cmd_line_options

revert-10757-llvm-config

rustcmix

tingping/test-gir-program

tingping/test-profile

tingping/xdg-module

trigger-ciimage-builder

uniquefilenames

useargsintests

versionfile

vsmodtest

wip/default-directories

wip/ignatenko/gtester

wip/tingping/xdg-auto-post-install

wip/xclaesse/pr-10714

wip/xclaesse/pr-12097

xclaesse/pr11561-orig

0.1.0

0.10.0

0.11.0

0.12.0

0.13.0

0.14.0

0.15.0

0.16.0

0.17.0

0.18.0

0.19.0

0.2.0

0.20.0

0.21.0

0.22.0

0.23.0

0.24.0

0.25.0

0.26.0

0.27.0

0.28.0

0.29.0

0.30.0

0.31.0

0.32.0

0.33.0

0.34.0

0.35.0

0.35.1

0.36.0

0.37.0

0.37.1

0.38.0

0.38.1

0.39.0

0.39.1

0.4.0

0.4.1

0.40.0

0.40.1

0.41.0

0.41.1

0.41.2

0.42.0

0.42.1

0.43.0

0.44.0

0.44.1

0.45.0

0.45.1

0.46.0

0.46.1

0.47.0

0.47.1

0.47.2

0.48.0

0.48.1

0.48.2

0.49.0

0.49.1

0.49.2

0.5.0

0.50.0

0.50.1

0.51.0

0.51.1

0.51.2

0.52.0

0.52.1

0.53.0

0.53.1

0.53.2

0.54.0

0.54.0.rc1

0.54.1

0.54.2

0.54.3

0.55.0

0.55.0.rc1

0.55.0.rc2

0.55.1

0.55.2

0.55.3

0.56.0

0.56.0.rc1

0.56.0.rc2

0.56.1

0.56.2

0.57.0

0.57.0.rc1

0.57.1

0.57.2

0.58.0

0.58.0.rc1

0.58.1

0.58.2

0.59.0

0.59.0.rc1

0.59.0.rc2

0.59.1

0.59.2

0.59.3

0.59.4

0.6.0

0.60.0

0.60.0.rc1

0.60.0rc2

0.60.1

0.60.2

0.60.3

0.61.0

0.61.0rc1

0.61.1

0.61.2

0.61.3

0.61.4

0.61.5

0.62.0

0.62.0rc1

0.62.0rc2

0.62.1

0.62.2

0.63.0

0.63.0.rc2

0.63.0rc1

0.63.1

0.63.2

0.63.3

0.64.0

0.64.0rc1

0.64.0rc2

0.64.1

0.7.0

0.8.0

0.9.0

1.0.0

1.0.0rc1

1.0.0rc2

1.0.1

1.0.2

1.1.0

1.1.0rc1

1.1.0rc2

1.1.1

1.2.0

1.2.0rc1

1.2.0rc2

1.2.0rc3

1.2.1

1.2.2

1.2.3

1.3.0

1.3.0rc1

1.3.0rc2

1.3.0rc3

1.3.1

1.3.2

1.4.0

1.4.0rc1

1.4.0rc2

1.4.1

1.4.2

1.5.0

1.5.0rc1

1.5.0rc2

1.5.0rc3

1.5.1

1.5.2

1.6.0

1.6.0rc1

1.6.0rc2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'b11cf2f371'

${ noResults }

Commit Graph

1 Commits (b11cf2f37165ddf0ebe737e85768483ff4387481)

Author	SHA1	Message	Date
Jussi Pakkanen	1c3191be55	Condense test directory names.	3 years ago
Eli Schwartz	68b8fbcf6d	Revert "devenv: Set PYTHONPATH where we install python modules" ... This reverts commit 79c6075b56. # Conflicts: # docs/markdown/snippets/devenv.md # mesonbuild/modules/python.py # test cases/unit/91 devenv/test-devenv.py PYTHONPATH cannot be reliably determined. The standard use case for installing python modules with Meson is mixed pure sources (at least `__init__.py`) and compiled extension_modules or configured files. Unfortunately that doesn't actually work because python will not load the same package hierarchy from two different directories, one a source directory and one a (mandatory) out of tree build directory. (It kind of can, but you need to do what this test case accidentally stumbled upon, which is namespace packages. Namespace packages are a very specific use case and you are NOT SUPPOSED to use them outside that use case, so people are not going to use them just to circumvent Meson devenv stuff as that would have negative install-time effects.) Adding PYTHONPATH anyway will just lead to documentation commitments which we cannot actually uphold, and confusing issues at time of use because some imports *will* work... and some will *not*. The end result will be a half-created tree of modules which just doesn't work together at all, but because it partially works, users attempting to debug it will spend time wondering why parts of it do import. For any case where the automatic devenv would work correctly, it will also work correctly to use `meson.add_devenv()` a single time, which is very easy to manually get correct and doesn't provide any significant value to automate. In the long run, an uninstalled python package environment will require "editable installs" support.	3 years ago
Xavier Claessens	6acfe48f32	Allow setting method/separator in environment() and meson.add_devenv()	3 years ago
Xavier Claessens	79c6075b56	devenv: Set PYTHONPATH where we install python modules	3 years ago
Xavier Claessens	598e968993	Add `meson devenv` command and meson.add_devenv()	4 years ago