Brian Hartvigsen
Brian Hartvigsen
`createTempDirectory` has the same behavior and root cause (both `createTempDirectory` and `createTempFile` leverage `generatePath` under the hood)
Might want to look at #141 where I updated all this to the latest schema definitions.
With dnspython 2.4.2 and python 3.10.13, this fix makes no difference as far as I can tell. I'm still getting ``` "v=spf1 ip4:23.253.182.103 ip4:23.253.183.145 ip4:23.253.183.146 ip4:23.253.183.147 ip4:23.253.183.148 ip4:23.253.183.150 ip4:166.78.68.221 ip4:167.89.46.159...
You might take a look at https://github.com/tresni/sender_policy_flattener . I did a few other things before I gave up and went with a service. There are several more issues with this...
fix: Use the event start time zone to create rules so that daily rules don't end up on the wrong day
#77 also causes a weird change in the number of evs in that test when I was testing it locally. I imported that calendar into Google Calendar and it agreed...
@jacobbednarz Totally understand, I'm somewhat hoping that this pushes someone to update the docs. The current docs don't match the current response data from the API and it's not directly...
Any chance the documentation will be updated anytime soon? This has now been at least 9 months since the documentation for your registrar endpoint stopped aligning with the output actually...
Pinging now after 18 months since my PR was opened. The API documentation still does not match the actual API responses.
Check your locale settings, make sure it's something like utf-8 as right now it looks like your terminal emulator is setting it to ascii.