Thread: [SQLObject] Which version am I using?
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Aaron R. <aar...@mo...> - 2009-08-20 23:18:45
|
Hi All, I'm working on a project which is using an older version of SQLObject with some modifications. I'm wanting to update to the latest version, but I need to identify what changes were made so I can check them and replicate in the new version if needed. As SQLObject doesn't appear to define a "__version__", how does one tell which version one is using?? Thanks, |
From: Simon C. <hod...@gm...> - 2009-08-21 06:41:31
|
On Fri, Aug 21, 2009 at 1:18 AM, Aaron Robinson<aar...@mo...> wrote: > As SQLObject doesn't appear to define a > "__version__", how does one tell which version one is using?? Maybe try looking at the built-in documentation? The docstring for the module contains the version number (at least in version 0.10.2). Something like: pydoc sqlobject or python -c "import sqlobject; print sqlobject.__doc__" should display it for you. Schiavo Simon |
From: Oleg B. <ph...@ph...> - 2009-08-21 10:07:31
|
On Fri, Aug 21, 2009 at 08:41:17AM +0200, Simon Cross wrote: > On Fri, Aug 21, 2009 at 1:18 AM, Aaron > Robinson<aar...@mo...> wrote: > > As SQLObject doesn't appear to define a > > "__version__", how does one tell which version one is using?? > > Maybe try looking at the built-in documentation? The docstring for the > module contains the version number (at least in version 0.10.2). > > Something like: > > pydoc sqlobject > > or > > python -c "import sqlobject; print sqlobject.__doc__" > > should display it for you. sqlobject.__doc__ can even be used programmatically. Adding a kind of __version__ is in my TODO, not at the very top, but is planned for near future, probably for the next major release. Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Aaron R. <aar...@mo...> - 2009-08-21 08:36:11
|
Thanks for the idea,.. sadly this version doesn't define __doc__ either :-( On Fri, Aug 21, 2009 at 6:41 PM, Simon Cross <hod...@gm...> wrote: > On Fri, Aug 21, 2009 at 1:18 AM, Aaron > Robinson<aar...@mo...> wrote: > > As SQLObject doesn't appear to define a > > "__version__", how does one tell which version one is using?? > > Maybe try looking at the built-in documentation? The docstring for the > module contains the version number (at least in version 0.10.2). > > Something like: > > pydoc sqlobject > > or > > python -c "import sqlobject; print sqlobject.__doc__" > > should display it for you. > > Schiavo > Simon > |
From: Oleg B. <ph...@ph...> - 2009-08-21 10:11:30
|
On Fri, Aug 21, 2009 at 08:35:55PM +1200, Aaron Robinson wrote: > Thanks for the idea,.. sadly this version doesn't define __doc__ either :-( That's a really really old version. sqlobject.__doc__ was added at version 0.7 in 2005! Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Simon C. <hod...@gm...> - 2009-08-21 09:00:53
|
On Fri, Aug 21, 2009 at 10:35 AM, Aaron Robinson<aar...@mo...> wrote: > Thanks for the idea,.. sadly this version doesn't define __doc__ either :-( I think that puts you at version <= 0.6 since all branches after that have the docstring [1, 2]. If your package is called "SQLObject" and not "sqlobject" then you're at version <= 0.5 [3]. [1] http://svn.colorstudy.com/SQLObject/branches/0.6/sqlobject/__init__.py [2] http://svn.colorstudy.com/SQLObject/branches/0.7/sqlobject/__init__.py [3] http://svn.colorstudy.com/SQLObject/branches/0.5/ Schiavo Simon |
From: Oleg B. <ph...@ph...> - 2009-08-21 10:13:37
|
On Fri, Aug 21, 2009 at 11:00:39AM +0200, Simon Cross wrote: > On Fri, Aug 21, 2009 at 10:35 AM, Aaron > Robinson<aar...@mo...> wrote: > > Thanks for the idea,.. sadly this version doesn't define __doc__ either :-( > > I think that puts you at version <= 0.6 since all branches after that > have the docstring [1, 2]. > > If your package is called "SQLObject" and not "sqlobject" then you're > at version <= 0.5 [3]. > > [1] http://svn.colorstudy.com/SQLObject/branches/0.6/sqlobject/__init__.py > [2] http://svn.colorstudy.com/SQLObject/branches/0.7/sqlobject/__init__.py > [3] http://svn.colorstudy.com/SQLObject/branches/0.5/ > > Schiavo > Simon Simon, thank you for the help! Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Aaron R. <aar...@mo...> - 2009-08-21 11:21:18
|
wow, that's terrific - thanks very much for your help! On Fri, Aug 21, 2009 at 10:13 PM, Oleg Broytmann <ph...@ph...> wrote: > On Fri, Aug 21, 2009 at 11:00:39AM +0200, Simon Cross wrote: > > On Fri, Aug 21, 2009 at 10:35 AM, Aaron > > Robinson<aar...@mo...> wrote: > > > Thanks for the idea,.. sadly this version doesn't define __doc__ either > :-( > > > > I think that puts you at version <= 0.6 since all branches after that > > have the docstring [1, 2]. > > > > If your package is called "SQLObject" and not "sqlobject" then you're > > at version <= 0.5 [3]. > > > > [1] > http://svn.colorstudy.com/SQLObject/branches/0.6/sqlobject/__init__.py > > [2] > http://svn.colorstudy.com/SQLObject/branches/0.7/sqlobject/__init__.py > > [3] http://svn.colorstudy.com/SQLObject/branches/0.5/ > > > > Schiavo > > Simon > > Simon, thank you for the help! > > Oleg. > -- > Oleg Broytmann http://phd.pp.ru/ ph...@ph... > Programmers don't die, they just GOSUB without RETURN. > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > sqlobject-discuss mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss > |