Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt
+1 python 2.7 +1 on bootstrap script
One could even include the bootstrap script in the install script, but just include additional editable flats. I think we want to minimize the number of steps that the end user does.
On 3/15/11 1:44 PM, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+1 python2.7
-1 on bootstrap script. I don't like the idea of making or editing files on people's machines that are not explicitly yt. I'm also not sure about pushing people onto bitbucket. If I'm overruled, I would at least really like it if the script very explicitly states what it's going to do.
Britton
On Tue, Mar 15, 2011 at 1:57 PM, Cameron Hummels < chummels@astro.columbia.edu> wrote:
+1 python 2.7 +1 on bootstrap script
One could even include the bootstrap script in the install script, but just include additional editable flats. I think we want to minimize the number of steps that the end user does.
On 3/15/11 1:44 PM, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ 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,
+1 on python2.7. I've been using 2.7 on NASA's pleiades for a few months without any problems.
0 on the bootstrap script.
John
On 15 Mar 2011, at 13:44, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+1 python2.7, 0 on bootstrap.
On Tue, Mar 15, 2011 at 3:07 PM, John Wise jwise@astro.princeton.eduwrote:
Hi,
+1 on python2.7. I've been using 2.7 on NASA's pleiades for a few months without any problems.
0 on the bootstrap script.
John
On 15 Mar 2011, at 13:44, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ 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
+1 python 2.7 0 bootstrapping
On Tue, Mar 15, 2011 at 3:38 PM, Sam Skillman samskillman@gmail.com wrote:
+1 python2.7, 0 on bootstrap.
On Tue, Mar 15, 2011 at 3:07 PM, John Wise jwise@astro.princeton.eduwrote:
Hi,
+1 on python2.7. I've been using 2.7 on NASA's pleiades for a few months without any problems.
0 on the bootstrap script.
John
On 15 Mar 2011, at 13:44, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ 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
+1 python 2.7 (i always just type "python") +1 bootstrap
While typically I am loathe to create/modify people's systems outside of the package being installed, I think that an option to do so is a good idea in this case. I have a number of *ahem* collaborators who will never read any amount of documentation and then will complain loudly when things don't work. I think making an *optional* bootstrap script could really help get people ready to use mercurial, which would help when someone installs without the intention to develop but then later creates a patch or fix or something.
j
On Tue, Mar 15, 2011 at 1:06 PM, Chris Malone chris.m.malone@gmail.com wrote:
+1 python 2.7 0 bootstrapping
On Tue, Mar 15, 2011 at 3:38 PM, Sam Skillman samskillman@gmail.com wrote:
+1 python2.7, 0 on bootstrap.
On Tue, Mar 15, 2011 at 3:07 PM, John Wise jwise@astro.princeton.edu wrote:
Hi,
+1 on python2.7. I've been using 2.7 on NASA's pleiades for a few months without any problems.
0 on the bootstrap script.
John
On 15 Mar 2011, at 13:44, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ 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
+1 2.7.
+0 bootstrap. As long as its explicit what it modifies, and opt-in rather than opt-out, I'm ok. (A secondary script, rather than a flag in the install, would be preferable to me.)
d.
On Wed, Mar 16, 2011 at 9:03 AM, j s oishi jsoishi@gmail.com wrote:
+1 python 2.7 (i always just type "python") +1 bootstrap
While typically I am loathe to create/modify people's systems outside of the package being installed, I think that an option to do so is a good idea in this case. I have a number of *ahem* collaborators who will never read any amount of documentation and then will complain loudly when things don't work. I think making an *optional* bootstrap script could really help get people ready to use mercurial, which would help when someone installs without the intention to develop but then later creates a patch or fix or something.
j
On Tue, Mar 15, 2011 at 1:06 PM, Chris Malone chris.m.malone@gmail.com wrote:
+1 python 2.7 0 bootstrapping
On Tue, Mar 15, 2011 at 3:38 PM, Sam Skillman samskillman@gmail.com wrote:
+1 python2.7, 0 on bootstrap.
On Tue, Mar 15, 2011 at 3:07 PM, John Wise jwise@astro.princeton.edu wrote:
Hi,
+1 on python2.7. I've been using 2.7 on NASA's pleiades for a few months without any problems.
0 on the bootstrap script.
John
On 15 Mar 2011, at 13:44, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ 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
I have updated the install script, which I am testing now before committing. I did not include the starter script. At no point was this going to be part of install_script.sh, or a flag; it was going to be a secondary call that was encouraged. Note that the current install script does not touch anything outside the DEST_DIR variable. I was not suggesting that we violate this sandbox principle without consulting the user.
The install script now checks out the repo yt-supplemental, which utilizes subrepos to pull in:
* yt-doc repo * cookbook repo * The new pasteboard_template repo * The hgbb extension
I have also recently added a pasteboard extension to the 'yt' command that programmatically generates posts, descriptions and raw files that can be accessed from either the command line or automatically uploaded, like at samskillman.bitbucket.org and matthewturk.bitbucket.org. The yt-supplemental repo will help make this pasteboard mechanism more accessible to people, but it will still require some bootstrapping on the part of the user. I'm documenting it presently, and it will be part of 2.1. (For which Sam is release manager.)
Also, in response to Stephen's comment, I wrote up a developer documentation page a few weeks ago:
http://yt.enzotools.org/doc/advanced/developing.html
which could use some additional bootstrapping of hg, since I think it might be likely that people won't go to the hg tutorial. Any additional suggestions would be greatly appreciated, or you can all feel free to either directly edit/commit or issue fork/pull requests on the yt-doc repo.
Best,
Matt
-Matt
On Wed, Mar 16, 2011 at 1:42 PM, david collins antpuncher@gmail.com wrote:
+1 2.7.
+0 bootstrap. As long as its explicit what it modifies, and opt-in rather than opt-out, I'm ok. (A secondary script, rather than a flag in the install, would be preferable to me.)
d.
On Wed, Mar 16, 2011 at 9:03 AM, j s oishi jsoishi@gmail.com wrote:
+1 python 2.7 (i always just type "python") +1 bootstrap
While typically I am loathe to create/modify people's systems outside of the package being installed, I think that an option to do so is a good idea in this case. I have a number of *ahem* collaborators who will never read any amount of documentation and then will complain loudly when things don't work. I think making an *optional* bootstrap script could really help get people ready to use mercurial, which would help when someone installs without the intention to develop but then later creates a patch or fix or something.
j
On Tue, Mar 15, 2011 at 1:06 PM, Chris Malone chris.m.malone@gmail.com wrote:
+1 python 2.7 0 bootstrapping
On Tue, Mar 15, 2011 at 3:38 PM, Sam Skillman samskillman@gmail.com wrote:
+1 python2.7, 0 on bootstrap.
On Tue, Mar 15, 2011 at 3:07 PM, John Wise jwise@astro.princeton.edu wrote:
Hi,
+1 on python2.7. I've been using 2.7 on NASA's pleiades for a few months without any problems.
0 on the bootstrap script.
John
On 15 Mar 2011, at 13:44, Matthew Turk wrote:
Hi all,
I'd like to move the install script to 2.7. This seems to fix all the issues with the install script on OSX, but it means everyone's muscle memory will have to be corrected if you're used to typing "python2.6". (An alternative would be to add an alias, "pyyt" or something.)
[+-][01] on Python 2.7?
One additional question, what would people think about a "bootstrap" script being included that users are encouraged to run following the installation script? This script could set up ~/.hgrc and also create a bitbucket user from the CLI. What do you think?
[+-][01] on optional bootstrap script?
If we have support for item 1, I'll push it out sometime later this week. #2 would be on the few week timescale. (Lots of non-yt projects I'm focusing on for a while.)
-Matt _______________________________________________ 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
-- Sent from my Stone Tablet and carried by my Pterodactyl. _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-
Britton Smith -
Cameron Hummels -
Chris Malone -
david collins -
j s oishi -
John Wise -
Matthew Turk -
Sam Skillman