Talk:Python - Revision history

Danbulant: /* Update the packaging section */ new section

2026-04-25T10:07:27Z

Update the packaging section: new section

← Older revision		Revision as of 10:07, 25 April 2026
Line 41:		Line 41:

	Can we add a section about Full (e.g. python312Full) and non-Full (e.g. python312) versions? Whats the difference and in which situation use on or the other?		Can we add a section about Full (e.g. python312Full) and non-Full (e.g. python312) versions? Whats the difference and in which situation use on or the other?

			== Update the packaging section ==

			Seems like the format was updated and the wiki is no longer accurate? Specifically the <code>setup.py</code> format

			Wiki says that the result of <code>main.py</code> will be in bin/app.py but the resulting filename isn't being renamed, so it should be main.py

			Setuptools now aren't included by default and need to be explicitly mentioned, and pyproject variable set to true, so the example nix file would look something like this:

			<syntaxhighlight lang="nix">
			{ pkgs ? import <nixpkgs> { } }:

			pkgs.python3Packages.buildPythonApplication {
			pname = "myFlaskApp";
			version = "0.1.0";

			src = ./src;

			build-system = with pkgs.python3Packages; [
			setuptools
			];
			propagatedBuildInputs = with pkgs.python3Packages; [
			flask
			];

			pyproject = true;
			}
			</syntaxhighlight> [[User:Danbulant\|Danbulant]] ([[User talk:Danbulant\|talk]]) 10:07, 25 April 2026 (UTC)

Turbotimon: /* Full */

2024-12-18T10:30:21Z

Full

← Older revision		Revision as of 10:30, 18 December 2024
Line 40:		Line 40:
	== Full ==		== Full ==

	Can we add a section about Full and non-Full versions? Whats the difference and in which situation use on or the other?		Can we add a section about Full (e.g. python312Full) and non-Full (e.g. python312) versions? Whats the difference and in which situation use on or the other?

Turbotimon at 10:29, 18 December 2024

2024-12-18T10:29:38Z

← Older revision		Revision as of 10:29, 18 December 2024
Line 37:		Line 37:

	</syntaxHighlight>		</syntaxHighlight>

			== Full ==

			Can we add a section about Full and non-Full versions? Whats the difference and in which situation use on or the other?

imported>Tejasjyothishetty: conda-shell, conda-install not working as bash can't find them

2023-03-23T11:46:07Z

conda-shell, conda-install not working as bash can't find them

← Older revision		Revision as of 11:46, 23 March 2023
Line 1:		Line 1:
	== Conda ==		== Conda ==

	conda-env does not exist after entering the conda-shell without first calling conda-install, so I think the wiki is missleading here, or the package has a bug.		conda-env does not exist after entering the conda-shell without first calling conda-install, so I think the wiki is missleading here, or the package has a bug.
			conda-shell, conda-install have no effect and nothing happens. Bash just says it can't find that command.

	== shellHook explanation ==		== shellHook explanation ==

imported>ManoftheSea at 16:47, 14 February 2023

2023-02-14T16:47:44Z

← Older revision		Revision as of 16:47, 14 February 2023
Line 12:		Line 12:

	[[User:L0b0\|L0b0]] ([[User talk:L0b0\|talk]]) 22:01, 19 September 2021 (UTC)		[[User:L0b0\|L0b0]] ([[User talk:L0b0\|talk]]) 22:01, 19 September 2021 (UTC)

			== Flake example for use with nix develop ==

			I was trying to get python with packages as defined by a flake, and found https://dev.to/deciduously/workspace-management-with-nix-flakes-jupyter-notebook-example-2kke a useful discussion. I propose to add an example:
			<syntaxHighlight lang="nix">
			{
			description = "Python environment";
			inputs.nixpkgs.url = "nixpkgs/nixos-22.11";
			outputs = {nixpkgs, ...}: let
			system = "x86_64-linux";
			pkgs = import nixpkgs {inherit system;};
			in {
			devShells.${system}.default = pkgs.mkShell {
			buildInputs = [
			(pkgs.python3.withPackages (p: [
			p.requests
			]))
			];
			shellHook = "python";
			};
			};
			}

			</syntaxHighlight>

imported>L0b0 at 22:14, 19 September 2021

2021-09-19T22:14:50Z

← Older revision		Revision as of 22:14, 19 September 2021
Line 9:		Line 9:
	== How to use specific Python version? ==		== How to use specific Python version? ==

	I'm working on a project where we're using a specific patch version of Python. How would I set this up?		I'm working on a project where we're using a specific patch version of Python. How would I set this up? [https://stackoverflow.com/q/68658367/96588 This] uses a Python fork, but I'm looking for a specific version of the official Python package.

	[[User:L0b0\|L0b0]] ([[User talk:L0b0\|talk]]) 22:01, 19 September 2021 (UTC)		[[User:L0b0\|L0b0]] ([[User talk:L0b0\|talk]]) 22:01, 19 September 2021 (UTC)

imported>L0b0: /* How to use specific Python version? */ new section

2021-09-19T22:01:25Z

How to use specific Python version?: new section

← Older revision		Revision as of 22:01, 19 September 2021
Line 6:		Line 6:

	It's not clear what the meaning of all the `shellHook` stuff is for, esp. the <code>unset SOURCE_DATE_EPOCH</code> bit.		It's not clear what the meaning of all the `shellHook` stuff is for, esp. the <code>unset SOURCE_DATE_EPOCH</code> bit.

			== How to use specific Python version? ==

			I'm working on a project where we're using a specific patch version of Python. How would I set this up?

			[[User:L0b0\|L0b0]] ([[User talk:L0b0\|talk]]) 22:01, 19 September 2021 (UTC)

imported>Samuela: /* shellHook explanation */ new section

2021-02-03T02:06:05Z

shellHook explanation: new section

← Older revision		Revision as of 02:06, 3 February 2021
Line 2:		Line 2:

	conda-env does not exist after entering the conda-shell without first calling conda-install, so I think the wiki is missleading here, or the package has a bug.		conda-env does not exist after entering the conda-shell without first calling conda-install, so I think the wiki is missleading here, or the package has a bug.

			== shellHook explanation ==

			It's not clear what the meaning of all the `shellHook` stuff is for, esp. the <code>unset SOURCE_DATE_EPOCH</code> bit.

imported>Red-hood: Information about conda seems wrong

2019-10-26T20:23:40Z

Information about conda seems wrong

New page

== Conda ==

conda-env does not exist after entering the conda-shell without first calling conda-install, so I think the wiki is missleading here, or the package has a bug.