Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on January 1st,
2020. Please upgrade your Python as Python 2.7 won't be maintained
after that date. A future version of pip will drop support for Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose are simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question requires administrator access, the collaborator can not deploy the add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in situations where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on January 1st,
2020. Please upgrade your Python as Python 2.7 won't be maintained
after that date. A future version of pip will drop support for Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well, like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or me, I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on January
1st,
2020. Please upgrade your Python as Python 2.7 won't be maintained
after that date. A future version of pip will drop support for Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Thanks Abdel, I will apply changes to add-ons and the wiki page soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well, like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or me, I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on January
1st,
2020. Please upgrade your Python as Python 2.7 won't be maintained
after that date. A future version of pip will drop support for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted (now
adding the appveyor for FTP, all this on my nvdaes GitHub account), ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well, like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or me, I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on January
1st,
2020. Please upgrade your Python as Python 2.7 won't be maintained
after that date. A future version of pip will drop support for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm
Rregards,
David.
2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted (now
adding the appveyor for FTP, all this on my nvdaes GitHub account), ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well, like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or me, I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on January
1st,
2020. Please upgrade your Python as Python 2.7 won't be maintained
after that date. A future version of pip will drop support for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards


El 22/05/2019 a las 2:35, DaVid escribió:

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted (now
adding the appveyor for FTP, all this on my nvdaes GitHub account), ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well, like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or me, I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards


El 22/05/2019 a las 2:35, DaVid escribió:

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted (now
adding the appveyor for FTP, all this on my nvdaes GitHub account), ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible
with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards


El 22/05/2019 a las 2:35, DaVid escribió:

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted (now
adding the appveyor for FTP, all this on my nvdaes GitHub account), ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python 3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum, available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible
with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

I just selected github aut because they recommended that option. but
since the appveyor website is not very accessible, I don't know if
that option was already selected by default.

Thanks, my github user is: david-acm

Regards,
David.

2019-05-22 4:15 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards


El 22/05/2019 a las 2:35, DaVid escribió:

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted
(now
adding the appveyor for FTP, all this on my nvdaes GitHub account),
ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page
soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or
me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change
it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python
3.

After updating PIP, we are asked to upgrade it, while it has just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum,
available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in question
requires administrator access, the collaborator can not deploy
the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible
with
Python 3 for almost all the add-ons I propose to the community.

Of course, I also kept the Python 2.7 compatibility for those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Really for me Bitbucket and Appveyor aren't very comfortable. I prefer
GitHub.
I will add you as a collaborator in case you want to fix the markdown
or add something you consider useful.
I created a website for the organization also to host there the wiki,
so I will see if I need to add you to nvdaaddons.github.io repo.


2019-05-22 12:32 GMT+02:00, DaVid <dhf360@...>:

I just selected github aut because they recommended that option. but
since the appveyor website is not very accessible, I don't know if
that option was already selected by default.

Thanks, my github user is: david-acm

Regards,
David.

2019-05-22 4:15 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards


El 22/05/2019 a las 2:35, DaVid escribió:

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted
(now
adding the appveyor for FTP, all this on my nvdaes GitHub account),
ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page
soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or
me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change
it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python
3.

After updating PIP, we are asked to upgrade it, while it has
just
been updated.

This is not a real problem because the add-on is properly built.

I just sent a question about this on the appveyor forum,
available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons
whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in
question
requires administrator access, the collaborator can not deploy
the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the
following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support
for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible
with
Python 3 for almost all the add-ons I propose to the
community.

Of course, I also kept the Python 2.7 compatibility for those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

I have invited you as a collaborator for nvdaaddons.github.io repo,
with push access.
Thanks

2019-05-22 12:38 GMT+02:00, Noelia Ruiz via Groups.Io
<nrm1977@...>:

