4 ms·
What makes it difficult? My projects are all quite simple, but I do keep them compatible with both Python 2 and Python 3. All I had to do was create a setup.cf
by slavik81 10y ago
What makes it difficult? My projects are all quite simple, but I do keep them compatible with both Python 2 and Python 3.
All I had to do was create a setup.cfg that said:
[wheel]
universal = 1
To build, I use:
python setup.py sdist bdist_wheel
twine upload -s dist/*
The .travis.yml is just 7 lines. https://github.com/cgmb/guardonce/blob/v2.0.0/.travis.yml https://github.com/cgmb/guardonce/blob/v2.0.0/.travis.yml
- zzleeper 10y agoAre you using py3 exclusive features? If you are not, then you are not really using python 3 (tuple unpacking, etc.) If you want to do both, then you need pasteurize, and end up with a travis mess: https://github.com/sergiocorreia/panflute/blob/master/.travis.yml https://github.com/sergiocorreia/panflute/blob/master/.travi... To be honest, for me the morale of the story is that supporting py2 is just not worth it. I am not going to use it, so why support it at all?
- slavik81 10y agoInteresting. I do stick to Python 2 features, but put in some work to ensure my programs are valid Python 3. I'm not a very skilled Python developer, so the simplicity of that strategy is attractive. One thing that I notice is that your project is a library, while mine is a program. I wonder if that also plays a role.