2715
Comment: Created a page that summarises ongoing discussions and added some use cases and ideas
|
3376
Added 'User defined prefixes' to the list of proposals under consideration
|
Deletions are marked like this. | Additions are marked like this. |
Line 14: | Line 14: |
* [[http://www.python.org/dev/peps/pep-0345/|PEP 345 - Metadata for Python Software Packages 1.2]] | |
Line 28: | Line 29: |
* [[Distutils/DiscussionOverview/UserPrefixes | User defined prefixes]] | |
Line 33: | Line 35: |
It is not possible to retrieve the installation paths of data, or other, files for all installation schemes supported by distutils right now. I propose the inclusion of a PREFIX file within the |
It is not possible to retrieve the installation paths of data, or other, files for all installation schemes supported by distutils right now. I propose the inclusion of a PREFIX file within the |
Line 38: | Line 40: |
-- Wolodja Wentland | -- [[WolodjaWentland|Wolodja Wentland]] |
Line 53: | Line 55: |
-- Wolodja Wentland | -- [[WolodjaWentland|Wolodja Wentland]] |
Line 61: | Line 63: |
== Change the default installation paths == | == Change the default installation scheme == |
Line 63: | Line 65: |
Distribute packaged distributions get installed into the system paths, that are typically under the aegis of the system's package manager. I propose to change the default installation scheme from installing into the system's Python paths to the (PEP 370) user scheme. |
Distribute packaged distributions get installed into paths that are typically under the aegis of the system's package manager. I propose to change the default installation scheme to the (PEP 370) `--user` one. |
Line 67: | Line 69: |
-- Wolodja Wentland | -- [[WolodjaWentland|Wolodja Wentland]] |
Line 74: | Line 76: |
== User defined prefix identifiers == It could be advantageous to provide a method to define arbitrary installation prefixes. This would enable users to split a package into `foo` and `foo-plugin` while still being able to install the data files shipped with `foo-plugin` into the correct location. -- [[WolodjaWentland|Wolodja Wentland]] '''Discussion''': [[Distutils/DiscussionOverview/UserPrefixes]] '''Status''': Under Consideration '''Affected PEPs''': 376 |
Python packaging discussion
The way packaging in Python works is currently undergoing big changes. This page tries to summarise the discussion, proposals and ideas that might be incorporated into the PEPs listed below.
If you have an idea, or a use case that is not (sufficiently) supported right now, we would like to know about it and encourage you to add it to the Ideas & Use cases section of this page.
PEPS
List of packaging related PEPs that are under consideration:
Proposals
Accepted
Under consideration
Ideas & Use cases
Data file installation paths
It is not possible to retrieve the installation paths of data, or other, files for all installation schemes supported by distutils right now. I propose the inclusion of a PREFIX file within the .egg-info directory that holds information on all prefixes set at installation time and a suitable API within pkgutil.
Discussion: Distutils/DiscussionOverview/FilePrefixes
Status: Under Consideration
Affected PEPs: 376
Data file prefix classes/placeholders
Data files shipped within a distribution are not further classified. This makes it impossible to define default installation paths for certain file types that are typically shipped with a distribution like configuration files, examples, shared data files, ...
Discussion: Distutils/DiscussionOverview/PrefixClasses
Status: Under Consideration
Affected PEPs: 376
Change the default installation scheme
Distribute packaged distributions get installed into paths that are typically under the aegis of the system's package manager. I propose to change the default installation scheme to the (PEP 370) --user one.
Discussion: Distutils/DiscussionOverview/DefaultInstallScheme
Status: Under Consideration
Affected PEPs: None
User defined prefix identifiers
It could be advantageous to provide a method to define arbitrary installation prefixes. This would enable users to split a package into foo and foo-plugin while still being able to install the data files shipped with foo-plugin into the correct location.
Discussion: Distutils/DiscussionOverview/UserPrefixes
Status: Under Consideration
Affected PEPs: 376