SomePackage | A simple example package for thinking about test packaging

Update your add_customer function to send a notification to the channel. To send the notification use the NOTIFY command or the pg_notify(text, text) function.

You have to install packages using the command pipenv install [package], then pipenv will create/update the Pipfile and Pipfile.lock files.

As you already installed the dependencies with pip, you can run pipenv run pip freeze > requirements.txt && pipenv install -r requirements.txt and it will create or update the aforementioned files for you (It is best if you add each package you want because the previous method also writes their dependencies on these files).

more here

In the browser, the file variable will be an instance of File as described in the MDN page: https://developer.mozilla.org/en-US/docs/Web/API/File

Meaning it's a complete object with properties like name, lastModified…

Meanwhile in Node.js the value returned by fs.readFile with the utf8 encoding will be the content of the file as a string.

So they're indeed incompatible. Depending on what somepackage.read does with the File object, you may be able to emulate a dummy object by retrieving date info with a separate fs.stat call.

Fortunately, projects like https://github.com/node-file-api/file-api already took care of it.

Beware that if somepackage.read assume that the provided file is a Blob, you'll need to enhance the package mentioned above by using feature introduced very recently in Node.js 15.x : https://github.com/nodejs/node/pull/36811

The linked page shows that the classes are all in the top-level package which has no name. Also, it looks like these classes are meant to be run, not imported. To run them, type:

The problem here was that with so many libraries with so many different potentially incompatible versions around, it was a complete mess.

The solution:

1. sudo -H python3.8 -m pip install --upgrade pip wheel setuptools

2. sudo -H python3.8 -m pip install colorama --upgrade

3. sudo -H python3.8 -m pip install shap

the reason that this solution wasn't so obvious is because none of this was mentioned in the error messages.

If you want to use devel or feature branch, or you haven’t published a certain package to the NPM registry, or you can’t because it's a private module, then you can point to a git:// URI instead of a version number in your package.json:

With the extension Command Variable you can create part of a property based on the file path

By using the absolute path to system Python like that:

It's important that my source code remains in this src directory. It is equally important that I am able to run and build my code from the root of my project (For example the .env file is located at the root of the repository).

These two requirements are contradictory. You have to let go of one.

Especially the second one is unfounded: Do not use go run, use go build. Make the path to look for the .env file a command line option to your program (Go is not PHP or JavaScript, there simply is no project or source root for the executing binary). Or build the executable somewhere but execute it in you project root.

Note that having a src folder is -- to put it mildly -- uncommon.

I tried moving the go.mod at the root of the project and running and ran go run ./src but this causes issues of its own:

Well, start by not using go run at all, use go build. And then try building the actual main package. All the go tooling works best on packages, not on file system folders. If your module is named playing.hardball/for-unspecific-reasons and package main is in src try go build playing.hardball/for-unspecific-reasons/src.

Takeaways even if this doesn't work out the way you want:

• Do not use go run. The reasons are manyfold, it is useful to run single file scripts and a loaded footgun for basically every other use case.
• The go tool works on import paths. In simple cases the import path can be inferred from the filesystem.
• A compiled executable has no notion of a "project directory", "source", "classpath" or whatever, it is a standalone executable runnable everywhere and completely detached from its sources.
• Make all filesystem lookup path a configuration option (cmdline flag or environment variable); provide practical defaults (e.g. ./); use that when running your executable to announce where to find static stuff like .env files, templates, icons, css files, etc.