Really for me Bitbucket and Appveyor aren't very comfortable. I prefer
GitHub.
I will add you as a collaborator in case you want to fix the markdown
or add something you consider useful.
I created a website for the organization also to host there the wiki,
so I will see if I need to add you to nvdaaddons.github.io repo.


2019-05-22 12:32 GMT+02:00, DaVid <dhf360@...>:

I just selected github aut because they recommended that option. but
since the appveyor website is not very accessible, I don't know if
that option was already selected by default.

Thanks, my github user is: david-acm

Regards,
David.

2019-05-22 4:15 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards


El 22/05/2019 a las 2:35, DaVid escribió:

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted
(now
adding the appveyor for FTP, all this on my nvdaes GitHub account),
ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons
if
possible, or to your github account, though anyway your name as the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page
soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or
me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll change
it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for Python
3.

After updating PIP, we are asked to upgrade it, while it has
just
been updated.

This is not a real problem because the add-on is properly
built.

I just sent a question about this on the appveyor forum,
available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons
whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in
question
requires administrator access, the collaborator can not deploy
the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than
GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to
this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the
following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support
for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is compatible
with
Python 3 for almost all the add-ons I propose to the
community.

Of course, I also kept the Python 2.7 compatibility for those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Thanks Noelia, I'll update it when I get home.

Regards,
DaVid.

2019-05-22 5:02 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I have invited you as a collaborator for nvdaaddons.github.io repo,
with push access.
Thanks

2019-05-22 12:38 GMT+02:00, Noelia Ruiz via Groups.Io
<nrm1977@...>:

Really for me Bitbucket and Appveyor aren't very comfortable. I prefer
GitHub.
I will add you as a collaborator in case you want to fix the markdown
or add something you consider useful.
I created a website for the organization also to host there the wiki,
so I will see if I need to add you to nvdaaddons.github.io repo.


2019-05-22 12:32 GMT+02:00, DaVid <dhf360@...>:

I just selected github aut because they recommended that option. but
since the appveyor website is not very accessible, I don't know if
that option was already selected by default.

Thanks, my github user is: david-acm

Regards,
David.

2019-05-22 4:15 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards


El 22/05/2019 a las 2:35, DaVid escribió:

You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select
the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted
(now
adding the appveyor for FTP, all this on my nvdaes GitHub
account),
ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons
if
possible, or to your github account, though anyway your name as
the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page
soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

    Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as
well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or
me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll
change
it
later, as it doesn't  use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :

Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to
make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :

Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for
Python
3.

After updating PIP, we are asked to upgrade it, while it has
just
been updated.

This is not a real problem because the add-on is properly
built.

I just sent a question about this on the appveyor forum,
available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons
whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in
question
requires administrator access, the collaborator can not deploy
the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than
GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :

Yes please, also, we will update the wiki page related to
this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel
<abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the
following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support
for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is
compatible
with
Python 3 for almost all the add-ons I propose to the
community.

Of course, I also kept the Python 2.7 compatibility for
those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

El 23 may 2019, a las 22:25, DaVid <dhf360@...> escribió:

Hi Noelia.
Sorry, I don't know how to work with github wikis. I received your
invitation and cloned the repo on the invitation:
https://github.com/nvdaes/nvdaaddons.github.io.git

But I just see readme.md file in that repo.
So, I'm doing something wrong I think.

Regards,
DaVid.

2019-05-22 6:23 GMT-06:00, DaVid via Groups.Io <dhf360@...>:

Thanks Noelia, I'll update it when I get home.

Regards,
DaVid.

2019-05-22 5:02 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I have invited you as a collaborator for nvdaaddons.github.io repo,
with push access.
Thanks

2019-05-22 12:38 GMT+02:00, Noelia Ruiz via Groups.Io
<nrm1977@...>:

Really for me Bitbucket and Appveyor aren't very comfortable. I prefer
GitHub.
I will add you as a collaborator in case you want to fix the markdown
or add something you consider useful.
I created a website for the organization also to host there the wiki,
so I will see if I need to add you to nvdaaddons.github.io repo.


