On 12/5/2019 7:11 PM, RjOllos wrote:
If you want my recommendation: write a requirements.txt, write some scripts
for maintaining/upgrading your site and setup an RSS feed so you can track
changes to plugins as they happen on trac-hacks and GitHub. Setup a staging
site, pull in changes, test
On Tuesday, December 3, 2019 at 4:25:02 AM UTC-8, Mo wrote:
>
>
>
> Am Mittwoch, 27. November 2019 09:10:51 UTC+1 schrieb Mo:
>>
>> Am Montag, 25. November 2019 16:39:05 UTC+1 schrieb RjOllos:
>>>
>>>
>>> He says in the ticket, that he doesn't want to take the time to publish
>>> to PyPI, so I
Am Mittwoch, 4. Dezember 2019 17:05:02 UTC+1 schrieb Dimitri Maziuk:
>
> I am not the one having a month-long thread, in year 2020, on how to
> distribute an application with all its dependencies.
>
Thanks for your reply. So you like to distribute an application with all
its dependencies. Does
On 12/4/2019 2:48 AM, Mo wrote:
Could you please describe what problem you are trying to solve with a
docker container?
I am not the one having a month-long thread, in year 2020, on how to
distribute an application with all its dependencies.
No problem here, moving right along,
Dima
--
Am Dienstag, 3. Dezember 2019 16:54:29 UTC+1 schrieb Dimitri Maziuk:
>
> Why not just roll a Dockerfile is what I don't get?
>
Could you please describe what problem you are trying to solve with a
docker container? Usually I use a $HOME, chroot, virtualenv, perlbrew or
whatever to have separate
On 12/3/2019 6:25 AM, Mo wrote:
...
Another idea could be that there is some developer would maintain a "Trac
distribution" with a central package management, and not every single
plugin developer needs to publish to PyPI. I mean after a developer has
released a code on a repository...
Why not
Am Mittwoch, 27. November 2019 09:10:51 UTC+1 schrieb Mo:
>
> Am Montag, 25. November 2019 16:39:05 UTC+1 schrieb RjOllos:
>>
>>
>> He says in the ticket, that he doesn't want to take the time to publish
>> to PyPI, so I think that's the answer.
>>
>
> Is it possible to host multiple versions
Am Montag, 25. November 2019 16:39:05 UTC+1 schrieb RjOllos:
>
>
> He says in the ticket, that he doesn't want to take the time to publish to
> PyPI, so I think that's the answer.
>
Is it possible to host multiple versions on PyPI like a development and a
release version?
Would it be possible
On Mon, Nov 25, 2019 at 3:34 AM Mo wrote:
> Am Sonntag, 17. November 2019 21:25:04 UTC+1 schrieb RjOllos:
>>
>>
>> I suggest trying to get everything published to PyPI and install from
>> there.
>>
>
> Is there any reason for some plugins not being published on PyPI like
>
Am Sonntag, 17. November 2019 21:25:04 UTC+1 schrieb RjOllos:
>
>
> I suggest trying to get everything published to PyPI and install from
> there.
>
Is there any reason for some plugins not being published on PyPI like
https://trac-hacks.org/ticket/13690#comment:1 ?
Maybe comment directly on
On Friday, November 22, 2019 at 2:07:46 AM UTC-8, Mo wrote:
>
> Am Donnerstag, 21. November 2019 12:05:06 UTC+1 schrieb Mo:
>>
>>
>> I know that .egg files in $ENV/plugins just are loaded. But what about
>> plugins installed via pip2 to ~/.local/lib64/python2.7/site-packages/ ?
>> I just
Am Donnerstag, 21. November 2019 12:05:06 UTC+1 schrieb Mo:
>
>
> I know that .egg files in $ENV/plugins just are loaded. But what about
> plugins installed via pip2 to ~/.local/lib64/python2.7/site-packages/ ?
> I just removed TracIncludeMacro-3.2.0.dev0-py2.7.egg and installed the
> (older)
On Monday, November 18, 2019 at 8:08:37 AM UTC-8, RjOllos wrote:
>
>
> TracXMLRPC 1.1.8 has been published to PyPI. The Framework is now shown on
> TracXMLRPC page, but it looks like filtered results are cached so we'll
> have to check later whether TracXMLRPC shows when filtering by
>
Am Montag, 18. November 2019 17:08:37 UTC+1 schrieb RjOllos:
>
>
> If you notice the issue for other plugins, please report it.
>
Please find all PyPI related tickets here:
https://trac-hacks.org/query?status=!closed=~pypi
Best regards,
- Mo
--
You received this message because you are
Hi again,
I know that .egg files in $ENV/plugins just are loaded. But what about
plugins installed via pip2 to ~/.local/lib64/python2.7/site-packages/ ?
I just removed TracIncludeMacro-3.2.0.dev0-py2.7.egg and installed the
(older) TracIncludeMacro via pip2:
TracIncludeMacro 3.1.0
This
On Monday, November 18, 2019 at 4:47:15 AM UTC-8, Mo wrote:
>
> Am Sonntag, 17. November 2019 21:25:04 UTC+1 schrieb RjOllos:
>>
>> You can filter by framework:
>> https://pypi.org/search/?q===Framework+%3A%3A+Trac
>>
>
> Ok, for instance there is
> https://pypi.org/project/TracXMLRPC/
> Which I
Am Sonntag, 17. November 2019 21:25:04 UTC+1 schrieb RjOllos:
>
> You can filter by framework:
> https://pypi.org/search/?q===Framework+%3A%3A+Trac
>
Ok, for instance there is
https://pypi.org/project/TracXMLRPC/
Which I found in the wiki.
But I can't find it in any search:
On Thursday, November 14, 2019 at 11:42:22 PM UTC-8, Mo wrote:
>
> Thank you very much.
> I think it's a good idea to use such a requirements_file, eventhough I
> still think it's part of a package manager to populate such a file after a
> '*pip
> install*', just like every rpm, apt, yum or
>
> You say it is also possible to use '*pip2 install .*' from the root of a
> svn or git cloned repo. That would only replace my .egg building and
> copying. I still need to pull or sync my repos. I guess maintaining a
> requirements_file is the best as you say. '*pip2 list --user --outdated*'
>
Thank you very much.
I think it's a good idea to use such a requirements_file, eventhough I
still think it's part of a package manager to populate such a file after a
'*pip
install*', just like every rpm, apt, yum or portage does.
Who is reponsible for publishing to PyPI? Does every
On Thu, Nov 14, 2019 at 6:03 AM Mo wrote:
> Am Donnerstag, 14. November 2019 11:55:54 UTC+1 schrieb RjOllos:
>
>>
>> $ pip install svn+https://trac-hacks.org/svn/accountmanagerplugin/trunk
>>
>> * Replace pip with pip2.7 as needed
>> * For Git repositories, use "git+" prefix rather than "svn+"
Am Donnerstag, 14. November 2019 11:55:54 UTC+1 schrieb RjOllos:
>
> $ pip install svn+https://trac-hacks.org/svn/accountmanagerplugin/trunk
>
> * Replace pip with pip2.7 as needed
> * For Git repositories, use "git+" prefix rather than "svn+"
>
Thanks. But when installing from a custom link,
On Thu, Nov 14, 2019 at 2:09 AM Mo wrote:
> Am Donnerstag, 14. November 2019 09:21:51 UTC+1 schrieb Mo:
>>
>>
>> Is it a good idea to move all the Trac installation towards using pip and
>> install into ~trac/ home? How would I check all user packages for updates,
>> how would I update all?
>>
>
23 matches
Mail list logo
