Re: pyxdg 0.23

2012-07-31 Thread Jakub Wilk

* Thomas Kluyver , 2012-07-30, 19:36:
The attached diff updates pyxdg with a new upstream version, which 
includes Python 3 support (bug #591017).


I'm not sure of the etiquette for doing this sort of thing. Should I 
contact the list (like this), directly contact the individual named as 
the uploader - in this case, Piotr Lewandowski - or commit the changes 
to the team SVN repository and then ask for review?


If the team is in the Maintainer field, you are invited to commit and 
upload stuff yourself. However, in case of big or controversial changes 
(*cough* #654978 *cough*) it's still a good idea to ask the human 
maintainer(s) first.


From a quick look at the diff:


+   rm -rf *.egg-info


This looks like a no-op to me.

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120731070252.ga...@jwilk.net



Re: pyxdg 0.23

2012-07-31 Thread Thomas Kluyver
On 31 July 2012 08:02, Jakub Wilk  wrote:
> If the team is in the Maintainer field, you are invited to commit and upload
> stuff yourself. However, in case of big or controversial changes (*cough*
> #654978 *cough*) it's still a good idea to ask the human maintainer(s)
> first.

Do these changes count as big? By the standards of packaging, it's a
fairly substantial set of changes, including adding a new binary
package. But it's not changing much that should affect users, just
packaging a new upstream release.

>> +   rm -rf *.egg-info
>
> This looks like a no-op to me.

Thanks, I'll remove that line. Are there other cases where it is
needed? I got it from http://wiki.debian.org/Python/LibraryStyleGuide

Best wishes,
Thomas


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caovn4qigrckmdlcbgwjg6bdxua_byn_yyp4a6umecfh4sfz...@mail.gmail.com