Option wanted to parse float numbers as symbols.

[kazssym]

I want an option to parse float numbers (or atoms that are looking so) as Symbols to distinguish 1.1, 1.10, 1.100 etc.

[kazssym]

Something like this one: kazssym@3e57dcd

[tkf]

I think float_to is better. Default float_to=None means to use the value of float(token). You can pass any callable including Symbol.

If you add some tests, doctest example and document I will pull the change.

[kazssym]

I don't like the name as it could imply that it first parses a token as
float and then converts it to something.

[tkf]

We are talking about parser. float_to should mean "float literal to", not "float value to". Converting to float value to something need not be done in parser as you can do it afterward. User will never lookup sexpdata document to convert float values.

[kazssym]

I don't see it as a float literal either, but as a pair of integers
concatenated with a dot. So I would prefer a name that I could think as if
any float number is disabled in the S-expression. Sorry for the confusing
title.

If you don't like the idea, feel free to forget my request. I can just
copy and modify your code to suit my needs.

[tkf]

You can use float_to to fit your need. It is easy to see that you are not parsing (or interpreting) float from load(..., float_to=Symbol). I don't understand why you don't like my idea. It is more extensible than yours.

I think forking is very bad idea. It took sometime for this project to mature (even though parsing sexp is easy). I wouldn't want to pay the price for the future merges if I were you.

[kazssym]

I don't like forking either. But your suggestion is too complicated for my
needs and I'm not sure I can complete such a change in time as I'm still a
Python learner.

So for now, I will copy your code into my project with minimal
modifications (just removal of several lines). When I get enough skills in
Python later, I could be back to a more extensible approach.

Thank you for considering my request.
2013/07/07 3:47 "Takafumi Arakaki" notifications@github.com:

You can use float_to to fit your need. It is easy to see that you are not
parsing (or interpreting) float from load(..., float_to=Symbol). I don't
understand why you don't like my idea. It is more extensible than yours.

I think forking is very bad idea. It took sometime for this project to
mature (even though parsing sexp is easy). I wouldn't want to pay the price
for the future merges if I were you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-20558882
.

[tkf]

OK. Makes sense. I think I'll try to implement my suggestion at some point. I'll let you know when it happens.

Just curious. What kind of software are you developing using sexpdata?

[kazssym]

Excuse my replying late. I'm working on a VCS repository converter from
PRCS to Mercurial. PRCS stores its version information in S-expressions
and I was looking for a parser.
2013/07/09 18:03 "Takafumi Arakaki" notifications@github.com:

OK. Makes sense. I think I'll try to implement my suggestion at some
point. I'll let you know when it happens.

Just curious. What kind of software are you developing using sexpdata?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-20661552
.

[tkf]

Nice. Good luck!

[tkf]

Actually let this open to track the issue :)

[kazssym]

It would be more general and extensible to have one such as numeric=[int, float]. If a user want complex numbers in addition, he can call with numeric=[int, float, complex]. numeric=None could be interpreted as numeric=[int, float].

[jd-boyd]

Given the age and that I'm not sure it really is in scope, I'm going to close this. Someone can bring it up again if they want.