2019-05-22 12:32 GMT+02:00, DaVid <dhf360@...>:

I just selected github aut because they recommended that option. but
since the appveyor website is not very accessible, I don't know if
that option was already selected by default.

Thanks, my github user is: david-acm

Regards,
David.

2019-05-22 4:15 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards

El 22/05/2019 a las 2:35, DaVid escribió:
You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select
the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was posted
(now
adding the appveyor for FTP, all this on my nvdaes GitHub
account),
ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to nvdaaddons
if
possible, or to your github account, though anyway your name as
the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page
soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as
well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia or
me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll
change
it
later, as it doesn't use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :
Hello Abdel,

This could be useful for the Weather_Plus repository as well, I
really
have not had time to consult the page, but I do not want to
make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :
Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for
Python
3.

After updating PIP, we are asked to upgrade it, while it has
just
been updated.

This is not a real problem because the add-on is properly
built.

I just sent a question about this on the appveyor forum,
available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons
whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in
question
requires administrator access, the collaborator can not deploy
the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than
GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :
Yes please, also, we will update the wiki page related to
this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel
<abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the
following
information when building with Python 2.7 after PIP update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop support
for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml file.

I also corrected the sconstruct file so that it is
compatible
with
Python 3 for almost all the add-ons I propose to the
community.

Of course, I also kept the Python 2.7 compatibility for
those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

You have to put .wiki after the repo name, without .git, that is, replace
.git with .wiki in the adrress to clone. Wiki repos are named like the main
repo where the wiki is hosted, and end with .wiki.
I created the wiki in the git.io repo so that we can host wiki pages in the
wiki, as well as a website using javascript, html, etc.

Regards

Enviado desde mi iPhone

El 23 may 2019, a las 22:25, DaVid <dhf360@...> escribió:

Hi Noelia.
Sorry, I don't know how to work with github wikis. I received your
invitation and cloned the repo on the invitation:
https://github.com/nvdaes/nvdaaddons.github.io.git

But I just see readme.md file in that repo.
So, I'm doing something wrong I think.

Regards,
DaVid.

2019-05-22 6:23 GMT-06:00, DaVid via Groups.Io
<dhf360@...>:

Thanks Noelia, I'll update it when I get home.

Regards,
DaVid.

2019-05-22 5:02 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I have invited you as a collaborator for nvdaaddons.github.io repo,
with push access.
Thanks

2019-05-22 12:38 GMT+02:00, Noelia Ruiz via Groups.Io
<nrm1977@...>:

Really for me Bitbucket and Appveyor aren't very comfortable. I prefer
GitHub.
I will add you as a collaborator in case you want to fix the markdown
or add something you consider useful.
I created a website for the organization also to host there the wiki,
so I will see if I need to add you to nvdaaddons.github.io repo.


2019-05-22 12:32 GMT+02:00, DaVid <dhf360@...>:

I just selected github aut because they recommended that option. but
since the appveyor website is not very accessible, I don't know if
that option was already selected by default.

Thanks, my github user is: david-acm

Regards,
David.

2019-05-22 4:15 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the first
option is the recommended and likely the default option. So, likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards

El 22/05/2019 a las 2:35, DaVid escribió:
You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select
the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was
posted
(now
adding the appveyor for FTP, all this on my nvdaes GitHub
account),
ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to
nvdaaddons
if
possible, or to your github account, though anyway your name as
the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki page
soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as
well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia
or
me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll
change
it
later, as it doesn't use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :
Hello Abdel,

This could be useful for the Weather_Plus repository as well,
I
really
have not had time to consult the page, but I do not want to
make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :
Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for
Python
3.

After updating PIP, we are asked to upgrade it, while it has
just
been updated.

This is not a real problem because the add-on is properly
built.

