Re: [cti-users] Re: [EXT] Re: [cti-users] CTI Python libraries and Python 2.6

[Terry MacDonald <terry.macdonald@gmail.com>]

We'd prefer python 3.

But it's more than that. It's what versions of python you have to support. There'll be some older platforms that people wish to update to STIX 2 without updating the whole platform to python 3. An example for us would be the Cosive STIX data generator. 

So we'll need python 2.7 in the short term, but we'd prefer python 3...

Cheers

Terry MacDonald

Cosive

On 11/04/2017 07:40, "Bret Jordan" <Bret_Jordan@symantec.com> wrote:

I guess I would ask the question this way, for this community.  

For those implementing a STIX 2.0 and TAXII 2.0 solution, who will be using the MITRE libraries, which version of Python would you prefer:
 
1) 2.6
2) 2.7
3) 3.x  

Bret

---

From: cti-users@lists.oasis-open.org <cti-users@lists.oasis-open.org> on behalf of Terry MacDonald <terry.macdonald@cosive.com>
Sent: Monday, April 10, 2017 1:30:26 PM
To: Back, Greg
Cc: cti-users@lists.oasis-open.org; Raphaël Vinot
Subject: [EXT] Re: [cti-users] CTI Python libraries and Python 2.6

 

I think we can lose python 2.6, but I agree that python 2.7 will be around for a while.

Cheers

Terry MacDonald

On 11/04/2017 02:57, "Back, Greg" <gback@mitre.org> wrote:

I would love for the libraries to be 3.3+ only, and I agree that it is prudent for people to start planning a migration from Python 2 to Python 3 now, before 2020. I’m thrilled that MISP is already switching to be Python 3 only.

Realistically, I believe a significant portion of users will be using 2.7 for several more years, and some may even still be using 2.6 (hence my question).  The Python library for STIX 2 is currently under development [1], and will support at least Python 2.7 (if not Python 2.6 also). If you (or anyone else) are interested in helping, we’d love the help. Check out the contributing guide [2] or send me an email if you’d like to help or have any feedback.

My question also applies to the older (python-stix, python-cybox, libtaxii, etc.) libraries, where we are still trying to fix bugs that users find, even if we aren’t actively adding new features. Those libraries already support Python 2.6. We could drop 2.6 support if no one needs it, which is part of why I asked my question.

Greg

[1] https://github.com/oasis-open/cti-python-stix2
[2] https://stix2.readthedocs.io/en/latest/contributing.html

On 2017-04-10, 9:10 AM, "Raphaël Vinot" <raphael.vinot@circl.lu> wrote:

    Short answer: nope, even python 2.7 is not relevant IMO

    As we speak, we are far from having a usable Python library for STIX 2.0
    so backporting code to EOL (or close to EOL) languages is useless.

    FYI, we will remove python2 support to all MISP libraries this year.

    Cheers,
    Raphaël


    On 04/06/2017 07:02 PM, Back, Greg wrote:
    > Hi-
    >
    >
    >
    > If you currently use any of the Python libraries for STIX, TAXII, or
    > CybOX (either the older 1.x libraries or the newer 2.0 libraries) with
    > Python 2.6, please let me know. The information will help me determine
    > what level of effort (for both new development and ongoing support) we
    > should be putting into supporting Python 2.6.
    >
    >
    >
    > (Yes, I know Python 2.6 is officially end-of life.)
    >
    >
    >
    > Greg Back
    >
    > MITRE
    >

    --
    Raphaël Vinot
    CIRCL - Computer Incident Response Center Luxembourg

    41, Avenue de la Gare
    L-1611 Luxembourg

    (+352) 247 88444 - info@circl.lu - www.circl.lu