Dev zone/Reports - Revision history

Dereckson: /* Python tools */

2025-09-25T16:39:01Z

Python tools

← Older revision		Revision as of 16:39, 25 September 2025
Line 7:		Line 7:
	First, ensure you don't have any module installed through .whl running <code>pip freeze</code>. If you see something like <code>nasqueron-reports==0.1.0</code>, it comes from package auto detection and it's fine and will use your local code. What is not fine is a long line with wheel archive.		First, ensure you don't have any module installed through .whl running <code>pip freeze</code>. If you see something like <code>nasqueron-reports==0.1.0</code>, it comes from package auto detection and it's fine and will use your local code. What is not fine is a long line with wheel archive.

	Then, include every tools/*/src include in your path. The environment script takes care of that.		Then, include every tools/*/src include in your path. The environment script <code>.env</code> as repository root takes care of that.

	=== Environment script ===		=== Environment script ===

Dereckson: /* Environment script */

2025-09-14T13:09:50Z

Environment script

← Older revision		Revision as of 13:09, 14 September 2025
Line 33:		Line 33:
	for dir in $(find tools -type d -name src); do		for dir in $(find tools -type d -name src); do
	if [ "$full_path" = "" ]; then		if [ "$full_path" = "" ]; then
	~~export~~ full_path="$current_dir/$dir"		full_path="$current_dir/$dir"
	else		else
	~~export~~ full_path="$full_path:$current_dir/$dir"		full_path="$full_path:$current_dir/$dir"
	fi		fi
	done		done

Dereckson: /* Environment script */

2025-09-14T13:09:26Z

Environment script

← Older revision		Revision as of 13:09, 14 September 2025
Line 48:		Line 48:
	</syntaxhighlight>		</syntaxhighlight>

	If you call it .env, you can use <code>source .env</code>, but your IDE could complain it contains shell stuff. Override file type as shell script or save it under another name.		If you call it .env, you can use <code>source .env</code>, but your IDE could complain it contains shell stuff if it has support for dotenv files. Override file type as shell script or save it under another name.

Dereckson: /* Environment script */

2025-09-14T13:09:12Z

Environment script

← Older revision		Revision as of 13:09, 14 September 2025
Line 48:		Line 48:
	</syntaxhighlight>		</syntaxhighlight>

	If you call it .env, you can use <code>source .env</code>, but your IDE ~~will~~ complain it contains shell stuff. Override file type as shell script or save it under another name.		If you call it .env, you can use <code>source .env</code>, but your IDE could complain it contains shell stuff. Override file type as shell script or save it under another name.

Dereckson: /* Environment script */ Avoid PYTHONPATH repetitions

2025-09-14T13:08:41Z

Environment script: Avoid PYTHONPATH repetitions

← Older revision		Revision as of 13:08, 14 September 2025
Line 16:		Line 16:
	#!/bin/sh		#!/bin/sh

	~~# Not intended to contain actual credentials, but it allows to validate env config~~
	export DB_USERNAME=someuser		export DB_USERNAME=someuser
	export DB_PASSWORD=somepass		export DB_PASSWORD=somepass

			export VAULT_ADDR=https://localhost:8200

			# -------------------------------------------------------------
			# Python paths
			#
			# Modules are in tools/*/src
			# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

			current_dir=$(pwd)
			full_path=""

	# shellcheck disable=SC2044		# shellcheck disable=SC2044
	for dir in $(find tools -type d -name src); do		for dir in $(find tools -type d -name src); do
	if [ "$~~PYTHONPATH~~" = "" ]; then		if [ "$full_path" = "" ]; then
	export ~~PYTHONPATH~~="$dir"		export full_path="$current_dir/$dir"
	else		else
	export ~~PYTHONPATH~~="$~~PYTHONPATH~~:$dir"		export full_path="$full_path:$current_dir/$dir"
	fi		fi
	done		done

	export ~~VAULT_ADDR~~=~~https://localhost~~:~~8200~~		if [ "$PYTHONPATH" != "$full_path" ]; then
			if [ "$PYTHONPATH" = "" ]; then
			export PYTHONPATH="$full_path"
			else
			export PYTHONPATH="$PYTHONPATH:$full_path"
			fi
			fi
	</syntaxhighlight>		</syntaxhighlight>

	If you call it .env, you can use <code>source .env</code>, but your IDE will complain it contains shell stuff. Override file type as shell script or save it under another name.		If you call it .env, you can use <code>source .env</code>, but your IDE will complain it contains shell stuff. Override file type as shell script or save it under another name.

Dereckson: Created page with "The Nasqueron internal reports repository is a monorepo containing SQL queries and tools to produce reports about Nasqueron internal data. == Python tools == === Configure PYTHONPATH === Python allows to develop several packages at the same time providing all the src/ folders to your PYTHONPATH variables. First, ensure you don't have any module installed through .whl running `pip freeze`. If you see something like `nasqueron-reports==0.1.0`, it co..."

2025-09-14T12:52:06Z

Created page with "The Nasqueron internal reports repository is a monorepo containing SQL queries and tools to produce reports about Nasqueron internal data. == Python tools == === Configure PYTHONPATH === Python allows to develop several packages at the same time providing all the src/ folders to your PYTHONPATH variables. First, ensure you don't have any module installed through .whl running <code>pip freeze</code>. If you see something like <code>nasqueron-reports==0.1.0</code>, it co..."

New page

The Nasqueron internal reports repository is a monorepo containing SQL queries and tools to produce reports about Nasqueron internal data.

== Python tools ==
=== Configure PYTHONPATH ===
Python allows to develop several packages at the same time providing all the src/ folders to your PYTHONPATH variables.

First, ensure you don't have any module installed through .whl running <code>pip freeze</code>. If you see something like <code>nasqueron-reports==0.1.0</code>, it comes from package auto detection and it's fine and will use your local code. What is not fine is a long line with wheel archive.

Then, include every tools/*/src include in your path. The environment script takes care of that.

=== Environment script ===

You can use this environment configuration script for sh, bash and zsh:

<syntaxhighlight lang="shell">
#!/bin/sh

# Not intended to contain actual credentials, but it allows to validate env config
export DB_USERNAME=someuser
export DB_PASSWORD=somepass

# shellcheck disable=SC2044
for dir in $(find tools -type d -name src); do
if [ "$PYTHONPATH" = "" ]; then
export PYTHONPATH="$dir"
else
export PYTHONPATH="$PYTHONPATH:$dir"
fi
done

export VAULT_ADDR=https://localhost:8200
</syntaxhighlight>

If you call it .env, you can use <code>source .env</code>, but your IDE will complain it contains shell stuff. Override file type as shell script or save it under another name.