by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Anna Liao
    @anna-liao
    that's ok. I've never used the term bushed, but I can sympathize
    sure I will post some questions here for later
    Anna Liao
    @anna-liao
    Issue #1:
    Issue 1:
    In manual tox on my MacOS, test_base() passes
    However, in Travis CI, it complains about needing a bytes input, not str input
    When I trace that error, it comes down to this call in pyslet.vfs.py: https://github.com/anna-liao/pyslet/blob/gift-support/pyslet/vfs.py#L963
    os.sep is a <str>
    When I change that definition to:
    Anna Liao
    @anna-liao
    sep = os.sep.encode()
    This makes sep a bytes type
    however, then it doesn't pass my manual tox
    And also, vfs.py is from the original pyslet modules that I haven't modified
    so it really should just be sep = os.sep, not sep = os.sep.encode()
    but I don't know why it is trigger a type error
    Anna Liao
    @anna-liao
    I will add any more that I encounter
    Anna Liao
    @anna-liao
    I don't know why but I'm not getting email notifications from gitter when you post here, so feel free to just email me at aliao22@gmail.com if you need my attention here.
    John Vandenberg
    @jayvdb
    nice write up of your current issues. dont worry about issue 1. that is a py2/py3 issue, and I'll create a branch with the fix for that one
    I think we can provide some guidance on Issue 3: validation
    at a glance, issue 2 & 4 are pure parser issues, and they are yours to debug. sorry ;-)
    Anna Liao
    @anna-liao
    ok, I will ignore 1 for now
    Thanks, I can use some guidance on validation
    I will look to change the parser then
    and then worry about validation
    Think validation should come after the parser is working for well-formed and valid types
    John Vandenberg
    @jayvdb
    I think we were planning on having another voice chat today-ish. Im back in Indonesia, and it is 11pm, but I am online for another few hours
    Anna Liao
    @anna-liao
    oh ok
    So I re-wrote the parser
    and it handles more question types
    I'm thinking about adding feedback nested in a *Response element
    But I'm not sure how to do that
    Also working on reading in a document
    Previously, I instantiate an Element and then add children to that Element
    Usually the document root is an Element
    however, adding a child to the document, is replacing the document root
    which is strange. This is why when I parse a GIFT format text from a file, it only shows the last element
    I still don't understand why it is defined as such in Pyslet
    And there is also adding validation
    John Vandenberg
    @jayvdb
    in XML, the document root is a special node which contains all the other nodes, directly or indirectly.
    it will include things like the preamble , which isnt a typical element.
    Anna Liao
    @anna-liao
    I would have thought it would make sense when adding a child element to the document root, it would be adding a child to the document root Element. However, it seems that it replaces it.
    There is just a few ways to go
    I could work on reading in a file
    work on adding more supported types
    or work on validation
    John Vandenberg
    @jayvdb
    can you print out a 'tree' of a parsed QTI document ?
    Anna Liao
    @anna-liao
    Hmm, I guess I could try that
    I could just run the QTI sample and see what it looks like