Thanks! I'll keep in on list as long as no one feels spammed :) And I'm very glad you asked about support -- it's been on our minds a lot lately.
I did some more digging on the ForcedTimeZone test. No issues on your end! That test gets skipped, and the test runner emits `datetime.datetime.min`. This confuses the uploader. There's agreement over on NUnit <https://github.com/nunit/nunit/issues/2339> for their implementation to start emitting the current time instead of DateTime.Min, and I've raised an issue <https://github.com/xmlrunner/unittest-xml-reporting/issues/168> with the xmlrunner folks to make the same change. I'm also going to see if I can track down the right person to be more liberal in what the uploader accepts. On Thu, Jul 12, 2018 at 9:40 AM Carlton Gibson <carlton.gib...@gmail.com> wrote: > Hi Matt, > > The settings files from the django-box project are here: > https://github.com/django/django-box/tree/master/roles/djangodata/files > If you look in each, you'll see they basically just redefine the > connection details for the 'default' and 'other' DB. > (There's not much more to it really.) > > You can see supported Python versions here: > https://docs.djangoproject.com/en/dev/faq/install/#what-python-version-can-i-use-with-django > For master it's now just Python 3.5-3.7. > > > tests.timezones.ForcedTimeZoneDatabase generates output with an invalid > timestamp... > > Not sure what that's about, but if you think there's an issue our end open > a ticket at https://code.djangoproject.com. > > > ... what issues you faced ... > > None in particular. My observation was more from a UX perspective. VSTS is > all built around the idea you host on visualstudio.com > but if you don't do that whole areas are blank (and a bit > superfluous/confusing). It seems to have changed a bit, I see. :) > > Finally: > > > I'm confident we can put something together in terms of resources for > the DSF... > > Great! Of course we don't have to talk about it now. (It was more a > speculative ask.. :-) > > I think we're OK to discuss here if it's not too noisy. Otherwise do hit > me off-list. > (Is there no VSTS messaging...? You could create an issue on your GitHub > clone and @mention me. :-) > > Kind Regards, > > Carlton > > -- > 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/oDgv_Ztgd4s/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 https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/5f1b112b-212e-413f-aa8d-e97553b7538d%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/5f1b112b-212e-413f-aa8d-e97553b7538d%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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAGtApQXLMT-rSgFyHBMEFSzh%3DDo50wvBxssTAzzREGS2rHAMag%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
