3.0 version labeled as '2.5-dev'
Hello All, Is there some special reason that the __version__ in yt-3.0 is listed as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change? Be Well Anthony
Hi Anthony, I believe that's an oversight and it should be 3.0-dev - compare to the VERSION variable in the setup script. Matt, can you confirm that? -Nathan On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
Hello All,
Is there some special reason that the __version__ in yt-3.0 is listed as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change?
Be Well Anthony _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Anthony,
In the tip of my clone it's set to 3.0 in setup.py.
Also, I have recently merged from yt 2.x but not yet pushed to the
main repository. I've been working on "acceptance scripts" here:
https://bitbucket.org/MatthewTurk/yt.acceptance_scripts/
These include links to datasets and checks on the data. If you get a
chance, could you add download and testing checks for the polar data
to it? I'll push the big merge to the main repository in a few
minutes.
-Matt
On Tue, Jan 15, 2013 at 2:55 PM, Nathan Goldbaum
Hi Anthony,
I believe that's an oversight and it should be 3.0-dev - compare to the VERSION variable in the setup script.
Matt, can you confirm that?
-Nathan
On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
Hello All,
Is there some special reason that the __version__ in yt-3.0 is listed as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change?
Be Well Anthony _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Matt, I believe Anthony is referring to yt/__init__.py, where version is set to "2.5-dev" in my copy. -Nathan On Jan 15, 2013, at 12:01 PM, Matthew Turk wrote:
Hi Anthony,
In the tip of my clone it's set to 3.0 in setup.py.
Also, I have recently merged from yt 2.x but not yet pushed to the main repository. I've been working on "acceptance scripts" here:
https://bitbucket.org/MatthewTurk/yt.acceptance_scripts/
These include links to datasets and checks on the data. If you get a chance, could you add download and testing checks for the polar data to it? I'll push the big merge to the main repository in a few minutes.
-Matt
On Tue, Jan 15, 2013 at 2:55 PM, Nathan Goldbaum
wrote: Hi Anthony,
I believe that's an oversight and it should be 3.0-dev - compare to the VERSION variable in the setup script.
Matt, can you confirm that?
-Nathan
On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
Hello All,
Is there some special reason that the __version__ in yt-3.0 is listed as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change?
Be Well Anthony _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Actually, Anthony, I have the cylindrical data / scripts you sent me
last December. I'm going to use those for generating and checking
against reference images.
On Tue, Jan 15, 2013 at 3:01 PM, Matthew Turk
Hi Anthony,
In the tip of my clone it's set to 3.0 in setup.py.
Also, I have recently merged from yt 2.x but not yet pushed to the main repository. I've been working on "acceptance scripts" here:
https://bitbucket.org/MatthewTurk/yt.acceptance_scripts/
These include links to datasets and checks on the data. If you get a chance, could you add download and testing checks for the polar data to it? I'll push the big merge to the main repository in a few minutes.
-Matt
On Tue, Jan 15, 2013 at 2:55 PM, Nathan Goldbaum
wrote: Hi Anthony,
I believe that's an oversight and it should be 3.0-dev - compare to the VERSION variable in the setup script.
Matt, can you confirm that?
-Nathan
On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
Hello All,
Is there some special reason that the __version__ in yt-3.0 is listed as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change?
Be Well Anthony _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Nathan,
Ah, oops. Yeah, looks like that slipped under my radar; I don't even
remember when Casey added it. I'll update it, but that should only be
considered very coarse-grained information -- the actual version
number can be gotten with get_version_stack() or get_yt_version(),
both of which are in mods.
-Matt
On Tue, Jan 15, 2013 at 3:08 PM, Nathan Goldbaum
Hi Matt,
I believe Anthony is referring to yt/__init__.py, where version is set to "2.5-dev" in my copy.
-Nathan
On Jan 15, 2013, at 12:01 PM, Matthew Turk wrote:
Hi Anthony,
In the tip of my clone it's set to 3.0 in setup.py.
Also, I have recently merged from yt 2.x but not yet pushed to the main repository. I've been working on "acceptance scripts" here:
https://bitbucket.org/MatthewTurk/yt.acceptance_scripts/
These include links to datasets and checks on the data. If you get a chance, could you add download and testing checks for the polar data to it? I'll push the big merge to the main repository in a few minutes.
-Matt
On Tue, Jan 15, 2013 at 2:55 PM, Nathan Goldbaum
wrote: Hi Anthony,
I believe that's an oversight and it should be 3.0-dev - compare to the VERSION variable in the setup script.
Matt, can you confirm that?
-Nathan
On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
Hello All,
Is there some special reason that the __version__ in yt-3.0 is listed as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change?
Be Well Anthony _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hey Matt.
If I remember, that was for GDF writing. We needed a yt version string for
that GDF attribute.
- Casey
On Tue, Jan 15, 2013 at 12:10 PM, Matthew Turk
Hi Nathan,
Ah, oops. Yeah, looks like that slipped under my radar; I don't even remember when Casey added it. I'll update it, but that should only be considered very coarse-grained information -- the actual version number can be gotten with get_version_stack() or get_yt_version(), both of which are in mods.
-Matt
Hi Matt,
I believe Anthony is referring to yt/__init__.py, where version is set to "2.5-dev" in my copy.
-Nathan
On Jan 15, 2013, at 12:01 PM, Matthew Turk wrote:
Hi Anthony,
In the tip of my clone it's set to 3.0 in setup.py.
Also, I have recently merged from yt 2.x but not yet pushed to the main repository. I've been working on "acceptance scripts" here:
https://bitbucket.org/MatthewTurk/yt.acceptance_scripts/
These include links to datasets and checks on the data. If you get a chance, could you add download and testing checks for the polar data to it? I'll push the big merge to the main repository in a few minutes.
-Matt
On Tue, Jan 15, 2013 at 2:55 PM, Nathan Goldbaum
wrote: Hi Anthony,
I believe that's an oversight and it should be 3.0-dev - compare to
On Tue, Jan 15, 2013 at 3:08 PM, Nathan Goldbaum
wrote: the VERSION variable in the setup script. Matt, can you confirm that?
-Nathan
On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
Hello All,
Is there some special reason that the __version__ in yt-3.0 is listed
as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change?
Be Well Anthony _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Ah, right -- makes sense.
For what it's worth, I've updated the acceptance scripts and pushed a
series of changesets that
1) Merges with 2.x
2) Fixes a bug with RAMSES IO
I've also pushed in the recent pull request I issued where I added a
binary gadget data reader.
On Tue, Jan 15, 2013 at 3:24 PM, Casey W. Stark
Hey Matt.
If I remember, that was for GDF writing. We needed a yt version string for that GDF attribute.
- Casey
On Tue, Jan 15, 2013 at 12:10 PM, Matthew Turk
wrote: Hi Nathan,
Ah, oops. Yeah, looks like that slipped under my radar; I don't even remember when Casey added it. I'll update it, but that should only be considered very coarse-grained information -- the actual version number can be gotten with get_version_stack() or get_yt_version(), both of which are in mods.
-Matt
On Tue, Jan 15, 2013 at 3:08 PM, Nathan Goldbaum
wrote: Hi Matt,
I believe Anthony is referring to yt/__init__.py, where version is set to "2.5-dev" in my copy.
-Nathan
On Jan 15, 2013, at 12:01 PM, Matthew Turk wrote:
Hi Anthony,
In the tip of my clone it's set to 3.0 in setup.py.
Also, I have recently merged from yt 2.x but not yet pushed to the main repository. I've been working on "acceptance scripts" here:
https://bitbucket.org/MatthewTurk/yt.acceptance_scripts/
These include links to datasets and checks on the data. If you get a chance, could you add download and testing checks for the polar data to it? I'll push the big merge to the main repository in a few minutes.
-Matt
On Tue, Jan 15, 2013 at 2:55 PM, Nathan Goldbaum
wrote: Hi Anthony,
I believe that's an oversight and it should be 3.0-dev - compare to the VERSION variable in the setup script.
Matt, can you confirm that?
-Nathan
On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
Hello All,
Is there some special reason that the __version__ in yt-3.0 is listed as '2.5-dev'? Am I missing something subtle about the release schedule or is this safe to change?
Be Well Anthony _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hello All,
Sorry about not being able to write back sooner. But it looks like y'all
figured it out without me. Good work ;).
Be Well
Anthony
On Tue, Jan 15, 2013 at 2:38 PM, Matthew Turk
Ah, right -- makes sense.
For what it's worth, I've updated the acceptance scripts and pushed a series of changesets that
1) Merges with 2.x 2) Fixes a bug with RAMSES IO
I've also pushed in the recent pull request I issued where I added a binary gadget data reader.
Hey Matt.
If I remember, that was for GDF writing. We needed a yt version string for that GDF attribute.
- Casey
On Tue, Jan 15, 2013 at 12:10 PM, Matthew Turk
wrote: Hi Nathan,
Ah, oops. Yeah, looks like that slipped under my radar; I don't even remember when Casey added it. I'll update it, but that should only be considered very coarse-grained information -- the actual version number can be gotten with get_version_stack() or get_yt_version(), both of which are in mods.
-Matt
On Tue, Jan 15, 2013 at 3:08 PM, Nathan Goldbaum
wrote:
Hi Matt,
I believe Anthony is referring to yt/__init__.py, where version is set to "2.5-dev" in my copy.
-Nathan
On Jan 15, 2013, at 12:01 PM, Matthew Turk wrote:
Hi Anthony,
In the tip of my clone it's set to 3.0 in setup.py.
Also, I have recently merged from yt 2.x but not yet pushed to the main repository. I've been working on "acceptance scripts" here:
https://bitbucket.org/MatthewTurk/yt.acceptance_scripts/
These include links to datasets and checks on the data. If you get a chance, could you add download and testing checks for the polar data to it? I'll push the big merge to the main repository in a few minutes.
-Matt
On Tue, Jan 15, 2013 at 2:55 PM, Nathan Goldbaum
wrote: Hi Anthony,
I believe that's an oversight and it should be 3.0-dev - compare to the VERSION variable in the setup script.
Matt, can you confirm that?
-Nathan
On Jan 15, 2013, at 11:45 AM, Anthony Scopatz wrote:
> Hello All, > > Is there some special reason that the __version__ in yt-3.0 is
On Tue, Jan 15, 2013 at 3:24 PM, Casey W. Stark
wrote: listed > as '2.5-dev'? Am I missing something subtle about the release schedule or > is this safe to change? > > Be Well > Anthony > _______________________________________________ > yt-dev mailing list > yt-dev@lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (4)
-
Anthony Scopatz
-
Casey W. Stark
-
Matthew Turk
-
Nathan Goldbaum