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
ed25c8a4
Commit
ed25c8a4
authored
8 years ago
by
Scott Kitterman
Browse files
Options
Downloads
Patches
Plain Diff
Make another attempt at Django specific binary naming
parent
36f33f94
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
+5
-1
5 additions, 1 deletion
debian/changelog
debian/python-policy.sgml
+10
-8
10 additions, 8 deletions
debian/python-policy.sgml
with
15 additions
and
9 deletions
debian/changelog
+
5
−
1
View file @
ed25c8a4
python-defaults (2.7.13-2) UNRELEASED; urgency=medium
python-defaults (2.7.13-2) UNRELEASED; urgency=medium
[ Matthias Klose ]
* Lower priority of packages from standard to optional.
* Lower priority of packages from standard to optional.
-- Matthias Klose <doko@debian.org> Fri, 30 Dec 2016 07:03:55 +0100
[ Scott Kitterman ]
* Make another attempt at Django specific binary naming
-- Scott Kitterman <scott@kitterman.com> Wed, 18 Jan 2017 01:41:29 -0500
python-defaults (2.7.13-1) unstable; urgency=medium
python-defaults (2.7.13-1) unstable; urgency=medium
...
...
This diff is collapsed.
Click to expand it.
debian/python-policy.sgml
+
10
−
8
View file @
ed25c8a4
...
@@ -628,14 +628,16 @@ import foo
...
@@ -628,14 +628,16 @@ import foo
versions should be included in a single package.
versions should be included in a single package.
</p>
</p>
<p>
<p>
As a special exception to the <package>python3-</package> and
Packages intended for use with Django (<package>python3-django</package>/
<package>python-</package> binary naming policy, Python modules
<package>python-django</package>) are installed in the same namespace as
intended for use with Django (<package>python3-django</package>/
other python packages for a variety of reasons. Many such packages are
<package>python-django</package>) should add django to their binary
named django_packagename upstream. These are then packaged as
package names to make it clear they are intended for use with Django
<package>python3-django-package</package> and
and not general purpose Python modules, i.e.
<package>python-django-package</package>.
<package>python3-django-</package> and
This makes it clear that they are intended for use with Django
<package>python-django-</package> respectively.
and not general purpose Python modules. Debian maintainers are
encouraged to work with their upstreams to support consistent use of
this approach.
</sect>
</sect>
<sect id="specifying_versions">
<sect id="specifying_versions">
<heading>Specifying Supported Versions</heading>
<heading>Specifying Supported Versions</heading>
...
...
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