Vivek, the repository has moved to https://github.com/beancount/beanprice
Would you like to resubmit it there?


On Sun, Dec 20, 2020 at 12:48 PM [email protected] <[email protected]>
wrote:

> Hi Ghanashyam,
> Yes, during the migration from bitbucket to github Martin Blais moved it
> to
> https://github.com/beancount/beancount/tree/pr128_seltzered_beanpriceupdate
> . It hasn't been reviewed/accepted yet, but perhaps it could be updated so
> it's easier to consider again. I haven't had time to touch beancount this
> year so that is the latest commit.
>
> On Saturday, December 19, 2020 at 11:27:13 PM UTC-8 [email protected]
> wrote:
>
>> Hi Vivek, Do you have this update? The bitbucket link is not available
>> anymore. Curious if this feature was ever reviewed and accepted, seems like
>> a very good feature
>>
>> On Sunday, 19 January 2020 at 21:33:06 UTC-8 [email protected] wrote:
>>
>>> Hi Andrzej! Nice to hear you're interested in the price update feature.
>>> There was some discussion between me and Johannes Harms late last year in a
>>> related issue ( 
>>> https://bitbucket.org/blais/beancount/issues/329/bean-price-support-fetch-over-range-of
>>> )  We may want to continue discussion there - last thing we were looking
>>> into was optimizing how a bunch of historical prices are fetched.
>>>
>>> I honestly don't know how the review process works for beancount, I've
>>> just been using my own fork in the meantime, so a script like Justus uses
>>> may be a better solution for your needs.
>>>
>>>
>>> On Sunday, January 19, 2020 at 6:46:09 PM UTC-8, Justus Pendleton wrote:
>>>>
>>>> On Monday, January 20, 2020 at 5:14:13 AM UTC+7, Andrzej wrote:
>>>>
>>>>> Alternatively, does anyone know if there a tool that does something
>>>>> similar but is outside of beancount main repository? (I'm not a fan of
>>>>> maintaining my own fork of beancount for this patch)
>>>>>
>>>>
>>>> Vivek mentioned in his original post that people wrote their own
>>>> scripts, so you could just do that. Depending on what you want, it isn't
>>>> especially complicated. Here's one I had for when I wanted to populate the
>>>> price map with historical data.
>>>>
>>>> If uses gdate because I usually run it on a mac. If you wanted to
>>>> update prices weekly instead of daily, just change the "+ 1 day" to
>>>> something else.
>>>>
>>>> #!/bin/bash -e
>>>>
>>>> DATE=gdate
>>>>
>>>> if [ -z $1 ]; then
>>>>   echo "Must supply start date, e.g. 1983-05-22"
>>>>   exit 1
>>>> else
>>>>   from=$1
>>>> fi
>>>>
>>>> if [ -z $2 ]; then
>>>>   to=$(${DATE} -I)
>>>> else
>>>>   to=$2
>>>> fi
>>>>
>>>> d=$from
>>>> while [ "$d" != "$to" ]; do
>>>>   echo Fetching prices on $d...
>>>>   bean-price --date $d my.beancount >> prices.beancount
>>>>   d=$(${DATE} -I -d "$d + 1 day")
>>>> done
>>>>
>>>> --
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/b471b460-1e64-47f1-91a0-4aba5789aa59n%40googlegroups.com
> <https://groups.google.com/d/msgid/beancount/b471b460-1e64-47f1-91a0-4aba5789aa59n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhMm92DhtngdawWwh%2BnsUpiyPxnEPJKTRtNFn62pZ7YptQ%40mail.gmail.com.

Reply via email to