On 01/31/2014 03:20 PM, Vincent Bernat wrote:
[...]
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
Since it is team maintained, I don't think it really makes sense. Should
we just close the bug report and remove Sandro from the
On Tue, Feb 04, 2014 at 06:35:56PM +0800, Thomas Goirand wrote:
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
Since it is team maintained, I don't think it really makes sense. Should
we just close the bug report and remove Sandro
* Vincent Bernat ber...@debian.org, 2014-01-31, 08:20:
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
Since it is team maintained, I don't think it really makes sense.
Given that he was the only uploader, this makes perfect sense.
[Vincent Bernat, 2014-01-31]
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
sorry to see that, unfortunately people who do something also have to
have thick skin to ignore people who talk much
Since it is team maintained, I don't think
2014-01-26 Barry Warsaw ba...@debian.org:
I do think we should be switching all team maintained packages to dh_py2 and
finally getting rid of py-support and py-central (!).
python-central is no longer a problem, see #717091 :)
--
To UNSUBSCRIBE, email to
Excerpts from Piotr Ożarowski's message of 2014-01-31 02:05:43 -0800:
[Vincent Bernat, 2014-01-31]
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
sorry to see that, unfortunately people who do something also have to
have thick skin
[...]
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
Since it is team maintained, I don't think it really makes sense. Should
we just close the bug report and remove Sandro from the Uploaders field?
--
panic(Oh boy, that early out of
On 2014-01-27 at 00:14:12 +0100, Nicolas Dandrimont wrote:
It has been a while since I have been meaning to post a message like this. I
Thanks for writing this
- Be more welcoming to newcomers. I think that the proof of previous work
policy is a hurdle that we would be better off without.
❦ 26 janvier 2014 02:49 CET, Thomas Goirand z...@debian.org :
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-paths
Oh ok. Thanks!
On Jan 26, 2014, at 03:50 AM, Thomas Goirand wrote:
[1] https://wiki.debian.org/Python/TransitionToDHPython2 has:
The two traditionally popular Python helpers, python-support and
python-central have both been deprecated in favor of dh_python2.
So if someone do not agree with this, it should IMO
* Barry Warsaw ba...@debian.org [2014-01-26 13:24:38 -0800]:
I do think we should be switching all team maintained packages to dh_py2 and
finally getting rid of py-support and py-central (!). For the sake of
consistency, I'd love to see the latter two just disappear completely, but at
least
On Mon, Jan 27, 2014 at 12:14:12AM +0100, Nicolas Dandrimont wrote:
[ awesome points here ]
Cheers,
Nicolas Dandrimont
Hear, Hear!
Cheers,
Paul
--
.''`. Paul Tagliamonte paul...@debian.org | Proud Debian Developer
: :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87
`.
On 26 Jan 2014 16:33, Paul Tagliamonte paul...@debian.org wrote:
On Mon, Jan 27, 2014 at 12:14:12AM +0100, Nicolas Dandrimont wrote:
[ awesome points here ]
Cheers,
Nicolas Dandrimont
Hear, Hear!
Ditto - I agree with just about everything Nicolas said. I'd love to see
this become a
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.
On 25 January 2014 23:01, Sandro Tosi mo...@debian.org 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?
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 more
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 25 Jan 2014 07:37, Thomas Goirand z...@debian.org 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
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, but
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 calling
* Thomas Goirand z...@debian.org, 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
On 01/26/2014 04:29 AM, Jakub Wilk wrote:
* Thomas Goirand z...@debian.org, 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
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
* Thomas Goirand z...@debian.org, 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
On Sat, Jan 25, 2014 at 3:53 PM, Thomas Goirand z...@debian.org 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
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.
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-paths
On 25 January 2014 17:21, Sandro Tosi mo...@debian.org 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
28 matches
Mail list logo