I just sent a question about this on the appveyor forum,
available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons
whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in
question
requires administrator access, the collaborator can not
deploy
the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than
GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :
Yes please, also, we will update the wiki page related to
this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel
<abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the
following
information when building with Python 2.7 after PIP
update.

DEPRECATION: Python 2.7 will reach the end of its life on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop
support
for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml
file.

I also corrected the sconstruct file so that it is
compatible
with
Python 3 for almost all the add-ons I propose to the
community.

Of course, I also kept the Python 2.7 compatibility for
those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml
file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.

Git shows an error, this message appears when the repo doesn't have a
wiki. I tried with another repo without wiki and the message is the
same.

The command:
git clone https://github.com/nvdaes/nvdaaddons.github.io.wiki.git

Message:
Cloning into 'nvdaaddons.github.io.wiki'...
fatal: remote error: access denied or repository not exported:
/f/nw/fa/dc/77/146022923/87686629.wiki.git

I have a question just to be sure. This repo is distinct from the original?
Because the original is:
https://github.com/nvdaaddons/nvdaaddons.github.io.wiki.git

It worked correctly to clone locally, even though I don't have
permissions here to push.

Regards,
David.

2019-05-23 21:39 GMT-06:00, Noelia Ruiz <nrm1977@...>:

You have to put .wiki after the repo name, without .git, that is, replace
.git with .wiki in the adrress to clone. Wiki repos are named like the
main
repo where the wiki is hosted, and end with .wiki.
I created the wiki in the git.io repo so that we can host wiki pages in
the
wiki, as well as a website using javascript, html, etc.

Regards

Enviado desde mi iPhone

El 23 may 2019, a las 22:25, DaVid <dhf360@...> escribió:

Hi Noelia.
Sorry, I don't know how to work with github wikis. I received your
invitation and cloned the repo on the invitation:
https://github.com/nvdaes/nvdaaddons.github.io.git

But I just see readme.md file in that repo.
So, I'm doing something wrong I think.

Regards,
DaVid.

2019-05-22 6:23 GMT-06:00, DaVid via Groups.Io
<dhf360@...>:

Thanks Noelia, I'll update it when I get home.

Regards,
DaVid.

2019-05-22 5:02 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I have invited you as a collaborator for nvdaaddons.github.io repo,
with push access.
Thanks

2019-05-22 12:38 GMT+02:00, Noelia Ruiz via Groups.Io
<nrm1977@...>:

Really for me Bitbucket and Appveyor aren't very comfortable. I
prefer
GitHub.
I will add you as a collaborator in case you want to fix the markdown
or add something you consider useful.
I created a website for the organization also to host there the wiki,
so I will see if I need to add you to nvdaaddons.github.io repo.


2019-05-22 12:32 GMT+02:00, DaVid <dhf360@...>:

I just selected github aut because they recommended that option.
but
since the appveyor website is not very accessible, I don't know if
that option was already selected by default.

Thanks, my github user is: david-acm

Regards,
David.

2019-05-22 4:15 GMT-06:00, Noelia Ruiz <nrm1977@...>:

I think that if using default options the procedure works, we don't
need to add other possibilities. Anyway, if you want to contribute
fixing or adding something, I would try to add you as a
collaborator
if you provide me your GitHub account.
Also, you can clone the wiki, fix the markdown file adding whatever
and attach it here, and I would modify it accordingly.

Regards


2019-05-22 11:57 GMT+02:00, DaVid <dhf360@...>:

Thanks, Maybe I selected github aut instead oaut aut, but the
first
option is the recommended and likely the default option. So,
likely
you used the same option.
I can contribute, but I don't know what is the process?
Github doesn't allow to fork wikis, how can I send pull requests?

Regards,
DaVid.

2019-05-22 0:21 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Hi, I didn't activate these permissions.
If you want, please contribute the wiki page.

Regards

