dateparser | lightweight JavaScript date library for parsing | Date Time Utils library

I am attempting to determine the OAS of of a callable bond in QuantLib. However, my results are always negative!?

I am wondering if there is some issue in the call schedule, as the bond yield returned from pricing the bond under the Hull White model seems to be reasonable.

Consider the following bond contract:

Trying to get search_dates from dateparser.search ignore relative dates like "tomorrow", "next week", "more", etc.

Currently, here's the behavior I'm getting:

So I manually installed a locally downloaded python package by going into the folder directory and using the cmd command:

python setup.py install

After that it just installed itself normally. Using the python function help("modules") in cmd also confirmed that it was installed correctly as I can see the name being given out. The two modules are called binance_d and binance_f

I am certain that this issue is down to my own ignorance of Python and pip, however, I have scoured the net and tried many things to get this to work, so far, to no avail.

I have a docker image based on the Bitbucket pipelines default image (version 2): atlassian/default-image:2, which uses Python 2.7.x. And SAM doesn't work with that, I looked at AWS' documentation and this said that the SAM CLI no longer supports Python 2.7.x, so I removed all Python installations from the docker container (debugging the Bitbucket pipeline locally) and attempted to make sure that there was only Python3 and pip3 installed (I even setup symlinks from /usr/bin/python to /usr/bin/python3 and from /usr/bin/pip to /usr/bin/pip3 - although, that seems like such a dumb thing to have to do).

I also tried doing the above with Python 3.6, as the error message (shown below) seemed to show a Python 'f-String' syntax, which according to Python's docs was introduced in 3.6.

Nothing I do seems to work and the more I look at this, the more I get tied up in an seemingly never ending web of Python versions and linux packages!

The error (and python versions) can be seen here:

I cannot understand how to use information on the current datetime in the code at the bottom. I calculated the current datetime as

I am attempting to include the dateparser package for a PySpark (v2.4.3) shell session by a short little zip build process pip install -r requirements.txt -t some_target && cd some_target && zip -r ../deps.zip . && cd .., after which I would, for example, pyspark --py-files deps.zip. When importing dateparser, though, I get an indirect ModuleNotFoundError from the regex library, whining that "No module named 'regex._regex'" (stack trace says this is referenced in /mnt/tmp/spark-some/long/path/deps.zip/regex/_regex_core.py line 21, which is of course referenced much farther up the stack by dateparser).

I attempted adding a flag to the dateparser line in requirements.txt like dateparser --no-binary=regex, but the error persisted. A normal python shell is able to import without issue, and other packages in this zip seem to be importable in PySpark shell without issue. This has led me down a number of rabbit holes, but I think/hope I have finally found the culprit: namely, that regex._regex is not a normal .py file, but rather a .so. My knowledge of python build process is limited, but it seems that regex library's setup.py uses the setuptools.Extension class to compile some C files into this shared object. I have seen suggestions to modify LD_LIBRARY_PATH environment variable in order to make those shared objects discoverable to python, but a number of comments also suggested this was dangerous and not a viable long-term solution. The fact that a normal python interactive session has no issue with the import also has me skeptical, since the LD_LIBRARY_PATH variable doesn't even exist in os.environ within that interactive shell. I'm thence left wondering if --py-files is insufficient for including packages that compile these Extension objects (seems unlikely, since there are a lot of people doing crazier things than my simple use case), or if this actually stems from neglecting some other setting.

Merci mille fois for any and all help :)

I have a bunch of data that I am parsing, and I've managed to get all of it into a database but there is one last part that is tripping me up, getting the date into the db in a "nice" format. If I can figure out how to extract just the date string from the data then it shouldn't be hard to use dateparser, but this part is really getting to me and my brain just doesn't know where to go.

This is the format of the data. There may be other key value pairs.

I have a such code:

This might be one of the more frustrating issues I've coped with in a while. Dates and -- in particular -- NgbDatepicker are a bit of a bear to deal with in Angular, in general.

I'm implementing NgbDatepicker against reactive forms in Angular 8, and the gist of my problem is that I can set the initial value of my date control, but that initial value doesn't show-up (visually) on the form. I can log my form to the console and see that the value is getting set, but the form field itself doesn't update. If I select a date from the picker itself then my selection reflects in the form field. I had thought it would be as simple as setting the [startDate] property of the ngbDatepicker input, but apparently no. I've tried a lot of different iterations on this; here's where things stand, code-wise:

My HTML: