Re: Bringing some popular must have django tools/packages under django org umbrella
2016-03-16 6:24 GMT-03:00 James Pic : > What do you mean stuck? Aren't you supposed to port the packages and > submit a patch in that case? How are you stuck ? > Alright... I don't know you but no, that doesn't quite work that way. Even if I submit a patch I wouldn't be able to: - Merge it into mainline. - Upload the patched version to pypi. So it's a no-starter, I can't rely on my fork, not for production, as I should guarantee that the package it's, at least, as tested as mainline, which usually involves non-trivial infrastructure. > I know the first portings are hard but once you've ported a dozen it > becomes piece of cake so don't be afraid of trying ! And please contribute > to the apps !! > > I know some people who only open issues and never submit a patch on > github, isn't that super annoying? > Really? you go around asking users to do the work of maintainers? > On Mar 16, 2016 5:38 AM, "Matías Iturburu" wrote: > >> I recently got stuck upgrading a project to 1.9 due to a lot of useful >> packages being not maintained: >> >> - django-endless-pagination: a substitute for django-pagination while it >> didn't had python3 support >> - django-taggit-templatetags: from when django-tagging didn't had python3 >> support. >> >> django-registration was another must have that recently resurfaced but >> the same situation spawned django-registration-redux. >> >> Would it be too much a hassle to open an django-contrib organization with >> less friction provide support for orphaned projects? >> >> 2015-11-24 16:27 GMT-03:00 Marc Tamlyn : >> >>> This is something the core team discussed in Amsterdam. I believe there >>> was consensus to trial it with Django registration. I should catch up with >>> James and see if it is transferred. If this goes well I see no reason why >>> not. >>> >>> The biggest problem is the selection of packages, we have historically >>> wanted to avoid too much bikeshedding. Initially it's likely to be mostly >>> relatively inactive small utilities I think. But I think we are open to >>> being more risky here. >>> >>> M >>> On 24 Nov 2015 7:02 pm, "Asif Saifuddin" wrote: >>> >>>> The projects will have the official tool status + the maintainer of the >>>> projects will be able to collaborate better with django core team? less >>>> risk of being abandoned by the maintainers etc. >>>> >>>> IMHO >>>> >>>> On Wed, Nov 25, 2015 at 12:31 AM, Collin Anderson >>> > wrote: >>>> >>>>> Hi, >>>>> >>>>> Say a little bit more: What would be the goal? What would you hope >>>>> would be accomplished by doing this? >>>>> >>>>> Thanks, >>>>> Collin >>>>> >>>>> On Tuesday, November 24, 2015 at 1:27:11 PM UTC-5, Asif Saifuddin >>>>> wrote: >>>>>> >>>>>> How is the idea? tools like django-debug-toolbar, django-silk, >>>>>> django-taggit, django-filter etc and some more de facto tools under the >>>>>> umbrella of django github org? >>>>>> >>>>>> Regards >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "Django developers (Contributions to Django itself)" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/django-developers/bIzfHebE2sw/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> django-developers+unsubscr...@googlegroups.com. >>>>> To post to this group, send email to >>>>> django-developers@googlegroups.com. >>>>> Visit this group at http://groups.google.com/group/django-developers. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/django-developers/70062405-3ccd-49b2-9118-ec1679203cd1%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/django-developers/70062405-3ccd-49b2-9118-ec1679203cd1%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> You received this message bec
Re: Bringing some popular must have django tools/packages under django org umbrella
2016-03-16 12:39 GMT-03:00 James Pic : > FTR, there's also Djangonauts which have been there for a while: > https://github.com/djangonauts > > This is exactly what I was asking for when I asked if there was an organization to pick on unmaintained projects. Thank you very much. > Sorry, I tried not to look uncivil - and yet I fail to see where I > was, but definitely re-reading and thinking about it (I'm not an > english native speaker). Please anyone feel free to PM me and point me > to where I was uncivil. > > Best ;) > > James > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CALC3KadbC%2B5QcScijB1a0yRFwuS9%3DRgXBdk8HrHaNvBy1qdWRA%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Matías Iturburu http://www.linkedin.com/in/tutuca | http://ltmo.com.ar -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CACPy_ubZ2Vfn1CzHsS61x0uw%2BBTXDLqA5-2eS-yHAN7ApAnQ9g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Bringing some popular must have django tools/packages under django org umbrella
I recently got stuck upgrading a project to 1.9 due to a lot of useful packages being not maintained: - django-endless-pagination: a substitute for django-pagination while it didn't had python3 support - django-taggit-templatetags: from when django-tagging didn't had python3 support. django-registration was another must have that recently resurfaced but the same situation spawned django-registration-redux. Would it be too much a hassle to open an django-contrib organization with less friction provide support for orphaned projects? 2015-11-24 16:27 GMT-03:00 Marc Tamlyn : > This is something the core team discussed in Amsterdam. I believe there > was consensus to trial it with Django registration. I should catch up with > James and see if it is transferred. If this goes well I see no reason why > not. > > The biggest problem is the selection of packages, we have historically > wanted to avoid too much bikeshedding. Initially it's likely to be mostly > relatively inactive small utilities I think. But I think we are open to > being more risky here. > > M > On 24 Nov 2015 7:02 pm, "Asif Saifuddin" wrote: > >> The projects will have the official tool status + the maintainer of the >> projects will be able to collaborate better with django core team? less >> risk of being abandoned by the maintainers etc. >> >> IMHO >> >> On Wed, Nov 25, 2015 at 12:31 AM, Collin Anderson >> wrote: >> >>> Hi, >>> >>> Say a little bit more: What would be the goal? What would you hope would >>> be accomplished by doing this? >>> >>> Thanks, >>> Collin >>> >>> On Tuesday, November 24, 2015 at 1:27:11 PM UTC-5, Asif Saifuddin wrote: >>>> >>>> How is the idea? tools like django-debug-toolbar, django-silk, >>>> django-taggit, django-filter etc and some more de facto tools under the >>>> umbrella of django github org? >>>> >>>> Regards >>>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/django-developers/bIzfHebE2sw/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> django-developers+unsubscr...@googlegroups.com. >>> To post to this group, send email to django-developers@googlegroups.com. >>> Visit this group at http://groups.google.com/group/django-developers. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/70062405-3ccd-49b2-9118-ec1679203cd1%40googlegroups.com >>> <https://groups.google.com/d/msgid/django-developers/70062405-3ccd-49b2-9118-ec1679203cd1%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CAKAqTgrnMoqy-%3DdDUx31Dgru6XTzT3e-T%3DhspY-CDK5tV9k1gQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-developers/CAKAqTgrnMoqy-%3DdDUx31Dgru6XTzT3e-T%3DhspY-CDK5tV9k1gQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAMwjO1FzQ8cCgF7pR%2BRtPiSkNc5W4ipeWfwLz0hi4q_xzxZoAQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAMwjO1FzQ8cCgF7pR%2BRtPiSkNc5W4ipeWfwLz0hi4q_xzxZoAQ%40mail.gmail.com?utm_medium=email&utm_source=
Re: Again,How to add some attributes to model object when initialize model in QuerySet?
This list is not for "how to" questions, please refer to django-us...@googlegroups.com. On Mon, Jun 14, 2010 at 10:22 PM, Cheney Pang wrote: > I need to go check out the related data of current data QuerySet and > set these into the model objects as attribute in the way, I know this: > > for row in self.query.results_iter(): > .. > > in iterator(self).but I can't do that,because it will lead to nested loops > . > > how to do that? thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- Matías Iturburu http://www.linkedin.com/in/miturburu -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
