Howdy all,
How can I convince ‘dh_python3’ to set the shebang to the *default*
Python 3 interpreter?
The way the ‘dh_python3’ tool works (by default?), it will write the
shebang with the full “/usr/bin/python3.X” where “3.X” is whichever
version of Python was used to invoke the install.
For bug#
On 25 January 2014 17:21, Sandro Tosi wrote:
>> Huh? Thomas seemed to be doing the right thing per the DPMT standards
>> etc;
>
> if you change the python helper, you HAVE TO contact who's maintaining
> the package and have they ack the change, that's the team standard.
>
No, one does not within
On 01/26/2014 05:52 AM, Andrew Starr-Bochicchio wrote:
> Also from Python Policy:
>
>> > Modules managed by python-support are installed in another directory
>> > which is added to the sys.path using the .pth mechanism.
> https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-
Thanks for your comments Jakub,
On 01/26/2014 05:47 AM, Jakub Wilk wrote:
> $ PYTHONWARNINGS=d python -c 'import futures'
> /usr/lib/python2.7/dist-packages/futures/__init__.py:24:
> DeprecationWarning: The futures package has been deprecated. Use the
> concurrent.futures package instead.
>Dep
On Sat, Jan 25, 2014 at 3:53 PM, Thomas Goirand wrote:
> I'm however confused how "import concurrent" works, even if there's
> nothing in /usr/lib/python2.7/dist-packages in this package. How come?
Take a look at /usr/share/doc/python-support/README.gz
> * Public modules (.py files that should
* Thomas Goirand , 2014-01-26, 04:53:
- No file shipped into /usr/lib/python2.x/dist-packages (well, 2.7
for Sid, and 2.x if you consider an eventual backport). Now, I'm
saying: "sorry what?" like on your 1st mail. This breaks the package
for everybody (and not "only my case").
It has always w
On 01/26/2014 01:21 AM, Sandro Tosi wrote:
>> if you don't want the package to be team maintained, perhaps take
>> it out of team maintenance?
>
> lecturing is not required, thanks
Actually, it seems it's required here. From this page:
https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
on
On 01/26/2014 04:29 AM, Jakub Wilk wrote:
> * Thomas Goirand , 2014-01-26, 03:50:
>> - No file shipped into /usr/lib/python2.x/dist-packages (well, 2.7 for
>> Sid, and 2.x if you consider an eventual backport). Now, I'm saying:
>> "sorry what?" like on your 1st mail. This breaks the package for
>>
* Thomas Goirand , 2014-01-26, 03:50:
- No file shipped into /usr/lib/python2.x/dist-packages (well, 2.7 for
Sid, and 2.x if you consider an eventual backport). Now, I'm saying:
"sorry what?" like on your 1st mail. This breaks the package for
everybody (and not "only my case").
It has always
Sandro,
I sent you a nice and long email explaining you the ins and outs of this
package, and why/how I did what I did. Now I think you've going really
too far, and crossed the line, IMO.
On 01/26/2014 01:57 AM, Sandro Tosi wrote:
>> This kind of message saddens me.
>
> the same holds for callin
> This kind of message saddens me.
the same holds for calling my packages as having "lots of problems"
(none of them ever being reported as bugs by any of the current users,
nor even by you) of accusing me of having done something without
thinking.
> I'm not expecting this kind of
> interaction,
On 25 Jan 2014 07:37, "Thomas Goirand" wrote:
>
> On 01/25/2014 06:01 PM, Sandro Tosi wrote:
> > Sorry, what? and you didn't think to contact me first to almost
> > rewrite the package? If there's problems, open bugs. Revert your
> > changes or I'll do at the first occasion. and mainly, why don't
> Huh? Thomas seemed to be doing the right thing per the DPMT standards
> etc;
if you change the python helper, you HAVE TO contact who's maintaining
the package and have they ack the change, that's the team standard.
> if you don't want the package to be team maintained, perhaps take
> it out of
On 01/25/2014 06:01 PM, Sandro Tosi wrote:
> Sorry, what? and you didn't think to contact me first to almost
> rewrite the package? If there's problems, open bugs. Revert your
> changes or I'll do at the first occasion. and mainly, why don't you go
> away from DPMT once and for all? you're doing mo
On 25 January 2014 23:01, Sandro Tosi wrote:
> Sorry, what? and you didn't think to contact me first to almost
> rewrite the package? If there's problems, open bugs. Revert your
> changes or I'll do at the first occasion. and mainly, why don't you go
> away from DPMT once and for all? you're doing
Sorry, what? and you didn't think to contact me first to almost
rewrite the package? If there's problems, open bugs. Revert your
changes or I'll do at the first occasion. and mainly, why don't you go
away from DPMT once and for all? you're doing more harm than good
here. you're not welcome here.
O
16 matches
Mail list logo
