I am trying to come up with an organization scheme for a package and an a series of contributed plugins that can also work standalone - i.e., they have their own setup.py. Those contributed packages are all hosted in a single repo, which can be used to install them all at once. The plugins are discovered as native namespace packages (as described here), and I manually point to the folders in setup.py as so:
package_dir={
"contrib_package_1": "my_package/contrib/contrib_package_1",
"my_package.contrib.contrib_package_1": "my_package/contrib/contrib_package_1",
}
I am having one major and one minor issue with this setup (and maybe a few more I haven't discovered yet).
Major issue: I can't discover the contrib packages when installing them in editable mode: pip install -e contrib-packages\contrib_package_1 works fine, the package is in pip freeze or conda list, and the correct path is specified in the egg-link file - but I simply cannot import it (ModuleNotFoundError). I guess this is somehow related to the nested structure, because when I pull out contrib_package_1 to the root level and install it in editable mode, it is discovered.
Minor issue: When installing all packages in regular mode they are discovered fine and harmonize as expected, but the path for my_package.contrib is empty until I do from my_package.contrib import contrib_package_1. Upon doing import my_package I would like users to see which plugins are installed, so, somehow the path for my_package.contrib would need to be updated upon loading the main package (I added from .config import * to the main packages __init__.py, but that didn't do the trick).
Similar issues have been described here: How to install multiple python namespace packages in editable mode
main-package # main repo
├-- setup.py
├── my_package
│ ├── __init__.py <- # contains `from .config import *`
│ ├── code.py
│ ├── main
│ │ ├── __init__.py
│ │ └── more_code.py
│ ├── contrib <- # empty
contrib-packages # contrib repo
├-- setup.py <- # install all contrib packages
├── contrib_package_1
│ ├── setup.py
│ └── my_package
│ └── contrib
│ └── contrib_package_1
│ ├── __init__.py
│ ├── code.py
│ └── _version.py
├── contrib_package_2
│ ├── setup.py
│ └── my_package
│ └── contrib
│ └── contrib_package_2
│ ├── __init__.py
│ ├── code.py
│ └── _version.py
...
Envs
$ go version
go version go1.15.2 linux/amd64
What I want
I want to make a microservice implemented by Go.
What happened
When I run git commit, pre-commit run golint command, and now it prints 'golint: command not found'.
asuha on asuha-HP-EliteDesk-800-G4-TWR in ~/go/src/github.com/Asuha-a/URLShortener/api/services/user(27m|feat/_20_design_backend_architecture*)
$ git commit -m "feat: add user app #20"
go fmt...................................................................Passed
go lint..................................................................Failed
- hook id: go-lint
- exit code: 1
/home/asuha/.cache/pre-commit/repo5ywtpl6j/run-go-lint.sh: line 7: golint: command not found
go imports...............................................................Passed
go-cyclo.................................................................Failed
- hook id: go-cyclo
- exit code: 127
/home/asuha/.cache/pre-commit/repo5ywtpl6j/run-go-cyclo.sh: line 9: exec: gocyclo: not found
validate toml........................................(no files to check)Skipped
Check files aren't using go's testing package........(no files to check)Skipped
go-unit-tests............................................................Passed
go-mod-tidy..............................................................Passed
Codes
settings for go in .zshrc
export PATH=$PATH:/usr/local/go/bin
export GOROOT=/usr/local/go
export GOPATH=$HOME/go
export GOBIN=$GOPATH/bin
project tree
asuha on asuha-HP-EliteDesk-800-G4-TWR in ~/go/src/github.com/Asuha-a/URLShortener(43m|feat/_20_design_backend_architecture*)
$ tree
.
├── api
│ ├── Dockerfile
│ ├── go.mod
│ ├── go.sum
│ ├── main.go
│ ├── pb
│ └── services
│ ├── README.md
│ └── user
│ ├── go.mod
│ ├── go.sum
│ └── main.go
├── docker-compose.yml
└── README.md
tree in gopath
.
├── bin
│ ├── gocyclo
│ ├── golint
│ ├── gopls
│ ├── go-test
│ ├── my-first-go
│ ├── protoc-gen-go
│ ├── protoc-gen-go-grpc
│ └── user
├── pkg
│ ├── linux_amd64
│ │ └── github.com
│ ├── mod
│ │ ├── cache
│ │ ├── cloud.google.com
│ │ ├── github.com
│ │ ├── golang.org
│ │ ├── google.golang.org
│ │ ├── gopkg.in
│ │ ├── honnef.co
│ │ └── mvdan.cc
│ └── sumdb
│ └── sum.golang.org
└── src
├── github.com
│ ├── Asuha-a
│ ├── fzipp
│ ├── gin-contrib
│ ├── gin-gonic
│ ├── golang
│ ├── go-playground
│ ├── leodido
│ ├── mattn
│ └── ugorji
├── golang.org
│ └── x
├── google.golang.org
│ └── protobuf
└── gopkg.in
└── yaml.v2
.pre-commit-config.yaml
repos:
- repo: git://github.com/dnephin/pre-commit-golang
rev: master
hooks:
- id: go-fmt
- id: go-lint
- id: go-imports
- id: go-cyclo
args: [-over=15]
- id: validate-toml
- id: no-go-testing
- id: go-unit-tests
- id: go-mod-tid
/home/asuha/go/src/github.com/Asuha-a/URLShortener/api/go.mod
module github.com/Asuha-a/URLShortener/api
go 1.15
require (
github.com/fzipp/gocyclo v0.3.1 // indirect
github.com/gin-gonic/gin v1.6.3
github.com/go-playground/validator/v10 v10.4.1 // indirect
github.com/golang/protobuf v1.4.3 // indirect
github.com/json-iterator/go v1.1.10 // indirect
github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
github.com/modern-go/reflect2 v1.0.1 // indirect
github.com/ugorji/go v1.1.13 // indirect
golang.org/x/crypto v0.0.0-20201016220609-9e8e0b390897 // indirect
golang.org/x/lint v0.0.0-20200302205851-738671d3881b // indirect
golang.org/x/sys v0.0.0-20201026173827-119d4633e4d1 // indirect
golang.org/x/tools v0.0.0-20201028025901-8cd080b735b3 // indirect
google.golang.org/protobuf v1.25.0 // indirect
gopkg.in/yaml.v2 v2.3.0 // indirect
)
/home/asuha/go/src/github.com/Asuha-a/URLShortener/api/services/user/go.mod
module github.com/Asuha-a/URLShortener/api/services/user
go 1.15
require (
github.com/fzipp/gocyclo v0.3.1 // indirect
golang.org/x/lint v0.0.0-20200302205851-738671d3881b // indirect
golang.org/x/tools v0.0.0-20201028025901-8cd080b735b3 // indirect
)
What I want to know
Why golint can't run?
How to fix it?
You need to source and persist changes to your PATH env variable. If you using bash you can add next changes to .bashrc or .bash_profile (it's up to OS).
export GOPATH="${HOME}/go"
export GOROOT="/usr/local/opt/go/libexec"
if [[ $PATH != *$GOPATH* ]]; then
export PATH="${GOPATH}/bin:${PATH}"
fi
if [[ $PATH != *$GOROOT* ]]; then
export PATH="${GOROOT}/bin:${PATH}"
fi
Note: there is $HOME variables in my case, but you can write full path to your gopath.
I added these lines directly into the pre-commit hook (at .git/hooks/pre-commit in your repo) and that fixed it for me:
export GOPATH=$HOME/go
if [[ $PATH != *$GOPATH* ]]; then
export PATH="${GOPATH}/bin:${PATH}"
fi
I started using direnv recently.
I created a .envrc file in my project’s root directory.
There is only one line in .envrc:
export GOPATH=$(pwd)
I use vim with coc & gopls to write go, but when I open main.go coc shows this error
Error [compiler] could not import os (no package for import os)
This is my project structure
.
├── .envrc
├── bin -> /root/go/bin
├── out
├── pkg -> /root/go/pkg
└── src
├── github.com -> /root/go/src/github.com
├── golang.org -> /root/go/src/golang.org
└── monkey
├── lexer
│ ├── lexer.go
│ └── lexer_test.go
├── main.go
├── out
├── repl
│ └── repl.go
└── token
└── token.go
I am running the test scripts for my app and I am getting the following error.
Xamarin.UITest.dll version (1.3.8.0) and test-cloud.exe version (1.0.0.0) are incompatible
Any advise ?
There is a matching version test-cloud.exe within each Xamarin.UITest.XXXXX Nuget package and that is the .exe that you should use to run your tests with.
Example:
/packages/Xamarin.UITest.1.3.8.1491-dev
.
├── Xamarin.UITest-License.rtf
├── Xamarin.UITest.1.3.8.1491-dev.nupkg
├── lib
│ ├── Xamarin.UITest.dll
│ └── Xamarin.UITest.xml
└── tools
└── test-cloud.exe
/packages/Xamarin.UITest.1.3.8
.
├── Xamarin.UITest-License.rtf
├── Xamarin.UITest.1.3.8.nupkg
├── lib
│ ├── Xamarin.UITest.dll
│ └── Xamarin.UITest.xml
└── tools
└── test-cloud.exe
I observed one thing.
The package folder for my solution has Xamarin.UITest of 1.0.0.0 and my UITest project had 1.3.8 version. Can you tell me that how to push it to github ?
I think I did everything I could in the last 20 hours, but nothing seems to work. My app is running and working -- just as it should -- the only problem I have is that I cannot create a .app bundle from it. I tried both Py2App and cx_Freeze but non of them is working. Because of the multi-platform support I would stick with the latter -- if possible.
The setup.py looks like this:
import sys
from cx_Freeze import setup, Executable
base = None
if sys.platform == 'win32':
base = 'Win32GUI'
OPTIONS = {'build_exe': {'includes': ['sip',
'PyQt5',
'PyQt5.QtCore',
'PyQt5.QtGui',
'PyQt5.QtWidgets',
'PyQt5.QtMultimediaWidgets',
'PyQt5.QtMultimedia',
'PyQt5.QtNetwork']}}
EXECUTABLES = [Executable('main.py', base=base)]
NAME = 'coublet'
VERSION = '0.5.70'
setup(name = NAME,
version = VERSION,
options = OPTIONS,
executables = EXECUTABLES)
The error message I have is this:
objc[28404]: Class NotificationReceiver is implemented in both
/Users/.../build/coublet-0.5.70.app/Contents/MacOS/QtWidgets and
/usr/local/Cellar/qt5/5.3.1/lib/QtWidgets.framework/Versions/5/QtWidgets. One of
the two will be used. Which one is undefined.
QObject::moveToThread: Current thread (0x7fc4b96e98b0) is not the object's thread
(0x7fc4b95dbc80).
Cannot move to target thread (0x7fc4b96e98b0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process.
Check that all plugins are compiled against the right Qt binaries. Export
DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
This application failed to start because it could not find or load the Qt
platform plugin "cocoa".
Available platform plugins are: cocoa, minimal, offscreen.
Reinstalling the application may fix this problem.
Abort trap: 6
My system Info:
Mac OS X : 10.9.4
Python : 3.4.1
cx_Freeze : 0.9
PyQt5: : 5.3.1
- - -
Packages installed via: Homebrew and PIP
.app structure:
build/coublet-0.5.70.app
└── Contents
├── Frameworks
├── Info.plist
├── MacOS
│ ├── PyQt5.QtCore.so
│ ├── PyQt5.QtGui.so
│ ├── PyQt5.QtMultimedia.so
│ ├── PyQt5.QtMultimediaWidgets.so
│ ├── PyQt5.QtNetwork.so
│ ├── PyQt5.QtWidgets.so
│ ├── Python
│ ├── QtCore
│ ├── QtCore.so
│ ├── QtGui
│ ├── QtGui.so
│ ├── QtMultimedia
│ ├── QtMultimedia.so
│ ├── QtMultimediaWidgets
│ ├── QtMultimediaWidgets.so
│ ├── QtNetwork
│ ├── QtNetwork.so
│ ├── QtOpenGL
│ ├── QtWidgets
│ ├── QtWidgets.so
│ ├── _bisect.so
│ ├── _bz2.so
│ ├── _codecs_cn.so
│ ├── _codecs_hk.so
│ ├── _codecs_iso2022.so
│ ├── _codecs_jp.so
│ ├── _codecs_kr.so
│ ├── _codecs_tw.so
│ ├── _datetime.so
│ ├── _hashlib.so
│ ├── _heapq.so
│ ├── _json.so
│ ├── _lzma.so
│ ├── _md5.so
│ ├── _multibytecodec.so
│ ├── _opcode.so
│ ├── _pickle.so
│ ├── _posixsubprocess.so
│ ├── _random.so
│ ├── _scproxy.so
│ ├── _sha1.so
│ ├── _sha256.so
│ ├── _sha512.so
│ ├── _socket.so
│ ├── _ssl.so
│ ├── _struct.so
│ ├── array.so
│ ├── binascii.so
│ ├── grp.so
│ ├── imageformats
│ │ ├── libqdds.dylib
│ │ ├── libqgif.dylib
│ │ ├── libqicns.dylib
│ │ ├── libqico.dylib
│ │ ├── libqjp2.dylib
│ │ ├── libqjpeg.dylib
│ │ ├── libqmng.dylib
│ │ ├── libqsvg.dylib
│ │ ├── libqtga.dylib
│ │ ├── libqtiff.dylib
│ │ ├── libqwbmp.dylib
│ │ └── libqwebp.dylib
│ ├── libcrypto.1.0.0.dylib
│ ├── liblzma.5.dylib
│ ├── library.zip
│ ├── libreadline.6.dylib
│ ├── libssl.1.0.0.dylib
│ ├── main
│ ├── math.so
│ ├── platforms
│ │ ├── libqcocoa.dylib
│ │ ├── libqminimal.dylib
│ │ └── libqoffscreen.dylib
│ ├── pyexpat.so
│ ├── readline.so
│ ├── select.so
│ ├── sip.so
│ ├── termios.so
│ ├── time.so
│ ├── unicodedata.so
│ └── zlib.so
└── Resources
The question is I think pretty obvious: what am I doing wrong? (or what am I not doing?)
When building an app with cx_Freeze on MacOSX all dependent libraries (.so files on MacOSX) are packaged into the application bundle. It is this that makes the application portable to other systems, without requiring a second install of Qt.
When launching the Application, the libraries should therefore be loaded from within the bundle. However, in your case the system libraries are still being loaded:
/Users/.../build/coublet-0.5.70.app/Contents/MacOS/QtWidgets
/usr/local/Cellar/qt5/5.3.1/lib/QtWidgets.framework/Versions/5/QtWidgets
The result One of the two will be used. Which one is undefined. means that either of these could be loaded. If it picks the correct one, great! If it doesn't you've got two separate sets of libraries loading simultaneously, and that fails shortly afterwards. As an aside, you may find that if you try your Application on another system it will work fine! Sometimes.
For an overview of the problem I suggest taking a look at the following bug #33.
Before you begin
Make sure you have an up-to-date version of cx_Freeze installed. I would suggest trying to clone the repository and installing from there.
Secondly, ensure that the Qt plugins are being correctly built into your application. Cx_Freeze previously looked for the qt-menu.nib file to determine if it was building a Qt application. This is no longer available in Qt5, but you can pass it on the command-line when building your app. Set it to whatever you want, it really doesn't matter:
python setup.py bdist_mac --qt-menu-nib=/usr/local/Cellar/qt5/5.3.1/plugins/platforms/
This may be enough to fix your problem. But if not, you have two options:
Option 1
Each library file contains the paths to it's dependencies. If you're receiving this error, it means some of those paths are either a) still pointing to the original file, or b) not specific enough (and being found on your PATH or DYLD_LIBRARY_PATH). However, you can re-write paths using install_name_tool from the command line (as described here:
install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtWidgets.framework/Versions/5/QtWidgets #executable_path/QtWidgets build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib
install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtCore.framework/Versions/5/QtCore #executable_path/QtCore build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib
install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtPrintSupport.framework/Versions/5/QtPrintSupport #executable_path/QtPrintSupport build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib
install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtGui.framework/Versions/5/QtGui #executable_path/QtGui build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib
This rewrites the paths in the libraries to point into your application folder, using #executable_path as the base. You will need to do this for all the paths that you find loading incorrectly. I'd suggest wrapping it up into an script, to run automatically after the build.
If you want to look at which libraries a file is referencing you can use otool. For example, in a successfully built application of mine:
otool -L libqcocoa.dylib
libqcocoa.dylib:
#executable_path/../Resources/qt_plugins/platforms/libqcocoa.dylib (compatibility version 0.0.0, current version 0.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 20.0.0)
...
There was an updated workaround in the issue tracker that suggests that just importing the correct module in your app will get it to function, however it seems unlikely that you've made an application without QtWidgets.
Option 2
If the above doesn't work, there is another approach outlined here. This is a bit of a sledgehammer approach in that it simply prevents loading of plugins at all.
Add a qt.conf file next to the executable (in the .app bundle that contains:
[Paths]
Plugins = '.'
Either set the environment variable QT_PLUGIN_PATH="" (you can do this within your application before importing PyQt. Or call QtGui.QApplication.setLibraryPaths([]) before creating your application object.
The result is no plugins, so your application will not have access to the MacOSX Cocoa style and UI (e.g. file, colour dialogs).
Use this command :
pip install opencv-python-headless
It resolved the same issue in my case.
This is in addition to #mfitzp's answer.
This QT Plugins Document came in handy.
To look for default locations that your QT app is trying to search you can use following command:
$sudo dtruss MacOS/ncher
getattrlist("/ncher.app\0", 0x7FFF954B51A4, 0x7FFF5C8FDD20) = 0 0
getattrlist("/ncher.app/Contents\0", 0x7FFF954B51A4, 0x7FFF5C8FDD20) = 0 0
getattrlist("/ncher.app/Contents/MacOS\0", 0x7FFF954B51A4, 0x7FFF5C8FDD20) = 0 0
stat64("/ncher.app/Contents/MacOS\0", 0x7FFF5C8FDED8, 0x7FFF5C8FDD20) = 0 0
stat64("/ncher.app/Contents/MacOS/platforms/.\0", 0x7FFF5C8FDF58, 0x7FFF5C8FDD20) = -1 Err#2
open("/dev/tty\0", 0x1000000, 0x1FF) = 5 0
fcntl(0x5, 0x2, 0x1) = 0 0
close(0x5) = 0 0
write_nocancel(0x2, "This application failed to start because it could not find or load the Qt platform plugin \"cocoa\".\n\nReinstalling the application may fix this problem.\n\0", 0x97) = 151 0
sigprocmask(0x3, 0x7FFF5C8FE6B4, 0x0) = 0x0 0
__pthread_sigmask(0x3, 0x7FFF5C8FE6C0, 0x0) = 0 0
__pthread_kill(0x603, 0x6, 0x0) = 0 0
kevent64(0x4, 0x0, 0x0) = -1 Err#4
You can see this QT app trying to look into MacOS/platforms, once i copied my libqcocoa.dylib plugin (its path were modified by install_name_tool command as per #mfitzp's answer) there, my application worked like charm.
BTW it is advisable by MAC codesigning guide to have this directory structure correctly setup, DONT put Frameworks, plugins in ncher.app/Contents/MacOS directory
I had this problem in the context of just starting a Qt Widgets app from Qt Creator.
What helped me was to set the variable QT_PLUGIN_PATH to the value <Qt-dir>/plugins (where <Qt-dir> is the absolute path to the folder in the Qt directory containing, among others, bin, doc, include, lib and of course plugins).
This probably did not fix the root cause of the problem but it was a quick fix that's working fine so far.