Solution exception:time data does not match format data

Replies to This Discussion

Permalink Reply by djordje on February 6, 2017 at 5:10am

Hi Abraham,

Thank you for reporting this!
Judging by the text you posted the "versionDate" method seems to be getting the correct date format, but your ironpython's strptime function is failing to work for some reason.

I wonder if this has to do with you having some other ironpython version installed on your PC.
Do you by chance have Dynamo installed as well?

Can you please try running the same .gh file on some other PC (without Dynamo installed there)?

Also, can I ask you to open the attached file below and let me know which error does it return?

Thank you once again.

Attachments:

• version_test.gh, 8 KB

Permalink Reply by Abraham Yezioro on February 6, 2017 at 12:03pm

Hi Djordje,

I do have Dynamo installed on my laptop. I tried in another plugin and it runs ok.

I opened the version_test file and both components gave errors:

The top one:

version:  2.7.5 (IronPython 2.7.5 (2.7.5.0) on .NET 4.0.30319.42000 (64-bit))version info:  sys.version_info(major=2, minor=7, micro=5, releaselevel='final', serial=0)Runtime error (ValueErrorException): time data does not match formatdata=JAN/30/2017, fmt=%m/%d/%Y, to: M'/'d'/'yyyyTraceback:  line 8, in scriptds

The bottom one:

Runtime error (ValueErrorException): time data does not match format
data=JAN/30/2017, fmt=%m/%d/%Y, to: M'/'d'/'yyyy
Traceback:
  line 4, in script

Thanks,

-A.

Permalink Reply by djordje on February 6, 2017 at 12:16pm

Thank you for running the test Abraham!

What do you mean you by: you tried it in another plugin and it runs ok?
You tried it on another PC?

What is the version of Rhino 5 which raises the upper message, and what is the version
of Rhino 5 where the component runs ok?

Permalink Reply by Abraham Yezioro on February 6, 2017 at 12:20pm

My mistake. I meant that I tried in another computer and it runs ok.

My Rhino version is 5 SR12 64b. I'm not besides the other computer but it is about the same.

Thanks,

-A.

Permalink Reply by djordje on February 7, 2017 at 9:57am

Thank you once again for the reply Abraham!

Rhino 5 comes with IronPython verion 2.7.0. Your previous screenshots and replies show IronPython 2.7.5 which means that you either have Rhino WIP installed on that same PC or maybe even Dynamo. Or manual installation of 2.7.5 version. Once you installed either of these they somehow "interfered" with IronPython 2.7.0.

For some reason the strptime function you posted in your first post fails to work on IronPython 2.7.5. I do not know why is that so, I need to ask IronPython support.

Still in case I get the answer: Gismo is at the moment targeted towards Rhino 5, and I won't be making it work on Rhino WIP until Rhino 6 is released. So it may be that I can not solve your issue, unless you either use a different PC, or uninstall Rhino WIP and Dynamo (I understand that this is highly unlikely).

I deeply apologize for this kind of inconvenience.

Permalink Reply by Abraham Yezioro on February 7, 2017 at 10:49pm

Hi Djordje,

Thanks for your reply. As a result of it i tried the following:

Uninstall Dynamo: No help. Still the same error.

Uninstall Python 2.75: Now it works!!

No need to uninstall Rhino 6 WIP.

I'll check installing back dynamo and see what happens. In case it spoils again i'll report.

Though it is weird that from IP2.70 to 2.75 will bring things to fail.

Attached the image of the version_test file. The top one is fine now, the bottom one fails differently from the previous test results.

Thanks again,

-A.

Permalink Reply by djordje on February 8, 2017 at 2:49am

Hi Abraham,
The upper ghpython component is what "OSM Shapes" and other Gismo components currently use.
The bottom one can fail, it's not currently important.
Thank you again for the testing!

Permalink Reply by Abraham Yezioro on February 8, 2017 at 3:01am

Hi Djordje,

Another update FYI:

In my desktop computer i have Rhino5 SR12, Dynamo installed and updated for today, Python 2.7 and it works.

Tempted to update Python to something else just to check, but maybe not now ... :-) There is an official 2.7.13 version, and can't find 2.7.0, so for now i'll stay safe in base.

-A.

Permalink Reply by djordje on February 8, 2017 at 3:08am

EDIT: Something is definitely wrong with Ning forum this days.
Sorry for having to add another reply.

No problem! If it works, then leave it that way.
I think it is safe to conclude that IronPython 2.7.5 was the causing the issue. I will if I can get an answer on why is this so.