Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #7922 > unrolled thread

Packaging Python that requires 3.5

Back to article view | Back to linux.debian.maint.python

Contents

  Packaging Python that requires 3.5 Brian May <brian@linuxpenguins.xyz> - 2015-11-28 07:10 +0100
    Re: Packaging Python that requires 3.5 Dmitry Shachnev <mitya57@debian.org> - 2015-11-28 19:10 +0100
      Re: Packaging Python that requires 3.5 Brian May <bam@debian.org> - 2015-11-29 00:10 +0100
        Which bug report is tracking the “python3 is  Python 3.5” transition? (was: Packaging Python that  requires 3.5) Ben Finney <ben+debian@benfinney.id.au> - 2015-11-29 00:40 +0100
          Re: Which bug report is tracking the “python3  is Python 3.5” transition? (was: Packaging Python  that requires 3.5) Brian May <bam@debian.org> - 2015-11-29 01:30 +0100
            Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5) Scott Kitterman <debian@kitterman.com> - 2015-11-29 01:50 +0100
              Re: Which bug report is tracking the “python3  is Python 3.5” transition? (was: Packaging Python  that requires 3.5) Brian May <bam@debian.org> - 2015-11-29 02:50 +0100

#7922 — Packaging Python that requires 3.5

Apparently this doesn't work just yet.

In debian/control I have X-Python3-Version: >= 3.5

This gives in the Depends:
python3.5:any, python3:any (>= 3.5~)

This cannot be statisfied because python3 the version in unstable is
3.4.3-7
-- 
Brian May <brian@linuxpenguins.xyz>
https://linuxpenguins.xyz/brian/

[toc] | [next] | [standalone]

#7926

[Multipart message — attachments visible in raw view] — view raw

Hi Brian,

On Sat, Nov 28, 2015 at 05:08:20PM +1100, Brian May wrote:
> Apparently this doesn't work just yet.
>
> In debian/control I have X-Python3-Version: >= 3.5
>
> This gives in the Depends:
> python3.5:any, python3:any (>= 3.5~)
>
> This cannot be statisfied because python3 the version in unstable is
> 3.4.3-7

I recommend simply waiting until 3.5 is the default (do we have any ETA
for that?).

If you really want this now, you need to make sure that your scripts have
explicit python3.5 shebangs and not generic python3 ones (and you will need
to revert to python3 ones as soon as we get 3.5 as default, else it will
break with next default version change).

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#7927

Dmitry Shachnev <mitya57@debian.org> writes:

> I recommend simply waiting until 3.5 is the default (do we have any ETA
> for that?).

Good question. If it was anytime soon, I would wait.

However I don't know much about this Python 3.5 transition, or what the
current waiting point is.

Is there anything that can be done to help?
-- 
Brian May <bam@debian.org>

[toc] | [prev] | [next] | [standalone]

#7928 — Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Brian May <bam@debian.org> writes:

> However I don't know much about this Python 3.5 transition, or what
> the current waiting point is.

API/ABI transitions (such as switching default Python 3 to be PYthon
3.5) are managed by the release team, with a workflow described at
<URL:https://wiki.debian.org/Teams/ReleaseTeam/Transitions>.

A transition is initiated by a bug report against ‘release.debian.org’,
tagged with the user-tag “transition”. You can check current transitions
<URL:https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=release.debian.org@packages.debian.org;tag=transition>.

The transition of default ‘python3’ to Python 3.5 does not appear in
that set, so I'm not sure how it's being tracked.

The prior transition – to add support for Python 3.5 – is at
<URL:https://bugs.debian.org/798999> and refers to future transitions.
I think maybe the “default python3 is Python 3.5” transition has somehow
become entangled with that prior one.

> Is there anything that can be done to help?

Have a read through the log for bug#798999 and see whether they're
waiting on something we can help with.

-- 
 \     “Are you pondering what I'm pondering?” “I think so, ... Brain, |
  `\    but how can we get seven dwarves to shave their legs?” —_Pinky |
_o__)                                                   and The Brain_ |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#7929 — Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Ben Finney <ben+debian@benfinney.id.au> writes:

> API/ABI transitions (such as switching default Python 3 to be PYthon
> 3.5) are managed by the release team, with a workflow described at
> <URL:https://wiki.debian.org/Teams/ReleaseTeam/Transitions>.

There is https://release.debian.org/transitions/html/python3.5.html

Still trying to work out what the "Dependency level n" headers mean.

What are the implications of the "Collisions" section? Looks like
packages in multiple transitions.

Are the orange packages a problem or not? So if the build is failing on
a platform it will get an orange status as well as if it doesn't meet
the good or bad criteria.

If I understand this correctly, all packages as part of the transition
get uploaded to experimental, and then get moved at once to unstable?

Unfortunately the
https://release.debian.org/transitions/html/python3.5.html page doesn't
indicate if somebody is already working on the package or not.

I would have thought binNMU would be sufficient for some of these
packages, however maybe these easy targets have already been fixed now?

> Have a read through the log for bug#798999 and see whether they're
> waiting on something we can help with.

Not that I can see. So maybe that means any of the red packages on the
transition tracking page.

Some of the packages look like they are broken with no immediate fix,
maybe should get removed from unstable *if* inclusion in unstable is
holding up the transition. e.g. openturns.
-- 
Brian May <bam@debian.org>

[toc] | [prev] | [next] | [standalone]

#7930 — Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

On November 28, 2015 7:21:57 PM EST, Brian May <bam@debian.org> wrote:
>Ben Finney <ben+debian@benfinney.id.au> writes:
>
>> API/ABI transitions (such as switching default Python 3 to be PYthon
>> 3.5) are managed by the release team, with a workflow described at
>> <URL:https://wiki.debian.org/Teams/ReleaseTeam/Transitions>.
>
>There is https://release.debian.org/transitions/html/python3.5.html
>
>Still trying to work out what the "Dependency level n" headers mean.
>
>What are the implications of the "Collisions" section? Looks like
>packages in multiple transitions.
>
>Are the orange packages a problem or not? So if the build is failing on
>a platform it will get an orange status as well as if it doesn't meet
>the good or bad criteria.
>
>If I understand this correctly, all packages as part of the transition
>get uploaded to experimental, and then get moved at once to unstable?
>
>Unfortunately the
>https://release.debian.org/transitions/html/python3.5.html page doesn't
>indicate if somebody is already working on the package or not.
>
>I would have thought binNMU would be sufficient for some of these
>packages, however maybe these easy targets have already been fixed now?
>
>> Have a read through the log for bug#798999 and see whether they're
>> waiting on something we can help with.
>
>Not that I can see. So maybe that means any of the red packages on the
>transition tracking page.
>
>Some of the packages look like they are broken with no immediate fix,
>maybe should get removed from unstable *if* inclusion in unstable is
>holding up the transition. e.g. openturns.

We haven't started the transition yet.  When it starts, binNMU should be enough for most of the packages.

Scott K

[toc] | [prev] | [next] | [standalone]

#7931 — Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Scott Kitterman <debian@kitterman.com> writes:
> We haven't started the transition yet.  When it starts, binNMU should
> be enough for most of the packages.

When will you start the transition?
-- 
Brian May <bam@debian.org>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web