vlasovskikh/funcparserlib

Issues

• Improve typing support for _TupleParser

  #80 opened 7 months ago by beekill95
  10

• `.parse` doesn't support arbitrary iterables

  #78 opened a year ago by Kodiologist
  0

• make_tokenizer tokenisers return generators, Parser expects sequences

  #44 opened 2 years ago by gsnedders
  3

• Backtracking

  #75 opened 2 years ago by Kodiologist
  3

• Make a new release

  #65 opened 3 years ago by Kodiologist
  33

• Write classic API docs

  #29 opened 3 years ago by GoogleCodeExporter
  3

• Write nicer guides: short and sweet

  #28 opened 3 years ago by GoogleCodeExporter
  2

• In the Tutorial, don't use "composition" to refer to fmapping a function with a parser

  #39 opened 3 years ago by rgleichman
  4

• funcparserlib 0.3.5 SyntaxError

  #72 opened 3 years ago by amal-khailtash
  2

• funcparserlib 0.3.6 install fails

  #71 opened 3 years ago by amal-khailtash
  2

• setup.py uses use_2to3 which is not supported in latest setuptools

  #70 opened 3 years ago by ronaldoussoren
  4

• Parse errors should say what tokens are legal at the stopped position

  #52 opened 3 years ago by Kodiologist
  14

• Including source information as part of the parse tree

  #68 opened 3 years ago by lsp-ableton
  1

• Some of the documenation files have a non-free license

  #64 opened 3 years ago by glaubitz
  7

• Installation fail with setuptools 58.0.2 with `error in funcparserlib setup command: use_2to3 is invalid`

  #69 opened 3 years ago by ikus060
  1

• Handle intrinsically circular grammars by parser-combinators decomposed to a set of modules.

  #40 opened 9 years ago by magniff
  1

• Create a raw parse tree pretty-printer

  #10 opened 4 years ago by GoogleCodeExporter
  3

• TypeError in `oneplus` when applying it `parser + parser`

  #66 opened 4 years ago by vlasovskikh
  1

• Parser similar to `maybe()`, but without a return value like `skip()`

  #62 opened 4 years ago by AndreasMatthias
  2

• Broken "Monadic Parsing in Python" blog link

  #47 opened 4 years ago by jkmacc-LANL
  0

• Tutorial not working

  #49 opened 4 years ago by sofianito
  3

• Problem Combining Operator | and Operator +

  #48 opened 8 years ago by xie-dongping
  3

• make_tokenizer doesn't deal with binary tokenizers

  #46 opened 8 years ago by gsnedders
  0

• Not followed by

  #43 opened 8 years ago by gsnedders
  1

• RPython compatible

  #37 opened 10 years ago by GoogleCodeExporter
  8

• Python's ** is right-associative, so should the tutorial calculator be.

  #38 opened 10 years ago by GoogleCodeExporter
  0

• Make parsing of LL(1) or LL(k) parts of the grammar faster

  #19 opened 10 years ago by GoogleCodeExporter
  3

• Make funcparserlib imports more compact

  #23 opened 10 years ago by GoogleCodeExporter
  1

• Make non-halting error messages easier to grasp

  #26 opened 10 years ago by GoogleCodeExporter
  1

• Doc links are unreachable

  #35 opened 10 years ago by GoogleCodeExporter
  4

• Show warning for non-LL(k) grammars

  #18 opened 10 years ago by GoogleCodeExporter
  3

• support py3

  #36 opened 10 years ago by GoogleCodeExporter
  1

• Python 3 compatibility

  #34 opened 10 years ago by GoogleCodeExporter
  3

• make unittest fails in python2.7

  #33 opened 10 years ago by GoogleCodeExporter
  3

• many() consumes too many tokens in some cases

  #31 opened 10 years ago by GoogleCodeExporter
  7

• Python 3 support

  #32 opened 10 years ago by GoogleCodeExporter
  1

• Bug in left recursion detection for JSON parser example

  #30 opened 10 years ago by GoogleCodeExporter
  1

• Rewrite tests from the examples as nosetests

  #27 opened 10 years ago by GoogleCodeExporter
  1

• Convert documenation into Sphinx format

  #25 opened 10 years ago by GoogleCodeExporter
  1

• [deleted issue]

  #24 opened 10 years ago by GoogleCodeExporter
  0

• left_recursive() misses left recursion hidden behind many() and maybe()

  #21 opened 10 years ago by GoogleCodeExporter
  1

• Write tests for LL(1) optimization

  #22 opened 10 years ago by GoogleCodeExporter
  3

• Clean up all the tok()-related stuff in funcparserlib.parser

  #20 opened 10 years ago by GoogleCodeExporter
  1

• Add primitive tok(type[, value]) instead of some()

  #16 opened 10 years ago by GoogleCodeExporter
  1

• Create full predictive LL(k) parser generator for LL(k) grammars

  #17 opened 10 years ago by GoogleCodeExporter
  2

• Could not get some information from exceptions

  #14 opened 10 years ago by GoogleCodeExporter
  3

• Optimize lexer by joining all the spec regexps into a giant regexp

  #15 opened 10 years ago by GoogleCodeExporter
  2

• funcparserlib raise syntax error in python 2.4

  #13 opened 10 years ago by GoogleCodeExporter
  5

• Positions in lexer error ouput are 0-based instead of 1-based

  #12 opened 10 years ago by GoogleCodeExporter
  2

• README mentions `setuptools` but setup.py doesn't require it

  #11 opened 10 years ago by GoogleCodeExporter
  2