Difference between revisions of "Talk:Python package guidelines"

From ArchWiki
Jump to: navigation, search
m (Blackx moved page Talk:Python Package Guidelines to Talk:Python package guidelines: renamed for consistency with other package guidelines (also titles should use sentence case, see Help:Style#Title))
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
There is going to be an official policy drafted to deal with .pyc/.pyo files. See: http://wiki.archlinux.org/index.php/User:Allan/Python_Packaging_Policy
+
There is going to be an official policy drafted to deal with .pyc/.pyo files. See: https://wiki.archlinux.org/index.php/User:Allan/Python_Packaging_Policy
  
 
= Build =
 
= Build =
Line 10: Line 10:
  
 
[[User:Tokland|Tokland]] 09:47, 26 July 2009 (EDT)
 
[[User:Tokland|Tokland]] 09:47, 26 July 2009 (EDT)
 +
 +
: If a program fails to install, the install script probably shouldn't ignore such a critical error. For example, if something is wrong with the install script itself, then the installation probably should abort. Hiding such errors behind a <code>|| return 1</code> statement probably does not make sense. Am I missing something? [[User:Ichimonji10|Ichimonji10]] ([[User talk:Ichimonji10|talk]]) 03:23, 25 June 2014 (UTC)

Latest revision as of 07:34, 22 December 2014

There is going to be an official policy drafted to deal with .pyc/.pyo files. See: https://wiki.archlinux.org/index.php/User:Allan/Python_Packaging_Policy

Build

Shouldn't the install command be protected?

python setup.py install --root=$pkgdir/ || return 1

Tokland 09:47, 26 July 2009 (EDT)

If a program fails to install, the install script probably shouldn't ignore such a critical error. For example, if something is wrong with the install script itself, then the installation probably should abort. Hiding such errors behind a || return 1 statement probably does not make sense. Am I missing something? Ichimonji10 (talk) 03:23, 25 June 2014 (UTC)