Closed jjzieve closed 2 years ago
Do we need the entire Requirements section at the top of the readme? It seems a bit "in your face". Maybe the disclaimer at the top that "GTCtoVCF is currently only known to work with python2.7" is suffice
I sorta remember users having issues with wrong package versions used as well, not just the python version. The python version is a requirement, so it makes sense to me to keep it in that section instead of just being randomly on its own. I'd rather be "in your face" about everything necessary to run the script upfront than make it maybe more "friendly" by having the requirements at the bottom.
Do we need the entire Requirements section at the top of the readme? It seems a bit "in your face". Maybe the disclaimer at the top that "GTCtoVCF is currently only known to work with python2.7" is suffice
I sorta remember users having issues with wrong package versions used as well, not just the python version. The python version is a requirement, so it makes sense to me to keep it in that section instead of just being randomly on its own. I'd rather be "in your face" about everything necessary to run the script upfront than make it maybe more "friendly" by having the requirements at the bottom.
Ok, sounds good to me
Do we need the entire Requirements section at the top of the readme? It seems a bit "in your face". Maybe the disclaimer at the top that "GTCtoVCF is currently only known to work with python2.7" is suffice