Re: archive this group & redirect conversation elsewhere?
Fine with me :) On Sun, 10 May 2020 at 12:45, Sumana Harihareswara < sumana.hariharesw...@gmail.com> wrote: > Hey all -- I've heard no opposition, onlist or offlist. As I asked in > April: please speak up if I'm wrong, or if there's some other reason to > keep this Google group going. And please reply if you agree with the idea - > Jason's the only one who's replied so far. > > Reply by May 12th (2 days from now). > > -Sumana > > > On Friday, May 1, 2020 at 6:02:16 PM UTC-4, Sumana Harihareswara wrote: >> >> Thanks, Jason. >> >> Nudge to the group; 11 more days to comment. >> -Sumana >> >> On 4/14/20 9:20 PM, Jason R. Coombs wrote: >> > My initial reaction was that I _need_ this list, but after a moment’s >> consideration, I think you’re right. +1 >> > >> >> On 13 Apr, 2020, at 22:18, Sumana Harihareswara wrote: >> >> >> >> TL;DR: ok to archive this Google group? Reply by May 12th. >> >> >> >> Below: Context and proposal, reasoning, and timeline. >> >> >> >> >> >> Context & proposal: >> >> >> >> People talk about Python packaging problems, work, and plans in many >> different media: https://discuss.python.org/ , distutils-sig, blogs, >> Twitter, conference talks, IRC, https://python.zulipchat.com/ , >> individual GitHub issues on several different repositories, Stack Overflow, >> and more. So people frequently ask me: where should I go to keep up, or to >> announce something or ask for feedback? It's hard to guide them, because of >> this proliferation and fragmentation. And people have commented on that >> before, both senior folks like Donald[0], and people who are earlier in the >> learning curve[1]. >> >> >> >> We can't and shouldn't stop people from talking about Python packaging >> on social media, at conferences, and so on. But three mailing lists/forums >> on nearly identical topics strikes me as more than we need. >> >> >> >> So I suggest that, one month from now, we stop posting to this list ( >> pypa-dev@googlegroups.com) and essentially archive it. >> >> >> >> >> >> Reasoning (why close THIS one?): >> >> >> >> We now have three mailing list-type places to talk about Python >> packaging tools and progress. All of them allow both reading and posting >> from the web or from an email client, and all of them have web archives >> with built-in search. Generally, the people who want to talk about one of >> these topics want to hear about the same topics (things happening in PyPA >> and about related things in Python that will affect PyPA) no matter what >> venue they're in. >> >> >> >> 1. pypa-dev (here). Started in 2013. About 5 posts in the past month, >> mostly cross-posted to other places as well. Hosted by Google in a >> closed-source application that doesn't seem to get much love from Google's >> product folks. >> >> >> >> 2. The distutils-sig mailing list[2] which has expanded in its scope. >> It's a place to discuss and resolve problems that cut across different >> parts of the Python packaging ecosystem, and to announce new releases or >> in-progress work. You can log in an account, or with Facebook, GitHub, >> GitLab, or Google authentication. About 12 threads in the past month. >> Hosted by Python Software Foundation with an open source application that's >> under active development. >> >> >> >> 3. The Packaging category on Python's Discourse forum >> https://discuss.python.org/c/packaging , which started about a year and >> a half ago[3]. Very wide scope. You can log in with an account, or with >> Facebook or GitHub or via email. About 21 posts per month. Hosted by PSF >> with an open source application that's under active development. >> >> >> >> Maybe I'm missing something. Maybe there is a function being served by >> having a mailing list that is specifically labelled "PyPA" (for instance, >> we could add "get on the Google Group and that makes you a member of PyPA" >> to the pypa.io docs[4]). Maybe there are people actively reading/posting >> here who feel unwelcome on the other two lists/forums, because of >> atmosphere or user interface. As a person doing a bunch of work on PyPA >> stuff over the past ~2.5 years, I haven't noticed either of those >> conditions, so please speak up if I'm wrong, or if there's some other >> reason to keep this Google group going. >> >> >> >> >> >> Timeline and methods: >> >> >> >> Here's what I suggest, and what I will carry out if there is no >> objection. >> >> >> >> In one month, on May 13th, I would verify that no one has argued here >> for why this Google group should continue to be open for posting. Or, even >> if a few people have objected to closing the list, I would check for rough >> consensus, especially of people who are doing SOMETHING productive having >> to do with PyPA (teaching, answering questions online or in person, running >> key infrastructure, writing documentation, making or fixing software, >> etc.). >> >> >> >> I would post a final message to this list, marking its close and >> suggesting that people use distutils-sig or
Re: Announcement: Pipenv Beta Release
Thanks, Dan! Dan is now planning to release tomorrow (Monday). https://github.com/pypa/pipenv/issues/3369#issuecomment-626108212 On Friday, May 1, 2020 at 4:47:53 PM UTC-4, Dan Ryan wrote: > > Greetings all! I am happy to announce that after a long hiatus, there is > a pre-release of pipenv available for testing. > > You can read the full announcement at > https://discuss.python.org/t/announcement-pipenv-beta-release/4051 > > > I look forward to your feedback. > > Thanks, > Dan > > > > -- > Dan Ryan > Software Engineer | Pipenv Maintainer > Canonical, Ltd. | Python Packaging Authority > d@canonical.com | d.@danryan.co > > -- You received this message because you are subscribed to the Google Groups "pypa-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to pypa-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pypa-dev/93db814f-8f5b-451a-892c-4c8e00f92910%40googlegroups.com.
Re: archive this group & redirect conversation elsewhere?
I'm happy for this group to be archived. On Sun, 10 May 2020 at 11:45, Sumana Harihareswara wrote: > > Hey all -- I've heard no opposition, onlist or offlist. As I asked in April: > please speak up if I'm wrong, or if there's some other reason to keep this > Google group going. And please reply if you agree with the idea - Jason's the > only one who's replied so far. > > Reply by May 12th (2 days from now). > > -Sumana > > > On Friday, May 1, 2020 at 6:02:16 PM UTC-4, Sumana Harihareswara wrote: >> >> Thanks, Jason. >> >> Nudge to the group; 11 more days to comment. >> -Sumana >> >> On 4/14/20 9:20 PM, Jason R. Coombs wrote: >> > My initial reaction was that I _need_ this list, but after a moment’s >> > consideration, I think you’re right. +1 >> > >> >> On 13 Apr, 2020, at 22:18, Sumana Harihareswara wrote: >> >> >> >> TL;DR: ok to archive this Google group? Reply by May 12th. >> >> >> >> Below: Context and proposal, reasoning, and timeline. >> >> >> >> >> >> Context & proposal: >> >> >> >> People talk about Python packaging problems, work, and plans in many >> >> different media: https://discuss.python.org/ , distutils-sig, blogs, >> >> Twitter, conference talks, IRC, https://python.zulipchat.com/ , >> >> individual GitHub issues on several different repositories, Stack >> >> Overflow, and more. So people frequently ask me: where should I go to >> >> keep up, or to announce something or ask for feedback? It's hard to guide >> >> them, because of this proliferation and fragmentation. And people have >> >> commented on that before, both senior folks like Donald[0], and people >> >> who are earlier in the learning curve[1]. >> >> >> >> We can't and shouldn't stop people from talking about Python packaging on >> >> social media, at conferences, and so on. But three mailing lists/forums >> >> on nearly identical topics strikes me as more than we need. >> >> >> >> So I suggest that, one month from now, we stop posting to this list >> >> (pypa-dev@googlegroups.com) and essentially archive it. >> >> >> >> >> >> Reasoning (why close THIS one?): >> >> >> >> We now have three mailing list-type places to talk about Python packaging >> >> tools and progress. All of them allow both reading and posting from the >> >> web or from an email client, and all of them have web archives with >> >> built-in search. Generally, the people who want to talk about one of >> >> these topics want to hear about the same topics (things happening in PyPA >> >> and about related things in Python that will affect PyPA) no matter what >> >> venue they're in. >> >> >> >> 1. pypa-dev (here). Started in 2013. About 5 posts in the past month, >> >> mostly cross-posted to other places as well. Hosted by Google in a >> >> closed-source application that doesn't seem to get much love from >> >> Google's product folks. >> >> >> >> 2. The distutils-sig mailing list[2] which has expanded in its scope. >> >> It's a place to discuss and resolve problems that cut across different >> >> parts of the Python packaging ecosystem, and to announce new releases or >> >> in-progress work. You can log in an account, or with Facebook, GitHub, >> >> GitLab, or Google authentication. About 12 threads in the past month. >> >> Hosted by Python Software Foundation with an open source application >> >> that's under active development. >> >> >> >> 3. The Packaging category on Python's Discourse forum >> >> https://discuss.python.org/c/packaging , which started about a year and a >> >> half ago[3]. Very wide scope. You can log in with an account, or with >> >> Facebook or GitHub or via email. About 21 posts per month. Hosted by PSF >> >> with an open source application that's under active development. >> >> >> >> Maybe I'm missing something. Maybe there is a function being served by >> >> having a mailing list that is specifically labelled "PyPA" (for instance, >> >> we could add "get on the Google Group and that makes you a member of >> >> PyPA" to the pypa.io docs[4]). Maybe there are people actively >> >> reading/posting here who feel unwelcome on the other two lists/forums, >> >> because of atmosphere or user interface. As a person doing a bunch of >> >> work on PyPA stuff over the past ~2.5 years, I haven't noticed either of >> >> those conditions, so please speak up if I'm wrong, or if there's some >> >> other reason to keep this Google group going. >> >> >> >> >> >> Timeline and methods: >> >> >> >> Here's what I suggest, and what I will carry out if there is no objection. >> >> >> >> In one month, on May 13th, I would verify that no one has argued here for >> >> why this Google group should continue to be open for posting. Or, even if >> >> a few people have objected to closing the list, I would check for rough >> >> consensus, especially of people who are doing SOMETHING productive having >> >> to do with PyPA (teaching, answering questions online or in person, >> >> running key infrastructure, writing
Re: archive this group & redirect conversation elsewhere?
Hey all -- I've heard no opposition, onlist or offlist. As I asked in April: please speak up if I'm wrong, or if there's some other reason to keep this Google group going. And please reply if you agree with the idea - Jason's the only one who's replied so far. Reply by May 12th (2 days from now). -Sumana On Friday, May 1, 2020 at 6:02:16 PM UTC-4, Sumana Harihareswara wrote: > > Thanks, Jason. > > Nudge to the group; 11 more days to comment. > -Sumana > > On 4/14/20 9:20 PM, Jason R. Coombs wrote: > > My initial reaction was that I _need_ this list, but after a moment’s > consideration, I think you’re right. +1 > > > >> On 13 Apr, 2020, at 22:18, Sumana Harihareswara wrote: > >> > >> TL;DR: ok to archive this Google group? Reply by May 12th. > >> > >> Below: Context and proposal, reasoning, and timeline. > >> > >> > >> Context & proposal: > >> > >> People talk about Python packaging problems, work, and plans in many > different media: https://discuss.python.org/ , distutils-sig, blogs, > Twitter, conference talks, IRC, https://python.zulipchat.com/ , > individual GitHub issues on several different repositories, Stack Overflow, > and more. So people frequently ask me: where should I go to keep up, or to > announce something or ask for feedback? It's hard to guide them, because of > this proliferation and fragmentation. And people have commented on that > before, both senior folks like Donald[0], and people who are earlier in the > learning curve[1]. > >> > >> We can't and shouldn't stop people from talking about Python packaging > on social media, at conferences, and so on. But three mailing lists/forums > on nearly identical topics strikes me as more than we need. > >> > >> So I suggest that, one month from now, we stop posting to this list ( > pypa-dev@googlegroups.com) and essentially archive it. > >> > >> > >> Reasoning (why close THIS one?): > >> > >> We now have three mailing list-type places to talk about Python > packaging tools and progress. All of them allow both reading and posting > from the web or from an email client, and all of them have web archives > with built-in search. Generally, the people who want to talk about one of > these topics want to hear about the same topics (things happening in PyPA > and about related things in Python that will affect PyPA) no matter what > venue they're in. > >> > >> 1. pypa-dev (here). Started in 2013. About 5 posts in the past month, > mostly cross-posted to other places as well. Hosted by Google in a > closed-source application that doesn't seem to get much love from Google's > product folks. > >> > >> 2. The distutils-sig mailing list[2] which has expanded in its scope. > It's a place to discuss and resolve problems that cut across different > parts of the Python packaging ecosystem, and to announce new releases or > in-progress work. You can log in an account, or with Facebook, GitHub, > GitLab, or Google authentication. About 12 threads in the past month. > Hosted by Python Software Foundation with an open source application that's > under active development. > >> > >> 3. The Packaging category on Python's Discourse forum > https://discuss.python.org/c/packaging , which started about a year and a > half ago[3]. Very wide scope. You can log in with an account, or with > Facebook or GitHub or via email. About 21 posts per month. Hosted by PSF > with an open source application that's under active development. > >> > >> Maybe I'm missing something. Maybe there is a function being served by > having a mailing list that is specifically labelled "PyPA" (for instance, > we could add "get on the Google Group and that makes you a member of PyPA" > to the pypa.io docs[4]). Maybe there are people actively reading/posting > here who feel unwelcome on the other two lists/forums, because of > atmosphere or user interface. As a person doing a bunch of work on PyPA > stuff over the past ~2.5 years, I haven't noticed either of those > conditions, so please speak up if I'm wrong, or if there's some other > reason to keep this Google group going. > >> > >> > >> Timeline and methods: > >> > >> Here's what I suggest, and what I will carry out if there is no > objection. > >> > >> In one month, on May 13th, I would verify that no one has argued here > for why this Google group should continue to be open for posting. Or, even > if a few people have objected to closing the list, I would check for rough > consensus, especially of people who are doing SOMETHING productive having > to do with PyPA (teaching, answering questions online or in person, running > key infrastructure, writing documentation, making or fixing software, > etc.). > >> > >> I would post a final message to this list, marking its close and > suggesting that people use distutils-sig or discuss.python.org instead. > >> > >> Then, I would stop members from posting to this Google group. That is, > I would stop
Re: Documentation question about meta-variables
Hey Steve, сб, 9 трав. 2020 о 21:56 Steve Kelem пише: > Still, I'm not a newbie. I have a PhD in Computer Science, with a minor in > programming languages. I have been programming professionally for close to 50 > years. I find the typography on the python website unclear, because it's > overloaded. In some places, dark-green constant-width fonts mean literals. In > other places, it's used for meta-variables. > The Sphinx theme is here: https://github.com/pytest-dev/pytest/tree/master/doc/en/_themes. You may want to take a look at the pygments config and see if you can suggest any coloring changes. It'd probably require an issue on GitHub to see if the core team will accept your proposal, followed by a pull request that implements the changes. > If the python typographic conventions are widely known, can you show me where > they are stated? How can someone who knows computer languages find out these > widely-known facts? > I meant that *cls* argument name is common for *@classmethod*s, don't know about the typography but it probably shouldn't differ from any other variables/arguments. Sometimes it's also called *class_* or *klass*. > By the way, I checked my O'Reilly Python books, which I believe are the de > facto standards, and there's no "cls" in the indices. The O'Reilly books have > a section, Font Conventions, that makes explicit what each font means, and > sticks to it in all their books. Even though it's used in all their books, > they make sure to document their conventions and use them consistently so > that they communicate, unambiguously, to their readers. > I feel like we misunderstood each other here. *cls* does not have any special meaning. It's just a method argument name and that's it. Also, nobody colors things manually, highlighting is done automatically by pygments library. You can customize the colors for the different types of tokens but you cannot change the semantical meaning of just one instance of the variable name to look different from other variables. FWIW here's a few refs to help you figure out how *@classmethod* decorator works in Python: * https://www.youtube.com/watch?v=9rKx-8bj-R0 * https://youtu.be/HTLu2DFOdTg?t=1421 * https://stackoverflow.com/a/1669524/595220 * https://realpython.com/instance-class-and-static-methods-demystified/#class-methods * https://docs.python.org/3/library/functions.html#classmethod -- Kind regards, Sviatoslav Sydorenko email: sviatoslav+/nospam/~@sydorenko.org.ua --- https://useplaintext.email/ () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments --- -- You received this message because you are subscribed to the Google Groups "pypa-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to pypa-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pypa-dev/CAFYONRD_xxErroyVazo5VpZE2Ud61Eqtz-rDVv729uhCU%2Bz-3g%40mail.gmail.com.
