Open CoderFromCali opened 1 year ago
good thought about not using explicit versions in the requirements.txt
file. i was going to make that change, however, i've had a couple reports of header files working and then all of a sudden not.
in both cases, the reason was because of both had the latest stable version of chrome (v110) and/or package versions. i did some testing on my end and can re-create those results (i.e. errors).
it appears southwest has found a way to detect header files coming from those instances. so the fix was to revert to chrome v109 and the exact package versions in requirements.txt
.
for those stumbling on this thread, see the workaround here:
is it possible to package all requirements and dependencies into a docker container ? That will help people who are not very good with python.
is it possible to package all requirements and dependencies into a docker container ? That will help people who are not very good with python.
it is possible, however, the script doesn't currently work, and i don't have the time to troubleshoot.
right now, i'd recommend you use this working alternative (which has a docker container option):
I just installed this repo but ran into this error:
It seems that the
undetected-chromedriver
v3.1.7 that is specified by this repo is out of sync with the version ofgoogle-chrome-stable_current_amd64.deb
(v110.0.5481.77-1) that was downloaded when I installed. I was able to fix this by upgrading toundetected-chromedriver
v3.4.6 with the commandenv/bin/pip install undetected-chromedriver --upgrade
in thesouthwest-headers
directory.It may be better not to hard-code the version of
undetected-chromedriver
in therequirements.txt
file if you will be downloading the latest version ofgoogle-chrome-stable_current_amd64.deb
. Instead, letpipj
download the current version ofundetected-chromedriver
as well.