Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
python-defaults
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pkg
python-defaults
Commits
401e0517
Commit
401e0517
authored
14 years ago
by
Scott Kitterman
Browse files
Options
Downloads
Patches
Plain Diff
Revert X-S-PV for Python 3 versions policy change. We aren't there yet.
modified: debian/changelog debian/python-policy.sgml
parent
5b8f4149
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
debian/changelog
+0
-2
0 additions, 2 deletions
debian/changelog
debian/python-policy.sgml
+3
-14
3 additions, 14 deletions
debian/python-policy.sgml
with
3 additions
and
16 deletions
debian/changelog
+
0
−
2
View file @
401e0517
...
...
@@ -10,8 +10,6 @@ python-defaults (2.6.5-4) UNRELEASED; urgency=low
[ Scott Kitterman ]
* Additonal Python 3 related policy changes:
- Clarify that helper specific policy does not apply to Python 3
- Define policy for expressing Python and Python 3 versions in
XS-Python-Version
-- Piotr Ożarowski <piotr@debian.org> Sun, 20 Jun 2010 16:13:24 -0400
...
...
This diff is collapsed.
Click to expand it.
debian/python-policy.sgml
+
3
−
14
View file @
401e0517
...
...
@@ -438,35 +438,24 @@ import foo
in the general paragraph (the first one, for the source package) of
<file>debian/control</file> specifies the versions of Python
supported by the source package. When not specified, it defaults to
all currently supported Python versions (Note: This does not include any
Python 3 versions).
</p>
<p>
It is used to express both Python and Python 3 versions. Support for
Python 3 versions cannot be implicitly defined, it must always be
explicit. It is not necessary to express <tt><< 3.0</tt> because this is
always true when Python versions are specified.
</p>
<p>
all currently supported Python versions.
It is notably used to track packages during Python transitions,
and is also used by some packaging scripts to automatically
generate appropriate Depends and Provides lines. The format of the
field may be one of the following:
<example>
XS-Python-Version: >= X.Y
XS-Python-Version: >= 2.Y, >= 3.Y
XS-Python-Version: >= A.B, << X.Y
XS-Python-Version: A.B, X.Y
XS-Python-Version: all
XS-Python-Version: all, >= 3.1
</example>
The keyword "all" means that the package supports any Python
version available but might be deprecated in the future since
using version numbers is clearer than "all" and encodes more
information. The keyword "all" is limited to Python versions and
must be ignored for Python 3 versions.
</p>
<p>
The keyword "current" has been deprecated and used to mean that
the package would only have to support a single version (even
across default version changes). It must be ignored for Python 3
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment