There are a number of open source Python projects that have vendors associated with them (or large corporate users). OpenStack is one such example, but there's also various scientific libraries, e.g., NumPy/scipy that may better suited to your background. Typically open source-heavy companies are more open to remote/distributed work: I am not saying working remotely full-time, but something along the lines of working on site for the first six months (to prove yourself) and then working remotely most of the time/flying in on site for one week a month.
Consider this: identify several such projects along with the companies that are heavily involved in these projects open source communities, i.e., ones that are actually contributing and/or heavily modifying them.
First, send a patch, do something to "get your feet wet". Then pick a substantial sub-project (not something trivial), start contributing to it and at the mean time contact the engineer/managers working at associated companies (as not to be trapped in the HR resume black-hole). In the interview, at least mention the work you're doing.
Chances are they will be willing to fly you out to interview and help relocate. Be honest with them and say that (due to family reason) you'll need to at the very least travel.
In the worst case, you could do the reverse of working remotely/visiting the office frequently: rent a room in the remote area, work in the office most of the time, travel to Michigan for weekends/a week at a time: this will be difficult, but at the very least you'll be able to establish more "formal" experience and industry connections that you could translate into a more sustainable arrangement later (don't, however, start a position knowing that you won't be able to stick for at least a year and a half to two years: that would not very ethical, especially since you're looking for a company that will invest in your career). Of course, some family situations, e.g., elder care won't allow for that. In that case, still the advice applies: you're far more likely to find a remote-work scenario in an open-source related company than elsewhere.
Consider this: identify several such projects along with the companies that are heavily involved in these projects open source communities, i.e., ones that are actually contributing and/or heavily modifying them.
First, send a patch, do something to "get your feet wet". Then pick a substantial sub-project (not something trivial), start contributing to it and at the mean time contact the engineer/managers working at associated companies (as not to be trapped in the HR resume black-hole). In the interview, at least mention the work you're doing.
Chances are they will be willing to fly you out to interview and help relocate. Be honest with them and say that (due to family reason) you'll need to at the very least travel.
In the worst case, you could do the reverse of working remotely/visiting the office frequently: rent a room in the remote area, work in the office most of the time, travel to Michigan for weekends/a week at a time: this will be difficult, but at the very least you'll be able to establish more "formal" experience and industry connections that you could translate into a more sustainable arrangement later (don't, however, start a position knowing that you won't be able to stick for at least a year and a half to two years: that would not very ethical, especially since you're looking for a company that will invest in your career). Of course, some family situations, e.g., elder care won't allow for that. In that case, still the advice applies: you're far more likely to find a remote-work scenario in an open-source related company than elsewhere.