[Python-Dev] Removing doc from pythonhosted.org
I'm not sure whether this is the right mailing list where to post this. However, it seems the pypi UI currently provides a way to upload doc at the bottom of the page https://pypi.python.org/pypi?%3Aaction=pkg_edit&name=PROJECT_NAME but there's currently no way to remove it: https://bitbucket.org/pypa/pypi/issue/24/allow-deleting-project-documentation-from http://sourceforge.net/p/pypi/support-requests/294/ https://github.com/litl/rauth/issues/81 The only workaround as of http://stackoverflow.com/questions/6521931/how-to-delete-documentation-from-pypiappears to be uploading a new .zip file with a redirect. -- Giampaolo - http://grodola.blogspot.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Wave module support for floating point data
Hi everybody, more than a year ago I have submitted a patch to enhance the Wave module with read/write support for floating point data. http://bugs.python.org/issue16525 Up till now this patch has not been applied nor did I get feedback if anything needs to be enhanced or changed before it can be committed. I have never been in contact with your development process and Python core developers, so please tell me what I should improve... Regards, Sebastian ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Wave module support for floating point data
On 3/1/2014 2:57 PM, Sebastian Kraft wrote: Hi everybody, more than a year ago I have submitted a patch to enhance the Wave module with read/write support for floating point data. http://bugs.python.org/issue16525 Up till now this patch has not been applied nor did I get feedback if anything needs to be enhanced or changed before it can be committed. I have never been in contact with your development process and Python core developers, so please tell me what I should improve... Please subscribe to core-mentorship list and post your question there. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Wave module support for floating point data
On Sat, 01 Mar 2014 15:08:00 -0500 Terry Reedy wrote: > On 3/1/2014 2:57 PM, Sebastian Kraft wrote: > > Hi everybody, > > > > more than a year ago I have submitted a patch to enhance the Wave module > > with read/write support for floating point data. > > > > http://bugs.python.org/issue16525 > > > > Up till now this patch has not been applied nor did I get feedback if > > anything needs to be enhanced or changed before it can be committed. > > I have never been in contact with your development process and Python > > core developers, so please tell me what I should improve... > > Please subscribe to core-mentorship list and post your question there. I don't understand this response. You seem to be assuming that Sebastian is asking for guidance, but he's simply telling us about a patch that hasn't received any review yet, despite having been posted one year ago. It's not obvious he has been doing something wrong that he needs to be taught about. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Wave module support for floating point data
On 3/1/2014 3:25 PM, Antoine Pitrou wrote: On Sat, 01 Mar 2014 15:08:00 -0500 Terry Reedy wrote: On 3/1/2014 2:57 PM, Sebastian Kraft wrote: Hi everybody, more than a year ago I have submitted a patch to enhance the Wave module with read/write support for floating point data. http://bugs.python.org/issue16525 Up till now this patch has not been applied nor did I get feedback if anything needs to be enhanced or changed before it can be committed. I have never been in contact with your development process and Python core developers, so please tell me what I should improve... Please subscribe to core-mentorship list and post your question there. I don't understand this response. You seem to be assuming that Sebastian is asking for guidance, I am reading what he posted, which ended with "please tell me what I should improve...". This sort of question-request is routinely posted, in much the same words, on core-mentorship, and routinely gets a response there. > but he's simply telling us about a patch that hasn't received > any review yet, despite having been posted one year ago. If that were all he said (and it is not) it would not be too useful. There are about 4000 open issues. About half have the 'patch' keyword set, and probably more have patches without the keyword. About 700 with the keywork have seen no activity for a year. Some fraction of those have never received a review. I would guess at least 100. In this sense, there is, unfortunately in my opinion, nothing too special about this issue or patch. If you are really interested in this subset of issues, someone should do a custom search against the database. Issues that are open, have a patch (a file name ending in .diff or .patch) posted more than a year ago, and have no subsequent responses from a core developer, would be a start. Perhaps we should add a 'reviewed' field to the table of uploads, which would be automatically marked True when is a completed Rietveld response. Perhaps there should be a way to connect review messages, as opposed to mere comment messages, to the patch they review. We should think about this in the process re-design Nick has planned. It's not obvious he has been doing something wrong that he needs to be taught about. The same could initially be said of all the similar posts on core-mentorship. But please change 'wrong' to 'incomplete or something. Most patches get revised and augmented without being 'wrong'. This is especialy true of patches from people 'have never been in contact with [our] development process'. What makes Sebastian's request worth extra attention is the extra information that he, the author of the neglected patch, is still around and desirous of discussing, editing, and augmenting the patch as necessary. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] "Five reviews to get yours reviewed"?
Way back in 2012, Martin Löwis declared a standing offer on this list to get issue patches reviewed: review five issues and he'll review one of yours. [1] Is that offer still around? Have any other devs made any similar offer? I have a couple of patches outstanding, notably issue 20249 [2], which is a small change, has a patch, and has no activity or nosying since its creation. More importantly, if there is such an offer, it'd be great to mention it somewhere, so people can know what they can do to move an issue forward. (And preferably with a link somewhere to what it means to review a patch - what it takes to make a useful and helpful review, which I'm not entirely sure of at the moment.) If there's not, is it something that could be considered? I'd love to see some downward movement on the Open Issues figure, but am not really sure what I can personally do to help. ChrisA [1] https://mail.python.org/pipermail/python-dev/2012-October/122157.html [2] http://bugs.python.org/issue20249 ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] "Five reviews to get yours reviewed"?
On Sun, Mar 2, 2014 at 11:11 AM, Chris Angelico wrote: > I have a couple of patches outstanding, notably issue 20249 [2], which > is a small change, has a patch, and has no activity or nosying since > its creation. And Benjamin Peterson has just looked into this one and committed it, not three minutes after I posted. Looks like that crossed in the ether :) Thanks! I'm still willing to help out with reviewing, though! ChrisA ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] "Five reviews to get yours reviewed"?
On Sun, 2 Mar 2014 11:11:01 +1100 Chris Angelico wrote: > More importantly, if there is such an offer, it'd be great to mention > it somewhere, so people can know what they can do to move an issue > forward. (And preferably with a link somewhere to what it means to > review a patch - what it takes to make a useful and helpful review, > which I'm not entirely sure of at the moment.) If there's not, is it > something that could be considered? I'd love to see some downward > movement on the Open Issues figure, but am not really sure what I can > personally do to help. It's such an unbalanced offer that it's understandable why it never worked. "One review against another" would be reasonable. That said, it's not a mere issue of time. It's also that occasional contributors may not have (or may not feel they have) the required expertise to review other people's patches. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] "Five reviews to get yours reviewed"?
On Sun, Mar 2, 2014 at 11:25 AM, Antoine Pitrou wrote: > On Sun, 2 Mar 2014 11:11:01 +1100 > Chris Angelico wrote: >> More importantly, if there is such an offer, it'd be great to mention >> it somewhere, so people can know what they can do to move an issue >> forward. (And preferably with a link somewhere to what it means to >> review a patch - what it takes to make a useful and helpful review, >> which I'm not entirely sure of at the moment.) If there's not, is it >> something that could be considered? I'd love to see some downward >> movement on the Open Issues figure, but am not really sure what I can >> personally do to help. > > It's such an unbalanced offer that it's understandable why it never > worked. "One review against another" would be reasonable. > > That said, it's not a mere issue of time. It's also that occasional > contributors may not have (or may not feel they have) the required > expertise to review other people's patches. Since there's a skill level difference, I can understand that I'd have to do more work than I'm asking someone else to do. But it's the other part that's more important. How would someone know whether or not they're capable of making useful reviews? Are there guidelines somewhere? Obviously you have to be able to apply the patch, compile (if appropriate), and probably run the test suite, but beyond that, what does it take to review? (The buildbots have the intelligence to do that.) ChrisA ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] "Five reviews to get yours reviewed"?
On 3/1/2014 7:11 PM, Chris Angelico wrote: Way back in 2012, Martin Löwis declared a standing offer on this list to get issue patches reviewed: review five issues and he'll review one of yours. As I remember, he set a pretty low bar for 'review', lowing that I think you are thinking. I have a couple of patches outstanding, notably issue 20249 [2], which is a small change, has a patch, and has no activity or nosying since its creation. And the other? More importantly, if there is such an offer, it'd be great to mention it somewhere, so people can know what they can do to move an issue forward. (And preferably with a link somewhere to what it means to The question has been asked on core-mentorship list. I have considered making an offer, but haven't yet. review a patch - what it takes to make a useful and helpful review, which I'm not entirely sure of at the moment.) If there's not, is it something that could be considered? I'd love to see some downward movement on the Open Issues figure, but am not really sure what I can personally do to help. You are active on python-ideas, so build on that. There are 1551 open enhancement issues. Some have no response. Some should be rejected (for instance, if a couple of core devs have given negative responses, and none positive). Some should probably be closed, but possibly discussed on python-ideas. You could open either suggest that the OP post on python-ideas or open a discussion yourself. Many should have been discussed on python-ideas first, to garner support, but may have been posted before it existed, or at least before it was very well known. Some might be obsolete given what has otherwise been added, or by changes from py2 to py3. Any that are left open should be marked for 3.5. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] "Five reviews to get yours reviewed"?
On Sun, Mar 2, 2014 at 4:07 PM, Terry Reedy wrote: > On 3/1/2014 7:11 PM, Chris Angelico wrote: >> I have a couple of patches outstanding, notably issue 20249 [2], which >> is a small change, has a patch, and has no activity or nosying since >> its creation. > > And the other? http://bugs.python.org/issue19494 has a patch that I uploaded, but it's more accurately someone else's patch and I just made a slight tweak to it. http://bugs.python.org/issue20729 is an issue that I opened, and there's a patch at the issue, but I didn't write the patch. Technically, neither really counts, but I was checking over the "Followed by you" issues list and saw that several had patches. >> I'd love to see some downward >> movement on the Open Issues figure, but am not really sure what I can >> personally do to help. > > You are active on python-ideas, so build on that. There are 1551 open > enhancement issues. ... > You could open either suggest that the OP post on python-ideas > or open a discussion yourself. Okay! I'll poke around at some issues tonight and see what I can find. *thumb up* Thanks for the pointer. ChrisA ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