El 22/05/2019 a las 2:35, DaVid escribió:
You should add what access permissions are needed.
I failed my first release using appveyor because I didn't select
the
correct options. The error message by appveyor is not useful to
determine the problem.
I solved it activating: notifications, public_repo, repo:status,
repo_deploymentm

Rregards,
David.

2019-05-21 11:11 GMT-06:00, Noelia Ruiz <nrm1977@...>:

Dear Abdel, I have updated my add-ons with your sconstruct and
appveyor for GitHub files, the gist where appveyor.yml was
posted
(now
adding the appveyor for FTP, all this on my nvdaes GitHub
account),
ad
the wiki page in nvdaaddons.
Please check it at
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor

If you want, we can remove the gist from my account to
nvdaaddons
if
possible, or to your github account, though anyway your name as
the
creator of these files is reflected:

https://gist.github.com/nvdaes/a486e45b98566d530688f6da9ce75f84

In the wiki page the raw for each file is linked.

Thanks a lot

2019-05-21 10:43 GMT+02:00, Noelia <nrm1977@...>:

Thanks Abdel, I will apply changes to add-ons and the wiki
page
soon.

2019-05-20 19:24 GMT+02:00, Abdel <abdelkrim.bensaid@...>:

Hi Noelia, Rémy and all,

Well, I just had an answer on the appveyor forum.

Change the set command to include python version folder as
well,
like
this,
set PATH=C:\Python37;C:\Python37\Scripts;%PATH%

I just applied it to avoid the reminder of the PIP update.

You'll find the corrected files in attachment.

P.S.

The sconstruct file only applies to add-ons created by Noelia
or
me,
I
think that Joseph modified his own for his specific needs.

@Rémy:

The one on the Weather_Plus add-on is also different, I'll
change
it
later, as it doesn't use appveyor yet.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 18:55, Rémy Ruiz a écrit :
Hello Abdel,

This could be useful for the Weather_Plus repository as
well,
I
really
have not had time to consult the page, but I do not want to
make
mistakes. Thank you.

Cheers.

Rémy

Le 20/05/2019 à 18:26, Abdel a écrit :
Hi Noelia,

Thank you.

Here are the appveyor.yml and sconstruct files fixed for
Python
3.

After updating PIP, we are asked to upgrade it, while it
has
just
been updated.

This is not a real problem because the add-on is properly
built.

I just sent a question about this on the appveyor forum,
available
here :

https://help.appveyor.com/discussions/problems/23663-problem-when-updating-pip

Appveyor can also be used to deploy the add-on on FTP.

As I explained to Rémy, this can be very useful for persons
whose
are
simple collaborator on a GitHub repo.

As the deployment to the Releases section of the repo in
question
requires administrator access, the collaborator can not
deploy
the
add-on in this repo after pushing a tag.

This is where uploading to FTP can be useful, or even in
situations
where the developer prefers to upload to FTP rather than
GitHub.

I renamed the 2 appveyor files according to each context ,.

Thanks.

Kind regards,
Abdel.

Le 20/05/2019 à 17:16, Noelia Ruiz a écrit :
Yes please, also, we will update the wiki page related to
this:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor


2019-05-20 16:54 GMT+02:00, Abdel
<abdelkrim.bensaid@...>:

Hi Noelia and all,

After several tests on appveyor, I wanted to give the
following
information when building with Python 2.7 after PIP
update.

DEPRECATION: Python 2.7 will reach the end of its life
on
January
1st,
2020. Please upgrade your Python as Python 2.7 won't be
maintained
after that date. A future version of pip will drop
support
for
Python
2.7.

So I updated Python to Python 3.7 in the appveyor.yml
file.

I also corrected the sconstruct file so that it is
compatible
with
Python 3 for almost all the add-ons I propose to the
community.

Of course, I also kept the Python 2.7 compatibility for
those
who
are
still building add-ons with Python 2.7.

@Noelia:

If you want, I can give you a copy of the appveyor.yml
file
fixed
for
Python 3 as well as for the sconstruct file.

Kind regards,
Abdel.