Re: Simplified Python importing
On Fri, Mar 9, 2012 at 8:09 PM, John Wiegley jwieg...@gmail.com wrote: Simon Michael simon-jbxitmbj2llqt0dzr+a...@public.gmane.org writes: PS I'm not aware of any serious problem with the way I/hledger relates with the ledger community.. if anyone is, please let's discuss. I think hledger, and all that has gone on around it, has been a great companion to Ledger's goals and progress. I concur. It's also very reassuring to see multiple actively supported implementations of the same functionality that uses the same file format. In many ways, it's probably safer using ledger format files to store your financial data than a 3rd party tool that only has one implementation which may be closed source. This can also apply to the variety of unix kernels, or programming language implementations - more tools that do the same thing slightly differently provides choice and the ability to test design decisions in multiple directions simultaneously. - Zack
Re: Simplified Python importing
On 3/8/12 3:56 PM, David Whitmarsh wrote: On Wed, Mar 7, 2012 at 11:37, Simon Michaelsi...@joyful.com wrote: It's this word probably I don't like. For years we have been hearing people in #ledger trying to do this or that thing recommended by the docs which turn out to require a different ledger version or a different kind of build. I would like things to be definitely there or not there :) simplifying installation, reducing new user confusion/frustration and building more critical mass of people testing and discussing the same set of features. So you want free software which is written to scratch the itch of its main developer to stop adding features he wants to add? You've already forked it, if you want to chase ease of use/less frustration with your implementation then you should do that. I on the other hand appreciate the work John puts in to new features. Just a little honest feedback, of a kind I never see here, offered in case it might be useful to improve ledger, which I care about, contribute to, and want to thrive. I hoped John knows me well enough to not take offense, and I beg lenience... PS I'm not aware of any serious problem with the way I/hledger relates with the ledger community.. if anyone is, please let's discuss. -Simon
Re: Simplified Python importing
From my perspective as a noob to the community, you are nothing but a positive influence. The h/ledger split is the most amicable I've seen. Keep it up! On Mar 9, 2012 8:22 AM, Simon Michael si...@joyful.com wrote: On 3/8/12 3:56 PM, David Whitmarsh wrote: On Wed, Mar 7, 2012 at 11:37, Simon Michaelsi...@joyful.com wrote: It's this word probably I don't like. For years we have been hearing people in #ledger trying to do this or that thing recommended by the docs which turn out to require a different ledger version or a different kind of build. I would like things to be definitely there or not there :) simplifying installation, reducing new user confusion/frustration and building more critical mass of people testing and discussing the same set of features. So you want free software which is written to scratch the itch of its main developer to stop adding features he wants to add? You've already forked it, if you want to chase ease of use/less frustration with your implementation then you should do that. I on the other hand appreciate the work John puts in to new features. Just a little honest feedback, of a kind I never see here, offered in case it might be useful to improve ledger, which I care about, contribute to, and want to thrive. I hoped John knows me well enough to not take offense, and I beg lenience... PS I'm not aware of any serious problem with the way I/hledger relates with the ledger community.. if anyone is, please let's discuss. -Simon
Re: Simplified Python importing
Simon Michael simon-jbxitmbj2llqt0dzr+a...@public.gmane.org writes: Just a little honest feedback, of a kind I never see here, offered in case it might be useful to improve ledger, which I care about, contribute to, and want to thrive. I hoped John knows me well enough to not take offense, and I beg lenience... I certainly didn't take it that way. Consistency is awesome, I loves me some consistency. But 3.0 is still beta, which means: Let there be Flux. PS I'm not aware of any serious problem with the way I/hledger relates with the ledger community.. if anyone is, please let's discuss. I think hledger, and all that has gone on around it, has been a great companion to Ledger's goals and progress. John
Re: Simplified Python importing
It still happens, moving discussion to the bug report: http://bugs.ledger-cli.org/show_bug.cgi?id=672 On Wed, Mar 7, 2012 at 9:43 AM, John Wiegley jwieg...@gmail.com wrote: Paul Lathrop paul-rb2b2ncu2mk6lbifqvfbzv6hyfs7n...@public.gmane.org writes: This looks like the same problem I mentioned on IRC with the Homebrew build. See this gist: https://gist.github.com/1989041 I posted a few for this very late last night. If it's still happening with the latest next, please let me know. I couldn't reproduce it here after my fix. John
Re: Simplified Python importing
On 3/6/12 2:42 AM, John Wiegley wrote: Make sure to pass --python to acprep builds to get this support. It is not on by default for 3.0, but it will be for 3.1 onwards. Boo! -1 for tantalising us with carrots. If this is working, it'd be much better to have it it the coming release so people can rely on it and use it.
Re: Simplified Python importing
I am afraid that Ledger has began to be more complex than necessary! Sure we really need this feature? The manual has now more than 100 pages! Please, that is just one opinion open for discussion. Best, Alexandre On Mar 6, 2012, at 5:50 PM, John Wiegley wrote: Simon Michael simon-jbxitmbj2llqt0dzr+a...@public.gmane.org writes: On 3/6/12 2:42 AM, John Wiegley wrote: Make sure to pass --python to acprep builds to get this support. It is not on by default for 3.0, but it will be for 3.1 onwards. Boo! -1 for tantalising us with carrots. If this is working, it'd be much better to have it it the coming release so people can rely on it and use it. Oh, it will be in the release! It's just not on by default. End users will have to pass --enable-python to the configure script. It's a beta feature right now. John
Re: Simplified Python importing
But like any very good design you don't need to know anything of the advanced features until you want to try something new, then its nice to know it is probably already there. On Tue, Mar 6, 2012 at 16:37, Alexandre Rademaker aradema...@gmail.comwrote: I am afraid that Ledger has began to be more complex than necessary! Sure we really need this feature? The manual has now more than 100 pages! Please, that is just one opinion open for discussion. Best, Alexandre On Mar 6, 2012, at 5:50 PM, John Wiegley wrote: Simon Michael simon-jbxitmbj2llqt0dzr+a...@public.gmane.org writes: On 3/6/12 2:42 AM, John Wiegley wrote: Make sure to pass --python to acprep builds to get this support. It is not on by default for 3.0, but it will be for 3.1 onwards. Boo! -1 for tantalising us with carrots. If this is working, it'd be much better to have it it the coming release so people can rely on it and use it. Oh, it will be in the release! It's just not on by default. End users will have to pass --enable-python to the configure script. It's a beta feature right now. John -- Craig, Corona De Tucson, AZ enderw88.wordpress.com
Re: Simplified Python importing
Alexandre Rademaker arademaker-re5jqeeqqe8avxtiumw...@public.gmane.org writes: I am afraid that Ledger has began to be more complex than necessary! Sure we really need this feature? The manual has now more than 100 pages! Ledger is made up of layers. The core layers are not overly complex, and were hardly affected at all by adding this Python support. My whole intention with the design of Ledger is to make the design supportive of future additions without introducing new complexity at the lower levels. Thus, if you don't build in the Python support, then Ledger runs very much as it would have if I'd never written that support. If you don't use it, you don't pay for it. If all these features were coming at the cost of core elegance and simplicity, that is when I would balk at adding them. But in actual fact, some of the new support I've added in the past two weeks has actually made Ledger *cleaner and simpler* internally, even though outwardly I've enriched its capabilities. John
Re: Simplified Python importing
Make sure to pass --python to acprep builds to get this support. It is not on by default for 3.0, but it will be for 3.1 onwards. Did changes related to this this increment the version of Boost required? Or is Boost.Python or other libraries required? I get this error when trying to build the next branch with or without the --python option: -- CXXlibledger_math_la-value.lo CXXlibledger_math_la-balance.lo /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp: In destructor 'boost::intrusive_ptrT::~intrusive_ptr() [with T = ledger::expr_t::op_t]': src/expr.h:77: instantiated from here /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp:96: error: 'intrusive_ptr_release' was not declared in this scope /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp: In copy constructor 'boost::intrusive_ptrT::intrusive_ptr(const boost::intrusive_ptrT) [with T = ledger::expr_t::op_t]': src/expr.h:81: instantiated from here /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp:91: error: 'intrusive_ptr_add_ref' was not declared in this scope make[2]: *** [libledger_math_la-balance.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 -- (rest of system is OS X 10.6.8, Xcode 4.2, boost built via MacPorts, has built ledger3 next branch in the recent past). - Zack
Re: Simplified Python importing
This looks like the same problem I mentioned on IRC with the Homebrew build. See this gist: https://gist.github.com/1989041 On Tue, Mar 6, 2012 at 8:14 PM, Zack Williams zdw...@gmail.com wrote: Make sure to pass --python to acprep builds to get this support. It is not on by default for 3.0, but it will be for 3.1 onwards. Did changes related to this this increment the version of Boost required? Or is Boost.Python or other libraries required? I get this error when trying to build the next branch with or without the --python option: -- CXXlibledger_math_la-value.lo CXXlibledger_math_la-balance.lo /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp: In destructor 'boost::intrusive_ptrT::~intrusive_ptr() [with T = ledger::expr_t::op_t]': src/expr.h:77: instantiated from here /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp:96: error: 'intrusive_ptr_release' was not declared in this scope /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp: In copy constructor 'boost::intrusive_ptrT::intrusive_ptr(const boost::intrusive_ptrT) [with T = ledger::expr_t::op_t]': src/expr.h:81: instantiated from here /opt/local/include/boost/smart_ptr/intrusive_ptr.hpp:91: error: 'intrusive_ptr_add_ref' was not declared in this scope make[2]: *** [libledger_math_la-balance.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 -- (rest of system is OS X 10.6.8, Xcode 4.2, boost built via MacPorts, has built ledger3 next branch in the recent past). - Zack
Re: Simplified Python importing
John, this is great! What other actions work besides check? Also, should that be 'import os'? :) On Mar 5, 2012, at 7:49 PM, John Wiegley jwieg...@gmail.com wrote: You can now do this in your journal file: import so tag RECEIPT check os.path.isfile(value) 2012-02-29 KFC ; RECEIPT: some_file.pdf Expenses:Food$20 Assets:Cash Enjoy, John
